Rayn19

Make a new String Value in HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM , named, CustomThemeResource containing the path to the custom theme resource file and restart (or change between themes). .

I too had that error when using RP theme. Here's the debug log, with custom themes. Intel HD 3000 -> w/ Shader Render Optimization enabled. nVidia 9500GT -> w/ Shader Render Optimization disabled.

Here's a quick debug log for RC3, tried it first without enabling shader render optimization and then enabled. Couple of restarts and change in colorization settings. Working really fine till now, can see a little better performance than the previous RC. Will also provide debug for dual monitors later. intel HD 3000 BTW, which all video cards are supported for shader render optimization, discrete or integrated?

Hey, here are my debug files from my two test systems, have tested it for more than 10 days now, so the debug files have grown in couple of MBs. Intel HD 3000 -- nVidia 9500GT

Yes, Like a hidden forum topic that only special members can see, in this case TESTERS. BTW, here's my debug log from my two systems, been running RC2 for about 4days or so, regular usage. Intel HD 3000 | nVidia 9500GT(Tested with Games, no lags or performance issues)

Read the first page of the post of this topic.

Here's the RC2 debug log. Here's a quick screenshot of my desktop with RC2 enabled.

My Lock screen got skipped a couple of times while using RC1 and it still, sometimes, gets skipped in RC2, does anyone else have the same problem? I tried it on a fresh install of Windows 8 and still the problem persists. Here are my RC1 debug logs, and debug logs after fresh install. The performance seems a little more better with RC2, cant wait for the final release. BTW, bigmuscle, what are your plans for its GUI?

Nope, minidump does not need any files from MS servers and they don't even need any PDB files. It is a footprint of DWM process memory, so I can analyze it on my own PC more deeply than simple exception callstack in text file provides. The only disadvantage is the size of minidump file which is over 100 MBytes. OK. Still it can be compressed using 7z or similar formats. EDIT: Everything looks better in Aero

Nice work bigmuscle, the RC1 seems to be working properly on both Intel HD 3000 and on nVidia 9500GT. Till now no flickering or artifacts on both systems. I have attached the debug.log for both these systems below. Intel HD 3000: debug.log nVidia 9500GT: debug.log As you said in the release log, that there won't be any crash log, instead a minidump, will this require any internet connection to download the appropriate files from MS servers (as you said a couple of days back)...? The reason I am asking is because I don't have a constant internet connection on any of my systems.

The RC0 is much more stable than the BETA3 on my Intel HD 3000, the performance is much better. No artifacts seen till now and no crash log. I tried to run it on nVidia 9500GT but it fails to load properly on startup. When I log in, I am greeted with a black screen with only my mouse pointer. When I tried holding CTRL while logging in, the AERO Glass is still loaded to explorer, but the taskbar remains unaffected. I even tried the crashfix for v0.91, still have the same problem. I have also checked the uDWM.dll versions on both systems, both have 6.2.9200.16420 in system32 folder. I have attached both systems debug.log and/or crash.log, the system with nVidia card has dual monitors btw. Intel HD 3000: debug.log (no crash log) nVidia 9500GT: debug.log | crash.log nVidia 9500GT(w/ crashfix): debug.log (no crash log) Looking at the posts by Tusticles, the problem is related to nVidia cards. It runs well under intel HD (integrated graphics).

bigmuscle, the new version is working really well, there were no visible artifacts compared to the previous version when I use on my laptop with Intel HD 3000 but when I use it on my desktop with nVidia 9500 card, specially when I use dual monitors and I hover my mouse over any glass effect object I see artifacts. Here are my debug and crash logs Intel HD 3000: debug.log | crash.log nVidia 9500GT: debug.log | crash.log

Try lowering the the color intensity, while using v0.85.

Extract the 7z archive to a folder, for example "C:/DWM", now rgt click on LoadGlass_AppInit_DLLs.reg and select edit, now replace the AppInit_DLLs value as per the location of your extracted files, as per the example "C://DWM//DWMGlass.dll". Save the file and merge it with registry. Restart your computer and Aero Glass should start. Thanks for the reply. =)I tried doing this but the Aero glass doesn't load on reboot, however the version 0.5 with the exe file continues to work. I wonder why this is. Do I need to edit more registry entries than the ones given to get it to work? Thanks. When you tried v0.8, did you still get the popup message? You can try the v0.85 Debug version, and post your debug and/or crash log for bigmuscle to analyse...

Extract the 7z archive to a folder, for example "C:/DWM", now rgt click on LoadGlass_AppInit_DLLs.reg and select edit, now replace the AppInit_DLLs value as per the location of your extracted files, as per the example "C://DWM//DWMGlass.dll". Save the file and merge it with registry. Restart your computer and Aero Glass should start.

Check your PM.

Which version are you using? 0.8? Try v0.85, and post the debug and crash log here.

It is the RP theme, if I am not mistaken...RP had bigger Nav Buttons. @bigmuscle: Which version of shell32 and uDWM are compatible with Aero for Windows 8?

9.x didn't work but enabling UseNativeBlur worked Can you give link to version 0.85? I can't find it Try updating your driver. It might be because of incompatible system files as bigmuscle stated. Here's v0.85.

Here you go, GlassDebug.

Close animation works in the new version.

The new version shows 2 incompatible DLLs, shell32.dll and themecpl.dll. shell32.dll: 6.2.9200.16547 themecpl.dll: 6.2.9200.16394 and here's my debug log. I am still seeing artefacts on the glass. NativeGlass is enabled, btw whats its value is it 0x00000001 or 0x10000000, as Tusticles stated?

Here's my debug and crash log files...I was not able to upload here, so follow the link. debug.log crash.log

Hey bigmuscle, is there any way to get blur without NATIVE Blur like in v0.7?

Its turn out, the blur was from the previous version (v0.7), I was using AGTweaker so v0.7 was still loaded. When I completely removed it and tried v0.8, I only got transparency. Used NATIVE BLUR function, it worked but its glitch-y. The glitch is not visible in any screenshots.