Jump to content

Tusticles

Member
  • Posts

    320
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Italy

Everything posted by Tusticles

  1. I had that exact problem in 0.9. But RC0 fixed that problem on my machine. Man, it was annoying. On about:Tabs it is normal
  2. Opacity setting does nothing. you can add a new option, "Color Intensity"
  3. I also have a bad internet connection and I compressed the dump file to 19 mb from 120 mb
  4. When changing Color intensity in personalize menu these registry values are changed. ColorizationAfterglow ColorizationAfterglowBalance ColorizationBlurBalance ColorizationColor
  5. What values? from 0 to? Tried 0 but no changes.
  6. I;m talking about the registry setting, GlassTransparency.
  7. Yes, with the dll's released after RC0 + callBlurShapes set to 0x1. I already told you that. But I had to restart explorer to apply blur to starmenu and taskbar --edit-- Opacity setting is affected by callBlurShapes? Because I tried to change the opacity but nothing changes. or this setting was removed in RC0?
  8. using rc0 crashfix + callBlurShapes 0x1 works, why should I use HookFlag?
  9. 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. --edit-- Ops, I misunderstood, you can use teamviewer to test it yourself...
  10. Did you downloaded the minidump I posted? It shows me 0 downloads.
  11. Tried with all versions, 314.22, 320.00, no changes... No, this model doesn't support Optimus.
  12. Wtf, you know I always had problems related to performance but you don't know what configuration I have, I posted the specs a lot of times, it wasn't me who had problems, it was dwmglass, in RC0 the performance is improved a lot but there is the problem with the black screen. Ah and btw, I'm not the only one who had/have problems, there are some guys here with the same problem and many who downloaded the application but they didn't posted any debug files... ASUS G75VW Processor: Intel Core i7 3610QM Graphic: NVIDIA GeForce GTX 670M with 3GB GDDR5 VRAM Memory: 12 GB DDR3 1600 Storage: 750GB 7200 SSH
  13. 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, here is the dmp file before adding that reg value to registry http://www.mediafire.com/?7xm3delamv4a0k7
  14. Applied, black screen, pressed f11, waited a few minutes, tried ctrl, didn't worked, forced restart and returned to desktop holding ctrl key... debug_nofillpath.txt threads_nofillpath.txt
  15. Tried and again tried to do what you said, applied the debug version, to get the black screen I had to move a window over the taskbar, screen turned black, pressed f11 and saw the mouse pointer flickering so I presume it started to download required files for debugging. You said dwm process will be restarted automatically after a while but the screen remained black for more than 30 minutes then I decided to restart manually.... I hope thee debug files will tell you something dbghelp_debug.txt dbghelp_threads.txt
  16. Read the previous pages, lol. Btw, bigmuscle, tried what you gave me, a thread file was created but ctrl button didn't worked so I manually restarted. I'll try again.
  17. Ok, tried rc0 with callBlurShapes, black screen after applying then held ctrl button for a long time and it returned to desktop, ah, and glass was still active. see debug_rc0_callBlurShapes.txt --edit-- tried again rc0, this time when pressed the apply button in AGTweaker it worked then pressed apply button again and black screen occured. see debug_rc0_callBlurShapes2.txt --edit-- Man, I have no idea what have you done but 0.9 is optimized, Is smooth on all p-states :D , let's hope it stays like this. debug_rc0_callBlurShapes.txt debug_rc0_callBlurShapes2.txt
  18. Yes, tried this registry setting with rc0 crashfix and it worked, auto device future level, blur was not applied on taskbar and startmenu but restarting explorer will fix it, no crash when restarting explorer debug_crashfix_callBlurShapes.txt
  19. Yes, it worked/is working, no native blur enabled, I don't even have the key in registry.
  20. Yes, but I don't see why would that be a problem, 0.9 worked fine. Btw I tried again and the crashfix you uploaded does the same thing, black screen when is applied, sometimes the black screen occurs after a few seconds, sometimes it stays active and I have time to restart explorer, after restarting explorer again our friend, the black screen. here is another log... crashfix_debug2.txt
  21. Transparency applied only on windows borders, no blur on taskbar and startmenu, then I restarted explorer and again, black screen. forced restarted and returned to desktop holding ctrl key crashfix_debug.txt
  22. Tried again and got black screen instantly after applying, this time ctrl key didn't worked. forced restart and returned to desktop holding ctrl key fifth_time_applied.txt
  23. Wow, I held down the button for 40 seconds or so and nothing happened then I started to tap the key and returned to desktop miraculously. This time a crash log was created. fourth_time_applied.txt crash_fourth_time_applied.txt
×
×
  • Create New...