bigmuscle

shaneblack: could you provide your debug log?

Not in 1.0. Actually... if you want glass or not, you simply run and stop this application. Any need for a settings? I want to do it more clever, such as disabling glass when on battery etc.

I already wrote it, but it is totally impossible to get transparency without blur. Why? Because there is no such code. Such code was there but it was in some old beta version (which really was incorrectly executed on some video adapters) . Thus if you get transparency without blur than you have this utility incorrectly installed.

no, it's not expected but it works here correctly. But i have not tried to restart DWM, just forced to reload settings via control panel. EDIT: ah, I noticed that restarting DWM makes inactive frames to be drawn by default color and it is refreshed to correct color when window is redrawn.

And to inactive colors... how to reproduce your problem? I changed appropriate registry values and have no problems. Inactive frame color changed as expected.

Release candidate generally means that the software has not been fully released yet and it is not intended for regular usage. Yeah, it does not install exception handler in explorer process. The only executed code in this process is at startup and when modifying color settings in control panel. Thus if it crashes at another time then it is not fault of my utility. Not many... This is not the complete truth. If your video adapter supports DX11.1, you will be able to set 11.1 correctly. On the other side, if you adapter does not support anything higher than DX 9.3, it will crash for anything above this version. When this settings is not touched, it starts with the highest possible version and tries until it succeed.

I wanted to check the changes in Win8.1 DWM but the debug symbols are not available for build 9385 so it is very hard to see anything.

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.

What is your resolution? The flickering seems to appear under certain resolutions only and I should fix it in the next version.

AERO GLASS for Win8 RC1 * fixed hook return values on x64 * fixed compatibility with old 64-bit udwm.dll * fixed exception handler when settings loading crashes * fixed crash when removing D3D device * do not generate occlusion for border-less windows * fixed bug when source box does not fit into screen height in CopySubresourceRegion * produce minidump on crash instead of crashlog https://developer.berlios.de/project/showfiles.php?group_id=13124

yes, if this log is complete, it means that it has not been injected into dwm at all - or you just placed DLL into the folder where dwm.exe has not write privileges.

i already wrote that callBlurShapes is just temporary solution which does not generate glass regions properly thus it makes no sense to report bugs when this mode is enabled

It's not overlap but when window bottom edge has Y coordinate higher than screen_height - 7 (which is actually applied to taskbar too), then D3D debug mode shouts than I am out of range. This could be driver-dependent that some driver ignores it, but some driver fails completely resulting in black screen.

Nope, callBlurShapes does not provide much useful information. The only thing which can be tested with it is DWM compatibility + colorization settings. Btw, I found a bug which happens when window is moved outside the bottom screen boundary. Could that be what you were reporting as "black screen when I touch the taskbar" (so it is not touching the taskbar but moving the part of window below the taskbar) ???

When changing Color intensity in personalize menu these registry values are changed. ColorizationAfterglow ColorizationAfterglowBalance ColorizationBlurBalance ColorizationColor Because it also modifies the color to look better on selected opacity level. calBlurShapes is just a temporary solution because it does not generate glass region properly and can break with any Windows Updates. I will remove it when I am able to fix the issue. I will post another version to test when I manage to log Direct3D pipeline errors.

Minidump is not important now, it will always look same - stuck in nVidia driver after DWM failed wth ERR_NO_HARDWARE error. Just post debug.log if you use "x64_HookFlag" version.

It's percentage, so 0 - 100 is valid range, but it will take also a bit of ColorizationAfterglowBalance.

No, there is no such settings. If you want registry settings to control opacity then it is Windows native settings ColorizationBlurBalance. BTW, could anyone help how to properly log Direct3D errors? The problem seem to be some error during Draw so I need to detect what's wrong. I know that e.g. DebugView displays some errors but its window is not visible on error in DWM.

Excelent, at least I know it won't be some magic and know exactly which code to check :-) By opacity setting you mean the Intensity slider in Windows Colors control panel? There is no reason why it should not work, unless there is another bug - I just tested it and it works.

ah, so when callBlurShapes is set to 0x1, then it works always regardless HookFlag (even when this setting does not exist) ?

And when callBlurShapes is set to 0x1 (under HKCU), 8 + 2 (= 10 or 0xa) does not work either?

Yes, I did. My info comes this minidump. This one:

So if you put the value correctly (as decimal and not hexa) and value 10 (0xa) makes everything work correctly (transparency with blur but with glitches) then it seems there is some incompatibility between nVidia driver and glass safety zones (which is a new thing added to RC0 to get rid of artifacts but it is DWM native code completely) and I'm afraid that I won't be able to do anything about this except of adding the registry settings to switch to old technique (extend glass zone on my own but with occasional glitches). Could you just post debug.log from this latest build? edit: from minidump, I found DWM fails with MILERR_NO_HARDWARE_DEVICE error.

Done. Applied, black screen, pressed f11, I waited several minutes then I did a force restart and returned to desktop holding ctrl key Then added that key with this value 0x00000001, re-applied dwmglass, no black screen but transparency was not applied, Ok, if you can 100% confirm that setting NoInternalHooks to 0x1 does not bring black screen (and it was not just random) then it is time to try this version http://leteckaposta.cz/111719826 It adds this registry settings: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM: HookFlag (DWORD) which can control what NoInternalHooks disabled completely. Valid values are 1, 2, 4, 8 + their combinations (summations = anything between 1..15), maximum value = 1+2+4+8 = 15 (0xF) which enables everything, 0 disables almost everything (like NoInternalHooks did). I hope this helps me to find which function is the problem.

The message box is created with the flag MB_SERVICE_NOTIFICATION but I don't see reason why message box should kill some process.