Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Aero Glass for Win8 RC4


  • This topic is locked This topic is locked
2630 replies to this topic

#551
MagicAndre1981

MagicAndre1981

    after Windows 7 GA still Vista lover :)

  • Patrons
  • 6,216 posts
  • Joined 28-August 05
  • OS:Windows 8 x64
  • Country: Country Flag

Donator

the Preview has an issue with the UAC prompts. In this case Aero Glass is not working correctly.
Posted Image


How to remove advertisement from MSFN

#552
pengipete

pengipete

    Junior

  • Member
  • Pip
  • 70 posts
  • Joined 05-February 13
  • OS:Windows 8 x64
  • Country: Country Flag
Sorry to be a pain but you lost me completely :blushing:

What is "GlassColorization" - is it a registry value cos if it is, I don't have it in my registry?

Without any technical detail on how it works, can you say whether or not it's possible to have inactive window borders set to a colour other than the default grey when using the D3D mode. I don't mind how it works - I just want to know if it's possible.

I'm really confused because you seem to be saying that the inactive border should already be "tinted" with the colour of the active borders when using Aero Glass in D3D but I am seeing absolutely no colouring - even tested that by dramatically changing border colours, taking screen grabs then checking the inactive border colours in photoshop - they are identical.

At the moment, if I use Aero Glass in the D3D mode, I can only have grey inactive borders - always and only exactly the same "dead man's skin" shade of grey and that doesn't change no matter what I do with the active window border colour. If I use the D2D setting in your app, I can have the inactive borders any colour I like - so it seems to me that using D3D is a step backwards - it may be technically more "better" but it seems that it lsoes a valuable feature. If you are planning on dropping the D2D method, it will make the app less useful for me as changing the inactive border colour is at least as important as having transparency.

#553
bigmuscle

bigmuscle

    Aero Glass for Win8 developer

  • Developer
  • 1,314 posts
  • Joined 18-August 12
  • OS:none specified
  • Country: Country Flag

Donator

Sorry for confusion. I meant GlassTransparency settings. And yes, it is possible to colorize inactive borders in Direct3D if you respect the rule I wrote above.

Attached Files


Aero Glass for Win8.x --> http://www.glass8.eu

#554
pengipete

pengipete

    Junior

  • Member
  • Pip
  • 70 posts
  • Joined 05-February 13
  • OS:Windows 8 x64
  • Country: Country Flag
I copied your registry settings exactly - and got completely transparent borders with no colour at all - and then I noticed that your window gadgets are not standard Windows 8 ones. Are you using a custom theme or gui - cos your settings simply don't work on my bog-standard W8.

#555
bigmuscle

bigmuscle

    Aero Glass for Win8 developer

  • Developer
  • 1,314 posts
  • Joined 18-August 12
  • OS:none specified
  • Country: Country Flag

Donator

Used theme does not influence it at all. It is just glyph which is placed over the blurred and colorized border. I just tried with default Win8 theme and no problem - the color is just bit more intensive.
Aero Glass for Win8.x --> http://www.glass8.eu

#556
pengipete

pengipete

    Junior

  • Member
  • Pip
  • 70 posts
  • Joined 05-February 13
  • OS:Windows 8 x64
  • Country: Country Flag
On the screen-grab of your registry values, you have GlassTransparency set to 0 but your window borders are mostly opaque. If I set GlassTransparency to zero and duplicate all of your other values, I get totally colourless, transparent windows with a slight blur - nothing even remotely like your screen-grab.

It's not helping that the information for each update is buried somewhere amongst 550 (and rising) posts but it seems that v0.5 should have a DWM entry in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM - but that "folder" doesn't exist in my registry. Is it something I have to create?

And what about the DWN registry "folder" that was in HKEY_USERS\.default - should that still be there or should we delete it now?

I should add that I've asked in the forum if anyone else is getting the inactive coloured borders (without additional apps, themes or hacks) and no-one has replied - hence asking you.

#557
stonyi1966

stonyi1966

    Newbie

  • Member
  • 23 posts
  • Joined 06-November 12
  • OS:Windows 8.1 x64
  • Country: Country Flag
v 0.5 works perfect, but it looks much better when I use the Release Preview Theme instead of Win 8 RTM's theme.

#558
puerto

puerto
  • Member
  • 3 posts
  • Joined 12-March 13
  • OS:Windows 8 x64
  • Country: Country Flag
Works great for me on one of my computers, and I love it :thumbup

On the other one, the screen goes black and then it brings me back to the login screen

I've included the debug file.

I'm on Windows 8 Pro 64 bit .. i7, plenty of RAM


Hopefully there's a fix for this :rolleyes:

Attached Files


Edited by puerto, 12 March 2013 - 08:02 PM.


#559
bigmuscle

bigmuscle

    Aero Glass for Win8 developer

  • Developer
  • 1,314 posts
  • Joined 18-August 12
  • OS:none specified
  • Country: Country Flag

Donator

On the screen-grab of your registry values, you have GlassTransparency set to 0 but your window borders are mostly opaque.

Because I use different theme resource which is not fully transparent as RTM theme. RTM theme looks like this
Attached File  screen.png   172.61KB   57 downloads

but it seems that v0.5 should have a DWM entry in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM - but that "folder" doesn't exist in my registry. Is it something I have to create?

no, colorization settings are stored in HKEY_CURRENT_USER

v 0.5 works perfect, but it looks much better when I use the Release Preview Theme instead of Win 8 RTM's theme.

yeah, it's true because RTM theme is totally transparent with thin line around the border. RP theme has semi-transparent texture in the border.

On the other one, the screen goes black and then it brings me back to the login screen

I've included the debug file.

It looks like device failed to be created in some cases. Could you try playing with DeviceFeatureLevel? Maybe, your card does not accept level 0x9100 correctly.
Aero Glass for Win8.x --> http://www.glass8.eu

#560
pengipete

pengipete

    Junior

  • Member
  • Pip
  • 70 posts
  • Joined 05-February 13
  • OS:Windows 8 x64
  • Country: Country Flag
Turns out that the lack of the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM entry was the problem - that "folder" and the entries it was supposed to contain had been created in HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\DWM for some reason - presumably when V0.5 was first run given that I know I've never created those keys anywhere.

Edit - seems that the entries in WoW6432Node are created by AGTweaker - but that's separate from the problem that the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM wasn't created in the first place.

Given that the dafault if to use D2D - which appears to be more "stable" for more people is it possible that there's a bug and that HKLM entry is not being created - resulting in everyone running in D2D without even realising it (as they must be if the HKLM keys are missing)?

Since no-one but you and I has actually said that they are testing D3D and inactive border colouring (and NOT using any non-standard themes or GUI patches), I can see how such a bug - if it exists - could go completely unnoticed. I also note that since V0.5 was released, there has been no further mention of problems relating to DeviceFeatureLevel settings - which may support the idea that everyone is actually running the app in D2D without even realising it.

I've drop a note to ORelio to warn that his AGTweaker app appears to be setting keys in the wrong part of the registry but that should only result in his app showing the wrong values - it wouldn't delete the correct HKLM folder and simply wouldn't send any of those values to Aero Glass.

Can someone please check to see if the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM entry in the registry exists - someone who has never manually created any such DWM "folders" and entries.

Edited by pengipete, 13 March 2013 - 06:58 AM.


#561
DosProbie

DosProbie

    MSFN Expert

  • MSFN Sponsor
  • 1,034 posts
  • Joined 16-October 12
  • OS:Windows 8.1 x64
  • Country: Country Flag

Donator

Turns out that the lack of the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM entry was the problem - that "folder" and the entries it was supposed to contain had been created in HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\DWM for some reason - presumably when V0.5 was first run given that I know I've never created those keys anywhere.

Edit - seems that the entries in WoW6432Node are created by AGTweaker - but that's separate from the problem that the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM wasn't created in the first place.

Given that the dafault if to use D2D - which appears to be more "stable" for more people is it possible that there's a bug and that HKLM entry is not being created - resulting in everyone running in D2D without even realising it (as they must be if the HKLM keys are missing)?

Since no-one but you and I has actually said that they are testing D3D and inactive border colouring (and NOT using any non-standard themes or GUI patches), I can see how such a bug - if it exists - could go completely unnoticed. I also note that since V0.5 was released, there has been no further mention of problems relating to DeviceFeatureLevel settings - which may support the idea that everyone is actually running the app in D2D without even realising it.

I've drop a note to ORelio to warn that his AGTweaker app appears to be setting keys in the wrong part of the registry but that should only result in his app showing the wrong values - it wouldn't delete the correct HKLM folder and simply wouldn't send any of those values to Aero Glass.

Can someone please check to see if the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM entry in the registry exists - someone who has never manually created any such DWM "folders" and entries.


You have the wrong registry path key should be: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DWM]
There is also 2 more key/s : [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\DWM], [HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM]
and for 64-bit at: [HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Windows\DWM]

#562
pengipete

pengipete

    Junior

  • Member
  • Pip
  • 70 posts
  • Joined 05-February 13
  • OS:Windows 8 x64
  • Country: Country Flag

You have the wrong registry path key should be: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DWM]
There is also 2 more key/s : [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\DWM], [HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM]
and for 64-bit at: [HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Windows\DWM]


I cut and pasted "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM" directly from BigMuscle's post #506 - the one in which he announced V0.5 and listed the keys.

The key you suggested - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DWM - does not exist on my laptop

The key HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Windows\DWM was not created when I ran Aero Glass - it only appeared after running AGTweaker and the settings for D3D it contained were not applied to Aero Glass.

#563
bigmuscle

bigmuscle

    Aero Glass for Win8 developer

  • Developer
  • 1,314 posts
  • Joined 18-August 12
  • OS:none specified
  • Country: Country Flag

Donator

Turns out that the lack of the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM entry was the problem - that "folder" and the entries it was supposed to contain had been created in HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\DWM for some reason - presumably when V0.5 was first run given that I know I've never created those keys anywhere.

Edit - seems that the entries in WoW6432Node are created by AGTweaker - but that's separate from the problem that the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM wasn't created in the first place.

It seems that you miss the basic thing here. AeroGlass utility does not create any registry key nor modify any other system settings and it is not intended to do so. It only reads the values which you create on your own. Since the registry settings is still current development issue I have not put them in the first post but they can be found near last changelog only.

Also, there is no reason why the settings should be read from Wow6432Node because this utility is fully 64-bit. The global settings is read from HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM and the local (colorization) settings is read from HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM. (some settings can also work in other keys such as HKEY_USERS\.default etc. but it is only due to fallback when normal values has not been not found and nobody should modify these keys at all so ignore this small note :-) )

Since no-one but you and I has actually said that they are testing D3D and inactive border colouring (and NOT using any non-standard themes or GUI patches), I can see how such a bug - if it exists - could go completely unnoticed. I also note that since V0.5 was released, there has been no further mention of problems relating to DeviceFeatureLevel settings - which may support the idea that everyone is actually running the app in D2D without even realising it.

DeviceFeatureLevel has nothing to do whether blur effect is rendered via Direct3D or Direct2D. It states the graphics device compatibility mode which DWM uses (just because it is always Direct3D - also Direct2D is just an API layer above Direct3D 11). In 0.5, I put the default value to 0x9100 (if settings is not found in the registry) thus nobody complains about this settings now. My goal is to make everything work with native device level.
Aero Glass for Win8.x --> http://www.glass8.eu

#564
MarcOo

MarcOo
  • Member
  • 3 posts
  • Joined 12-March 13
  • OS:Windows 8 x64
  • Country: Country Flag
Works very well.
Few suggestions : you should remove the warning windows (use at your own risk) and put this message in a readme for example. Is it possible to run the programme in background in order to have no longer its presence in the taskbar or put it with the hidden icons ?

Each time I plug a usb device, the console (i always reduce) pop up. Is it normal ?

#565
AlexKven

AlexKven

    Junior

  • Member
  • Pip
  • 89 posts
  • Joined 03-February 13
  • OS:Windows 8 x64
  • Country: Country Flag

Works very well.
Few suggestions : you should remove the warning windows (use at your own risk) and put this message in a readme for example. Is it possible to run the programme in background in order to have no longer its presence in the taskbar or put it with the hidden icons ?

Each time I plug a usb device, the console (i always reduce) pop up. Is it normal ?


He says that he will not remove these annoyances until it is out of preview stage. The console window popping up seems to be a new annoyance. It sounds like that he really, really doesn't want us using this all the time while it's in preview.

#566
pengipete

pengipete

    Junior

  • Member
  • Pip
  • 70 posts
  • Joined 05-February 13
  • OS:Windows 8 x64
  • Country: Country Flag
That's precisely what I was trying to tell you - the registry keys HAVE been crreated in WOW6432Node - and it appears they are created there by AGTweaker because I completely removed them and they stayed deleted until I ran AGTweaker again - and then they reappeared. I ran AGTweaker and it appeared to allow me to use 9200 & 9300 - which never worked for me in your previous betas BUT inn reality, it Aero Glass wasn't using those values when using D3D - it was always running at 9100 - so anyone beta testing and using AGTweaker will be erroneously reporting that it works with those settings.

Regarding "It only reads the values which you create on your own. Since the registry settings is still current development issue I have not put them in the first post but they can be found near last changelog" - are you saying that everyone here apart from me manually created the entire HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM "folder" and all of the keys in it - because it quite simply did not exist on my installation of Windows 8? Does that mean there is and always has been a problem with my installation - because I've had no problems with it at all - or did I just completely miss a step when running V0.5?

Please understand - I am NOT talking about blur or anything else when refering to those missing registry values in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM - I only discovered those keys were missing whilst trying to work out why I could not get coloured inactive borders BUT that is just coincidental - it caused me to discover the lack of the HKLM entries was stopping AG from working as expected - I've resolved that problem and am just trying to warn you that V0.5 does work but without those HKLM keys, it is only running with "safe defaults" - so the beta-testing is not actually testing anything..

I'm trying to get you to see that if Aero Glass relies on reading values in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM and that "folder" and the keys it is supposed to contain does not exist, the app will work to a certain extent but will not be working correctly. What features do work are the basic ones you've had since the first beta so anyone testing V0.5 is not really testing the latest changes you've made.

As you can see from post # 561, someone else is now saying that their registry keys - the ones which determine whether D3D is used and whether it's set to 9100, 9200 or 9300 - are in yet another location. Are you saying that Aero Glass will still work no matter where those keys are - or is that person not actually using the values they think they are whilst testing?

As you know, with no other values changed, the overall Aero Glass effect looks quite different if you switch between D2D and D3D. It was only after I found that the HKLM folder was absent and manually created it that I was able to see that I had, in fact, been using D2D. I'm suggesting that other people who have said that it works for them may actually be using D2D without realising it - so they are not actually testing the new/updated routines you've added.

Again, I'm asking if some of the other people testing this could please check their registry and make sure that they have the correct keys in ALL of the registry sections applicable. Aero Glass will work with some of them missing but it may not be doing exactly what they think it is - such as using 9100 when they think you've set it to 9300. If that is the case, it may appear stable but they aren't actually testing V0.5 - just using the basic DWM hook which has worked since V0.1.

#567
bigmuscle

bigmuscle

    Aero Glass for Win8 developer

  • Developer
  • 1,314 posts
  • Joined 18-August 12
  • OS:none specified
  • Country: Country Flag

Donator

It seems that you absolutely miss the point why any registry settings are there. Any registry key/value (and it pays for all cases, not only this utility) is intended for experienced users only and it should be touched only if you know what the key/value is intended to do. Application has hardcoded default values and does not rely on the existence of any key. When no registry setting is modified, then application works exactly as it is intended to work - so it is absolutely wrong statement that application "will not be working correctly" when any key/value does not exist.

Registry values under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM are there only for technical reason and they should not been touched at all if you don't know what it really does. Therefore, the key does not even exist in the default state. And there is absolutely no reason why this key should exist and why application should rely on its existence. And nobody ever said that this key is supposed to exist in default state. So again, if the key under HKLM does not exist, then this application works at its best... there are only certain special reasons why one should create this key and change the default settings. But I strongly say DON'T DO IT! And what more, don't change them via any external 3rd party application which probably touches totally wrong keys - and I won't provide any support if you use any "GUI application", because it is totally beyond the scope of my utility (just because the keys such as WOW6432Node have nothing to do with my work so it is only your responsibility if you manage to create them by whatever way)

All user customization settings are placed under HKEY_CURRENT_USER key. But again, it is still Windows registry, so you should not touch it if you don't know what the key/value does!

To DosProbie (post #561), I say again - there is no WOW6432Node supported by this utility. Also HKEY_USERS\.DEFAULT is valid only for pre-0.5 previews.
Aero Glass for Win8.x --> http://www.glass8.eu

#568
DosProbie

DosProbie

    MSFN Expert

  • MSFN Sponsor
  • 1,034 posts
  • Joined 16-October 12
  • OS:Windows 8.1 x64
  • Country: Country Flag

Donator

To DosProbie (post #561), I say again - there is no WOW6432Node supported by this utility. Also HKEY_USERS\.DEFAULT is valid only for pre-0.5 previews.

With this thread getting so large now (approaching 600 posts), It would be a good idea to include a Changelog from you of new previews,
including which reg key or keys are affected, should and should not exist with proper recommended settings etc.

#569
pengipete

pengipete

    Junior

  • Member
  • Pip
  • 70 posts
  • Joined 05-February 13
  • OS:Windows 8 x64
  • Country: Country Flag

To DosProbie (post #561), I say again - there is no WOW6432Node supported by this utility. Also HKEY_USERS\.DEFAULT is valid only for pre-0.5 previews.

With this thread getting so large now (approaching 600 posts), It would be a good idea to include a Changelog from you of new previews,
including which reg key or keys are affected, should and should not exist with proper recommended settings etc.


I've previously asked for that - and asked that they (and any future updates) be added to the first post - because they are nowdramatic spread throughout nearly 600 posts and the changes are quite dramatic at times.

#570
DosProbie

DosProbie

    MSFN Expert

  • MSFN Sponsor
  • 1,034 posts
  • Joined 16-October 12
  • OS:Windows 8.1 x64
  • Country: Country Flag

Donator

To DosProbie (post #561), I say again - there is no WOW6432Node supported by this utility. Also HKEY_USERS\.DEFAULT is valid only for pre-0.5 previews.

With this thread getting so large now (approaching 600 posts), It would be a good idea to include a Changelog from you of new previews,
including which reg key or keys are affected, should and should not exist with proper recommended settings etc.


I've previously asked for that - and asked that they (and any future updates) be added to the first post - because they are nowdramatic spread throughout nearly 600 posts and the changes are quite dramatic at times.


I feel your pain and a lot of others as well, and frankly I don't have the time to scroll thru almost 600 posts trying to find the "sweet spot" settings..When a few screen
shots and changelogs would keep us all up to date..B)

Edited by DosProbie, 13 March 2013 - 01:43 PM.


#571
pengipete

pengipete

    Junior

  • Member
  • Pip
  • 70 posts
  • Joined 05-February 13
  • OS:Windows 8 x64
  • Country: Country Flag
BigMuscle...

I think you are missing the point entirely.

You are asking people to BETA TEST your app - so you NEED them to mess around and see if there's anything they can do that will break it. If they are all running it with your default settings, they are not beta testing - they're just using it. The point is that your app is reading and using values which may or may not exist in the registry and if they don't exist, it runs at your "safe defaults". If those "safe defaults" are all you ever plan on using, there is no further need for beta testing - but if you are still trying to work out what works best or looking to develop futher, you need people to fiddle about. You have specified that those registry values exist and have even ASKED people to test them on more than one occasion - so I'm just trying to tell you that it's not possible to correctly beta-test an application when you can't test all of the possible variations and settings.

A prime example - the black screen that many people are reporting is usually avoided by using 9100 - but unless you have people willing to try the other values, you'll never know WHY that is causing what appears to be a more-or-less random and unpredictable problem. If you are leaving that at 9100, you should remove the setting from the registry rather than now saying that no-one should change it.

If changing a registry value that your app uses causes or highlights a problem, that's not a failure on the part of the beta-tester. Unless they are sticking in values that the operating system can't even handle, then the application needs to be able to deal with them. It may be okay for now to say something like "x is never more than 200" - but all it takes if for some external app or even Microsoft to make a small change and that value may suddenly be set to 201.

If all you want is for people to run your app and tell you that it doesn't simply crash when run, you shouldn't be listing the registry values it uses. If you list them - and even ask people to try changing them - you shouldn't be critical of those who try to help by testing every value and setting. It's also a bit unfair to assume that just because someone is not 100% clear on how a handful of regsistry values interact with your application (or DWM in general) that they are totally ignorant and shouldn't touch the registry.

#572
bigmuscle

bigmuscle

    Aero Glass for Win8 developer

  • Developer
  • 1,314 posts
  • Joined 18-August 12
  • OS:none specified
  • Country: Country Flag

Donator

Sorry, but you are probably in the wrong thread. This small piece of software never entered in betatesting state, it neither entered in the alphatesting stage. That's why I always highlight that each version is experimental preview only. It's purpose is not to test anything, it's purpose is not to hunt for bugs etc. and I have never said that (the only testing request was about GlassTransparency and BlurDeviation settings, not others!). The only purpose of this version was to show "hey, blur effect is possible and it may look like this!" and to show which direction it will take, and that's why the preview dialog will stay there. The registry setting is there only for a) HKCU for preview only - to show possible future features, B) HKLM if anyone experiences some serious problems... and yes, you are right, there is absolutely no reason to have any registry settings because believe it or not, the hardcoded values work really at its best (just because they are not hardcoded by me, but by DWM itself).

Also, the black screen problem has nothing to do with DeviceFeatureLevel, it is totally different problem. It is just limitation of the loader which is not possible to fix it (without "hardcoding" my library into system) and I already explained it.

I am not critical about changing registry settings. I am just critical that you change registry using some 3rd party application (which changes totally different keys) and then complain that my utility has a bug because it does not create key XYZ and thus the settings does not work.

DosProbie: as I have already said, the registry settings are not highlighted in the first topic just because it is temporary thing only. Settings such as DeviceFeatureLevel will be removed when I successfully fix the issue and it will use native level (i.e. 9100 for D3D 9.1 video card, a000 for D3D 10.0 video card, b000 for D3D 11.0 videocard etc.). It is only my good will that I added the settings to enable preview on unsupported videocards. Just a small example, there is tons of registry settings in Windows itself, keys nor values do not exist in the registry by default and you don't find any list of them - just because you are not intended to change them. There is also hidden MinFeatureLevel and MaxFeatureLevel directly in Direct3D library ;-)
Aero Glass for Win8.x --> http://www.glass8.eu

#573
stonyi1966

stonyi1966

    Newbie

  • Member
  • 23 posts
  • Joined 06-November 12
  • OS:Windows 8.1 x64
  • Country: Country Flag
I'm not sure if what I'm saying even matters, but if a person has a DX11 video card then it should work with DX11 registry setting. DX11 setting works the best on my system, and my system acts like the transparency was there from MS. I have no bugs or any other problems that I have seen as of yet.

#574
pengipete

pengipete

    Junior

  • Member
  • Pip
  • 70 posts
  • Joined 05-February 13
  • OS:Windows 8 x64
  • Country: Country Flag
I didn't "complaint that your program has a bug" - I reported something that wasn't working correctly on my pc and explained that I had found the reason for it.

The reason I mentioned AGTweaker is that a number of people reading this thread are likely to be using it and and if they are having problems with Aero Glass, it seemed sensible to tell them that the latest versions of both applications are not quite working in synch - so if someone tells you that "it's working perfectly at 9300 on my XYZ graphics card, that might not be true because they are actually running the default 9100 setting. That was nothing to do with "complaining" - it was to try to warn you that there could be bugs or problems you will never find because a lot of people are running at default settings without realising it - such as the 9100 value - and you've said several times that you'll be changing those in the final version. That makes it possible that people will be telling you that it works with such and such settings when, in reality, they are using totally different ones from what they think they are using.

I was just trying to help - reporting something that could result in you getting inaccurate feedback and maybe trusting something that has never actually been tested.

#575
puerto

puerto
  • Member
  • 3 posts
  • Joined 12-March 13
  • OS:Windows 8 x64
  • Country: Country Flag

It looks like device failed to be created in some cases. Could you try playing with DeviceFeatureLevel? Maybe, your card does not accept level 0x9100 correctly.



I changed the value of DeviceFeatureLevel to all of these (0x9200, 0x9300, 0xa000, 0xa100) and it didn't change anything.

Can you confirm the location of the entry? it was in HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\DWM

By the way, version 0.3 works nicely for that computer and without that entry in the registry

My graphic card is an ATI Radeon HD 4850

Here's another debug file with the test I did.

Thanks

Attached Files


Edited by puerto, 13 March 2013 - 07:14 PM.





6 user(s) are reading this topic

0 members, 6 guests, 0 anonymous users