[HOW TO] Transparency problems

[KillerJohn]

If you have transparency issues (black circles, etc) then follow this description (posted by a user):
Turned on aero and now work fine. Solution:
- Type the following text into the Start Search box: Aero
- Click on a search result listing under Control Panel group that named as the following: Find and fix problems with transparency and other visual effects
- An “Aero – Troubleshoot computer problems” wizard dialog will appear. Click on Next button.
- check the transparency settings: http://www.sevenforums.com/attachmen...pearance-1.jpg




Another post about transparency issue from a user:
I tried all the fixes in this thread. Eventually what I discovered is that my Windows Theme was the issue. I changed it from Basic to Win7 Theme and it fixed all the transparency issues (black circle while moving, blacked out mini map, etc). So if anyone else is in the same boat as me - try changing your windows theme under "personalize" in control panel. What your looking for is the annoying semi-transparent task bar and windows.




It looks like a good way to fix most of the Aero-related problems is to run the Windows Experience Index test: http://windows.microsoft.com/en-us/w...ndex=windows-8

[KillerJohn]

- copied my original post from turbohud.freeforums.net -

[mouaddib]

ty for your return nice day

[Jhoopes517]

Can't seem to get anything to work with Windows 10 and with the other forum down.... can't seem to find anything to try.

Help?

[RealGsus]

Edit: this is so the wrong thread to post it in... sorry, please delete.



Hey, I've head some trouble too, when I switched to Windows 10.

Here is what I did step by step

THuD Win10 Install/Warden Protection

• Create new user
  
  • Name: D3
  • Standard user, not an admin
• Edit settings of your THUD folder
  
  • Tab: Security
  • Edit... - Add user "D3"
  • deny everything
    
• Make a link to your "Diablo III Launcher.exe"
  
  • Edit settings of that link
  • Edit source and add runas /user:D3 /savecred in front so it looks like this:
    

    runas /user:D3 /savecred "C:\Program Files (x86)\Battle.net\Battle.net Launcher.exe"

• Allow your newly created user account (D3) access to the "Battle.net" and "Diablo 3 installation" folders.
  
• Allow your newly created user account (D3) access to the Diablo 3 preferences folder: "C:\Users\admin\Documents\Diablo III". Change admin to that user account you installed and first started Diablo 3 with (so probably your standard user)

hope that helps

[Jhoopes517]

Hey, I've head some trouble too, when I switched to Windows 10.

Here is what I did step by step

THuD Win10 Install/Warden Protection

• Create new user
  
  • Name: D3
  • Standard user, not an admin
• Edit settings of your THUD folder
  
  • Tab: Security
  • Edit... - Add user "D3"
  • deny everything
    
• Make a link to your "Diablo III Launcher.exe"
  
  • Edit settings of that link
  • Edit source and add runas /user3 /savecred in front so it looks like this:
    

    runas /user:D3 /savecred "C:\Program Files (x86)\Battle.net\Battle.net Launcher.exe"

• Allow your newly created user account (D3) access to the "Battle.net" and "Diablo 3 installation" folders.
  
• Allow your newly created user account (D3) access to the Diablo 3 preferences folder: "C:\Users\admin\Documents\Diablo III". Change admin to that user account you installed and first started Diablo 3 with (so probably your standard user)

hope that helps

Followed that and tried the other way from the enable warden protection and no go. It runs perfectly fine in starting town but once I leave or TP anywhere, black spots.

[KillerJohn]

how the hell is warden protection related to transparency??? guys...

[Jhoopes517]

how the hell is warden protection related to transparency??? guys...

I didn't think it did but I was going with suggestions.

Changed themes around and still couldn't find a way to make the black circles or map go away.

[itsmylife]

You should use the official W 10 version.

Previews seem to have problems with dx trasparency. There were some posts on the old forum talking about it.

[Jhoopes517]

You should use the official W 10 version.

Previews seem to have problems with dx trasparency. There were some posts on the old forum talking about it.

You mean like the insider previews? Ahh. I didn't even think to mention that I am running that. So, revert to Windows 10 proper and see what's up?

[JackCeparou]

You mean like the insider previews? Ahh. I didn't even think to mention that I am running that. So, revert to Windows 10 proper and see what's up?

Yep, for whatever reason i can't figure, insider builds seems to raise this transparency issues.

[Jhoopes517]

Yep, for whatever reason i can't figure, insider builds seems to raise this transparency issues.

Just finished re-installing Windows 10 proper. Gonna give it a go. Will update post with results.

EDIT: And that did it! Thank you so much for the heads up!

[Joco1114]

Yep, for whatever reason i can't figure, insider builds seems to raise this transparency issues.

Yep, Windows 10 Insider previews can't handle transparency. It's interesting, I didn't noticed problems with other programs. If KJ needs we can test it out...

J

[CaptainDesu]

Aww that transparency. Been using insider preview since it became available and never gon any problems. Switched to install release candidate builds only when they added it. Got that win 10 creators udpate and now have transparancy bug. Is that cuz of some improved personalization they made? Do i just revert update or wait like 10 days till its release?

[VBpb]

Aww that transparency. Been using insider preview since it became available and never gon any problems. Switched to install release candidate builds only when they added it. Got that win 10 creators udpate and now have transparancy bug. Is that cuz of some improved personalization they made? Do i just revert update or wait like 10 days till its release?

I would be surprised if the official release of the creators update fixes the problem for us. All of the builds that have been available in the slow ring for the past couple months have had this bug. But here's hoping! It has been discussed before, but the only way to fix this on your own is to roll back to an earlier build.