vjott

The link is dead.

^Someone seems a bit pushy^ Excellent work, bigmuscle. With the latest (0.5) release everything works great and Direct3D mode with colour intensity reduced gives me Aero Perfection. Using Direct3D rendering, everything on my desktop is faster (moving, closing, minimising and maximising windows). Thanks, again for your time and effort working on this project.

you could try also different values - e.g. 0x9100 or 0x9200. 0x9100 works for me - other 2 values do not It finally works. Using version 0.4 (without the 2 files you posted) it works fine by setting DeviceFeatureLevel to 0x9100

Adding that registry key and value does not work for me. Everything opaque.

When I use the 2 files in the link, I also notice the following errors reported in the debug log: Lines 8-11: [0x152C] Failed to open desktop process (error: 5) [0x152C] Failed to get token (error: 6) [0x152C] Failed to duplicate token (error: 6) [0x152C] Failed to impersonate logged user (error: 6) Line 22: [0x794] Failed to open desktop process (error: 5) Line 24: [0x794] Failed to get token (error: 6) Line 26: [0x794] Failed to duplicate token (error: 6) Line 29: [0x794] Failed to impersonate logged user (error: 6) Lines 46 & 47: [0x794] Failed to open desktop process (error: 5) [0x794] Failed to get token (error: 6) Line 50: [0x794] Failed to impersonate logged user (error: 6) I hope this helps in some small way.

I replaced the 2 files in version 0.4 with the 2 files in the link and the behaviour is the same: no transparency. Debug log attached. debug.log.txt

Drop the files in a folder called "DWM" in your root directory. For example: C:\DWM Then doubleclick the file called DWMLoader.exe The download link is in the announcement post you quoted.

I deleted all the registry keys that I added for the previous releases but still no luck.

Yeah, it might simply be different files from what he was working with or something.

yeah, this is done by the time which sets windows as layered. It runs with interval 500 ms thus new windows won't have transparency effect until the update routine is executed. This could be easily fixed by installing global windows hook which sets the window as layered during its creation. Problem is that this would require to have another service running (just because dwm.exe process does not run under logged user credentials). For anyone, who has problem with 0.4, could you try set BypassLayeredWindowsRendering to zero whether it helps? I tried adding BypassLayeredWindowsRendering to the registry and setting it to zero but the same issue occurs. Everything remains opaque. I seems that you know what the problem is so I guess we'll leave it to you.