bigmuscle

According to the minidumps, the crash does not even occur in Aero Glass, so the question is whether it is really related to the Aero Glass itself.

Then provide minidumps in such case. Just a information about crash is useless.

I would not advise this. If someone is not able to read what OS version is Aero Glass intended for, then he should not use experimental debug builds, because it will be harmful for him. (And the next question here would be why it displays debug windows).

I removed your topic, because you are not allowed to publish here builds which are intended for donators only.

Experimental build #675 for 32-bit Win10 10.0.14393 has been uploaded.

It's simple - as I said in another forum - users still need to complain about something, so if I don't release installer they will complain, if I release installer without 32-bit version they will complain. So why don't just give some other benefit to donators and provide them non-installer final release build before everything is completed? You are right here and I already mentioned some time ago. 32-bits builds/hooks are real pain in the a** and I have long-time idea to drop the 32-bit version completely.

Thanks for your reports. It worked on my home computer, but it really does not work here on my work computer. I will look at it later this afternoon.

Aero Glass for Win8.1+ v1.4.6 * hardcoded symbol patterns for build 10586.589 * dirty region optimization fixes * when DWM process crashes too often, Aero Glass will stop injecting * fixed data sharing between more drawings in one pass This version is designed for Windows 8.1 and Windows 10 TH up to build 10586 only! Use this topic to discuss v1.4.6 only! Discussion about RS build will be deleted to avoid off-topic and increase readability!

And do you have secure boot disabled?

Probably not. I will rather port some fixes back to 1.4.5 and release separate version. It would add some other time to have one version working on both systems.

Pre-release version is not for testing. It is just a regular release which has been published earlier so donators do not need to wait before I finish other stuff - 32-bit version, installer etc. I hope that many different forums will also leak their own Aero Glass if I decide to stop the development completely

I checked the error log and found this error: "Recipient address rejected: Domain not found", so surely when your e-mail is not accessible, it cannot send you a new password there.

AeroGlass is just a rendering engine for DWM. Office apps override DWM and draw its own frame by itself. So it is not possible.

Build #669 - Pre-release, 64 bit Designed for Windows 10 build 14393 Same as #668 but compiled as release build Requires sign in to your profile This build is candidate for the final release. Public installer will be made when 32-bit version is finished.

Build #668, 64 bit Designed for Windows 10 build 14393 Fixed occlusion management for overlapped dirty regions http://glass8.eu/beta

Problem fixed.

Thank you for your information, I forgot to make the redirection.

Could you test this: When set to 0x1, the dirty region optimization will be completely disabled. It will bring glitches on Start menu (and other areas which are blurred natively in Win10) but it should stay completely fine else where.

I forgot to mentioned two known bugs in ModernFrame: - it does not work correctly in apps which has their client area extended to the frame (e.g. Edge) - it sometimes works, but sometimes does not - full screen option is broken - if you switch app to fullscreen (e.g. ctrl+maximize button) then you won't be able to return back, because the title does not popout on the upper edge

Build #652, 64 bit Designed for Windows 10 build 14393 Fixed optimization of overlapped dirty regions Fixed data sharing between more drawings in one pass Includes new experimental ModernFrame.dll

The real reason is that he does not use Aero Glass compatible with Win10 build 14393.

RoundRectRadius does not work correctly since Windows 10, because the frame is not composed from one rectangle (which can be made rectangular) but from several rectangles. If you see set the radius too high, one rectangle won't visually continue to the second one.

I can confirm this bug even in build 10586 when modern app is in the background. This seems apply not only for Start menu but for any larger glass area. Could you test what happens with registry settings GlassSafetyZoneMode (DWORD in DWM key) set to 1 ?

yes, I will update it when I'm 100% sure with the state.

drakulyboy: yes, it will be there but I cannot say when, because 32-builds are pain in the a**. They contain a lot of complications which are more difficult to deal with.