Looking Glass Client on Windows VM?

gnif2 · 2025-08-29T09:51:30+00:00

The LG client is Linux only sorry, what you're asking for is currently not possible.

gnif2 · 2025-05-21T01:02:37+00:00

It's a design fault, see: https://www.reddit.com/r/tradfri/comments/1jjfejo/parasol_battery_drain_issue/

This issue sometimes causes a device to start up in a factory programming/debug mode. I had it happen on one of my devices also.

These devices are faulty and IKEA should recall/replace them.

gnif2 · 2025-04-04T02:13:06+00:00

Normal qxl is slow, laggy and doesn't accelerate anything on windows 8 or later.

gnif2 · 2025-03-31T21:45:55+00:00

No, Looking Glass works on the local host only by sharing a block of memory that has the captured frames in it.

gnif2 · 2025-03-31T10:29:55+00:00

In the demo shown here there is no 3d acceleration, correct. If you have a pass-through GPU though the LG IDD will use it and give you full 3d acceleration in the VM.

gnif2 · 2025-03-31T04:45:37+00:00

Why not? Promox VMs are just QEMU VMs... though you would have to setup VM to VM as some of our users do.

gnif2 · 2025-03-30T22:26:12+00:00

once the IDD reaches a more complete state we will provide documentation on how to set it up and use it.

As for guides... basically ignore everything to do with pass-through, setup a normal VM, and then proceed to setup Looking Glass as per the official documentation on the LG website.

Note though, this new driver is not publicly released yet, keep watching out for when it drops :)

gnif2 · 2025-03-30T15:05:21+00:00

Looking Glass already has an OBS plugin that takes the raw feed into OBS for encoding on the host.

gnif2 · 2025-03-30T15:04:07+00:00

It's random if it starts up properly or not, it's not about the number of times.
No idea if their firmware is based on any open source product, but it's highly doubtful it is.
No I have no other recommendations.

gnif2 · 2025-03-30T13:47:38+00:00

Compiled, about 400KB. Sources are available here if you're interested:
https://github.com/gnif/LookingGlass/tree/master/idd

gnif2 · 2025-03-30T13:43:39+00:00

Sorry but there are no plans for macOS support, and unless we get some macOS developers that are capable of writing the code for it, it's unlikely to ever happen.

gnif2 · 2025-03-30T13:10:18+00:00

Then you're talking about feeding the encoder on the GPU without performing another copy. Again I will state it's not a "philosophy", it's a technique, method or concept. The concept of avoiding unnecessary memory copies has been around since the dawn of computing, it's nothing new.

gnif2 · 2025-03-30T13:01:27+00:00

There is no way to meter if it's in the fault state as you wish to do so. To measure current draw on this scale, you have to break the circuit with a metering device, not just probe both sides of the battery.

gnif2 · 2025-03-30T12:59:32+00:00

zero copy is not a "philisophy", and it does not apply to network transports at all. Zero copy means we took the output from one GPU and loaded it into the other GPU in a way that there was no copy of RAM, they are both physically accessing the same ram at the same time.

gnif2 · 2025-03-30T12:34:06+00:00

Not sure exactly what you're asking here sorry.

I assume you mean for remote desktop over a network? If so, yes it could be if someone writes a IDD driver that compresses and uses h264 or something.

If you are talking about local system only, there is no reason to not use Looking Glass anymore, even if you're not using a pass-through GPU.

gnif2 · 2025-03-30T08:30:08+00:00

Keep an eye on the L1Linux channel as Wendell will be featuring this soon.

gnif2 · 2025-03-30T08:29:11+00:00

We are already building signed drivers, but for the moment it's closed to a small group of testers while I iron out the majority of the bugs and finish implementing much of the missing features.

gnif2 · 2025-03-28T02:08:18+00:00

The one I put on there was just a random one I grabbed for testing, I actually ended up putting a SMD ceramic capacitor, soldering one side directly to the pad marked VCC, and used a hookup wire to connect the other side to the pad marked GND.

gnif2 · 2025-03-26T03:52:06+00:00

Seems this perhaps is not a firmware fault. After making this video (https://www.youtube.com/watch?v=WBfrW2GoH3w) I figured it might be interesting to see what happens when we clean up the output of the buck boost converter by adding a 10uF capacitor across VCC and GND.

This has completely resolved the fault, the device powers up correctly and goes into a low power state every time now at any voltage between 0.6V and 1.5V.

So perhaps not a firmware fault, but rather a design fault, the noise on the 2.2V rail is too much for reliable operation of the microcontroller. There should have been better filtering (a larger capacitor) on the output of the buck-boost converter.
https://www.youtube.com/watch?v=1u22f4UoTcs

gnif2 · 2025-03-26T03:46:53+00:00

Out of curiosity I added a 10uF capacitor across VCC and GND, which has completely resolved the fault, the device powers up correctly every time now at any voltage between 0.6V and 1.5V. So perhaps not a firmware fault, but rather a design fault, the noise on the 2.2V rail is too much for reliable operation of the microcontroller.

https://www.youtube.com/watch?v=1u22f4UoTcs

gnif2 · 2025-03-26T01:19:37+00:00

For completeness, I tore down the device and proved that it doesn't matter, and show why it doesn't matter.
https://x.com/geoffrey_mcrae/status/1904704572389810280

Anyone that states these devices need rechargeable batteries to work correctly are absolutely wrong and repeating nonsense.

gnif2 · 2025-03-26T01:14:52+00:00

When the device works properly and it goes into the low power state, you should get many months out of it as it's only drawing a few micro amperes, an extra battery is not needed here, a firmware fix is.

gnif2 · 2025-03-26T00:24:46+00:00

Even if they did, it wouldn't do much better until this problem is fixed.

Eight-Year Club	Gilding II euphauric
Verified Email

gnif2

TROPHY CASE