Jump to content

Aero Glass for Win8.1 RTM RC3


Recommended Posts


This is the verbose debug build: http://glass8.berlios.de/stuff/DWMGlassVerbose.7z

NoelC: could you use this build a provide debug log when custom resource is not applied?

Hi BigMuscle, I did as you asked. Here's the log output from a bootup in which the themeatlas.png file was not loaded, then I closed the dwm.exe window and the themeatlas was successfully loaded.

http://Noel.ProDigitalSoftware.com/ForumPosts/Verbose_11-2-2013_01_debug.log

It doesn't seem particularly verbose, nor did I notice any slowness. Is there a trace level setup file you'd like me to change to increase the trace level?

-Noel

Link to comment
Share on other sites

it's ok, it logged what I needed and I think the problem is what I thought :w00t:

[0x36C] Loading settings: 0x00007FF7388D41D0 (0x00000000000003EC)
[0x3E4] Atlas resource loading (custom: )

Someone here already suggested adding timestamps to logs so I should really do it. But now it looks that settings and theme were loaded at the same time so it is just race condition when it asks for CustomThemeResource. I guess putting the settings into HKLM will work.

Link to comment
Share on other sites

it's ok, it logged what I needed and I think the problem is what I thought :w00t:

Someone here already suggested adding timestamps to logs so I should really do it. But now it looks that settings and theme were loaded at the same time so it is just race condition when it asks for CustomThemeResource. I guess putting the settings into HKLM will work.

Glad to help. My system's timing may be different than others because it's running from a fast SSD array, so lots of things can happen in a very short time.

I've put the CustomThemeResource string value in the HKLM path here:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM] "CustomThemeResource"="C:\\BIN\\themeatlas.png"

Confirmed: With this change it successfully loads the themeatlas.png consistently at bootup (5 times out of 5 boots) with the non-verbose beta 3 build. Thanks!

-Noel

Link to comment
Share on other sites

I made a batch file that can be quickly installed Aero Glass Beta 2, only the Aero81.7z files, extract to D: \ Aero81 (no folder please create), execute Windows 8.1 Aero Glass (x64) ENG.bat can be installed. I used Google Translate, if grammatical errors, sorry

Fix file https://drive.google.com/file/d/0B5lpnnM9IzikZE5BZjg1S2lYRmM/edit?usp=sharing

downlord:https://drive.google.com/file/d/0B5lpnnM9IzikWnJuNmRsY2pkTGM/edit?usp=sharinghttps://drive.google.com/file/d/0B5lpnnM9IzikWnJuNmRsY2pkTGM/edit?usp=sharing

Edited by CasparWindows
Link to comment
Share on other sites

Not that I'm complaining, but I'd like to report a BUG.

When spanning two monitors, when Explorer throws up a dialog box, it pop's up right in the middle of the two displays as if it's centered as one big display instead of poping up in the center of the active display, so half the window is on one monitor and the other half is on the other monitor.

Minor, but worth mentioning.

Edited by scanman1
Link to comment
Share on other sites

Not that I'm complaining, but I'd like to report a BUG.

When spanning two monitors, when Explorer throws up a dialog box, it pop's up right in the middle of the two displays as if it's centered as one big display instead of poping up in the center of the active display, so half the window is on one monitor and the other half is on the other monitor.

Minor, but wirth mentioning.

i had that happen several times before i had even downloaded aeroglass, thats an explorer bug, i suggest reporting it to MS.

Link to comment
Share on other sites

@bigmuscle

When the video window (by using DxVA2 acceleration) is across 2 monitors boundary (please see pic below), the dwm.exe process will eat 12% CPU of the Intel 2600k quad core. When the video window is within the main monitor, the dwm.exe only uses 1% CPU. Please check.

I'm using AMD 7750 GPU with latest 13.11b Catalyst on 64-bit Win 8.1 RTM. And AeroGlass beta3.

PS. This will also cause above issue when the video is in fullscreen mode, which consumes 25w more power..

@bigmuscle and @MagicAndre1981

I caught the DWMTrace.etl and uploaded to below site:

http://pan.baidu.com/s/1eOHPU

Thanks much!

the high CPU usage comes from a sleep (KernelBase.dll!SleepEx, ntdll.dll!NtDelayExecution). The Glass DLL is not shown in the callstack. The dwmglass.dll only uses 0.02% of the CPU.

01_DWM_Sleep.png

The dvbviewer.exe hogs the GPU most:

02_GPU_usage.png

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...