Dolphin 5.0 Strange HUD problems with StarFox Adventures HUD losing texture and then

cammelspit

StarFox Adventures now has a bug where the HUD seems to lose texturing. It also freezes quite regularly now compared to the last time I played it. This video shows only a small snippet where it illustrates better than I could explain it words what exactly is happening. I have NOT had this problem the last few times I booted this game but have not done a proper bisection yet to determine what exact revision started having this problem. You can ignore the steam overlay, I use my Steam Controller exclusively now but I have tested this both with and without the steam overlay and the issue is completely unchanged, in case anyone was curious. The last time I booted this game was probably 1-2 months ago or maybe since Dolphin had corrupted my saves when we were having those strange GCI folder problems with WindWaker. It seems that it will happen when attacking and there is a fire in the scene. If a fire is not present I believe it does not do this. Any ideas?

My specs are as follows...

Cire i5 6600K @4.5Ghz | R9 380 4GB | Windows10 Pro x64 | 16GB DDR4 @3Ghz | Rev Dolphin 5.0 release

https://youtu.be/vEqph4BavWI

cammelspit · 06-26-2016, 08:03 AM #2

I did some more testing... So. It seems like it is some change in Dolphin at some point recently COMBINED with a change in the steam beta client. I recorded a 10-second FIFO log and it worked fine, this got me thinking it had to be happening after Dolphin did it's rendering but before it showed up on screen. The only thing I had going at this time that could cause this was the steam overlay. I turned it off and it still did it. I reverted back to the stable client and blamo, no glitch.

I then tried a random older REV of Dolphin and it worked perfectly even with the beta steam client.

I am using the Crimson 16.6.1, which is the latest AMD driver at this time. I have seen problems like this with OpenGL stuff but never with D3D at all. nVidia cards don't have the OpenGL problems AMD cards do but this is the first time I have seen this sort of thing in D3D. I will now report this in the steam beta client forum. It still makes me wonder why disabling the overlay didn't fix it and it's ONLY the beta client itself that is causing it and only with the 5.0 release and not a few weeks old dev release.