• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Gabe

Profile Information

  • OS
    Windows 8 x64
  1. RC1 seems to be working perfectly here, too. Windows Mobility Center only acts up when I apply the "Default" custom theme resource.
  2. Yes, there is no native blur now. Why? I said it million-times that this mode is not supposed to be used at all and that all versions are intended for testing only. So what is the purpose of your testing when you disable the code to test? Good. I didn't like people whining about it all the time either. Performance is fine now regardless. My only problem is that the GPU does not ramp up in "balanced" or "power saving" mode (and the respective Intel graphics settings associated with these default power profiles), leading to single-digit framerates when moving some windows. This is probably because the HD 3000 in "power save" is too weak, especially when pushing FHD resolution. In Windows 7, a combination of the native dwm blurring and smart GPU ramping led to butter-smooth motion all the time. I personally run my laptop in maximum performance when plugged in and glass off when on battery anyway (the same as on Windows 7), so this is a non-issue to me.
  3. Was native blur removed in this version? It doesn't seem to have the speed or artifacts associated with the one in 0.8-0.90. Also, wanted to point out a typo in the warning message. "ON" should be "AT" because the expression is "AT YOUR OWN RISK."
  4. What is your GPU and your graphics driver version? Have you tried upgrading to the latest drivers? Oh I am with the latest drivers No doubt about that! GTX570 with 320.00 drivers. Haha, me too! At least, I was. The 320 beta turned out to have a huge number of problems and glitches in everyday (non-gaming) use. Check out the release thread on Guru3D -- it's horrifying. I also experienced some crashes and graphics corruption -- and that was before I ever used AG. But if the drivers are fine for you, so be it -- we can probably rule that out. I actually have Optimus so the HD 3000 handles the GUI lifting. What intrigues me is the fact that the artifacts cannot be captured in screenshots. This leads me to accuse the driver's post-processing. Check that FXAA is disabled globally, as well as both "optimization" settings in the control panel. In other news, I had the "black glass on restart" issue others are mentioning. Only ever had it on 0.9. How strange! Running AGTweaker to "re-apply" the dll fixed the issues. Any reports I can provide?
  5. I just noticed this. There's usually supposed to be a lightening behind window titles, but these two apps don't show it. How interesting. This means if a WordPad or Explorer titlebar is placed over a darker background in some color combinations, their titles pretty much disappear since they are indistinguishable from the background.
  6. What is your GPU and your graphics driver version? Have you tried upgrading to the latest drivers?
  7. I would like to report that Dx10.1 (and therefore autodetect as well) works again with my HD 3000 chipset. It worked in 0.7 and now in 0.9, but not 0.8. Great progress! I have not tried Swatches because I initially did not know what they were...heh
  8. I found a way to make the bug less random. Try using a custom theme resource (like the "default" one that comes with AGTweaker). Then the bug will show up 100% of the time. Otherwise, you are correct in that it seems to be a bit random. I also wanted to confirm that guy's report a few pages back about not getting DirectX 10 working on 0.8. When I downgraded to 0.7, DX10 started working perfectly. I tried it with and without AGTweaker as well -- for me, DX10 works only with 0.7. I have an Intel HD 3000. Autodetect detects DX10 regardless of version, which means autodetect worked with 0.7 but not with 0.8. What do I mean by "not work" in 0.8? I mean there is no blur or coloration, just completely transparent glass.
  9. I see. Must be Dell's fault then.
  10. I see this as the bug in the theme and not in the aeroglass utility. It's ported directly from my Windows 7 theme which does not have this issue so I don't think the issue is with my theme. Others are having a similar issue albeit with a hack workaround: http://vistastylebui...g10279#msg10279 Thanks Not sure what your problem is as you did not really explain it, if your referring to the non transparent top part of the jump list then I can say that I have not had this problem at all with aero glass from Big Muscle I have used D3D and D2D and both render fine with the themes that support it, just because it was ported directly from Windows 7 does not mean there might not be some problems, send me a link for the theme to test and I can tell you straight away if the problem is with the theme or not. Works fine here on default theme (I also turned on "thin edges" and custom theme resource "default", but works even if you don't).
  11. Okay. I am now re-reporting these glitches which can be reproduced without AGTweaker: I also want to stress that I only used AGTweaker in the first place because opacity was wrong by default (background windows appeared way too dark, and using AGTweaker to adjust opacity resolved this issue).
  12. Hi, just thought I'd share my experience. Version 0.85 (and 0.80), Intel HD 3000 (Sandy Bridge) x64. Default theme, AGTweaker used to modify settings. - "Autodetect" feature level gives me the bugged complete transparency. Anything above 9.3 does the same. Anything in the 11 series causes crash-loops I can only avert using the Ctrl method. - Changing the color of the window borders produces anomalous results if done from within the Windows Personalize tool while your Aero is running, because on restart of the system or the Aero module, the color is changed (darker on my system). - The opacity slider only affects background windows. The foreground Window's opacity is not noticeably altered with this slider at lower values, but the background windows become more transparent. At extremely high values, all transparency is eliminated in background and foreground windows. - The "blur" slider seems to increase brightness of the foreground window chrome (and opacity, though as a cause or effect I am uncertain). Values up to around 100 make the foreground chrome extremely bright against all background patterns, extremely low values make the glass very dark, and values higher than 100 do not affect the brightness; they merely cause all translucency to stop. - Windows Mobility Center still displays inappropriate transparency. I cannot speculate whose code is at fault; it could be Microsoft's (also arguably to blame for the lack of Aero in the first place, but I digress), yours, or Intel's (driver)...or a healthy combination of them.