The NEW Build Your Own Arcade Controls
Software Support => GroovyMAME => Topic started by: oomek on April 09, 2018, 10:21:59 pm
-
This is just great. Why is Microsoft messing with the legacy runtimes is beyond my understanding.
After installing the Spring update of Windows 10 (build 17133.1) suddenly HLSL scanlines stopped working and now mame takes like 5 seconds to quit.
Does anyone else experience the same issues?
UPDATE:
Here are some tips I found that fix what Microsoft broke in 1803 version of Windows 10
- Scanlines not working: disable shader cache in the settings app of your graphics card
- Delay after exiting Groovy Mame: disable Everything in the Windows Settings->System->Focus Assist
- Freesync not working: Disable full-screen optimisations in the mame.exe Properties->Compatibility tab
-
no, but windows 10 has taken a liking to just randomly freezing (no BSOD or nothing just stops) and also not shutting down. (just logs off and then loads the desktop again)
everytime i fix it...they update and break the same things again.
about time to reload... it's like a 3 year old windows 7 install that was "upgraded" so it might be nice to ---meecrob--- it and start over.
-
I lost hlsl scanlines on my Win 10/AMD RX 480 system awhile back, but it's running 1709. I'm not sure when the issue started, but I thought it was after I put 1709 on. I can't blame 1709 specifically though, because I have a Win 10 VM at 1709, and hlsl scanlines are working fine there.
-
The scanlines issue was caused by broken shader cache after updating windows. Disabling shader cache fixed scanlines. BUT...that was before...now on the latest windows build 17134.5 the d3d9ex version of GM showed me a middle finger... jesus Microsoft, stop...just please...f%£$ stop!
Direct3D: Using Direct3D 9Ex
Physical width 2560, height 1080
Direct3D: Initialize
Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 980
Direct3D: Adapter has Vendor ID: 10DE and Device ID: 13C0
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Unable to create the Direct3D device (8876086A)
Unable to initialize Direct3D 9
Fatal error: Unable to complete window creation
-
I found a solution. You have to disable Focus Assist in the Settings->System. It solved also a delay when exitting GM.
-
I won't ask how in the world you found that.
-
I wasn’t able to get much sense of the misbehavior of the MsgWaitForMultipleObjects() function in AttractMode that started acting randomly and often not registering GM window close event, so I simply went through all recently added Windows 1803 „features” and found this :) I have now disabled windows update in my cab. I’m not going to update until I test it on my other pc. Enough is enough :)
-
Thanks for the follow-up. I'll try to keep that one in mind when 1803 hits me.
-
[For solutions go to first post]
-
I don't think it's a good idea to have your cab online and have it update windows as well... are you people using some sort of online feature?
I just connect mine to the router when I need to update files/games , it still uses a non-updated 2016 win7 OS.
-
My cab is also running games from steam.