Thanks, but I don't think this has anything to do with MameUIFX. Whether I use a UI to input the values of GLSL shaders or not, doesn't make a difference.
I upgraded to Windows 10 because this thread gave me hope that I wouldn't see any setbacks in my emulation.
However, I can now see that using OpenGL and using GLSL shaders (where Main Mame Shader = "Lottes_CRT") do NOT seem to agree with Windows 10 in its present state. I keep getting the OpenGL error whenever I try to launch w/ Mame64.exe. And when I go to launch GTFore0# in MameUIFX with OpenGL settings on, the sound/gameplay behave as though its a DVD playing on X2 time.
Alternatively,
If I set video to Direct3D and try to use the HLSL filters, it gives me the Direct3D error I mentioned above and nothing ever boots in either Mame64.exe or MameUIFX.
Alternatively,
If I set video to OpenGL and no GLSL shaders (leave "Main Mame Shader" blank), the games boot fine in MameUIFX and Mame64, and the sound returns to normal in games like GTFore0#. But now the games look like garbage on my LED 1920x1080 monitor.
I tried installing DX9, but it prevents me from doing so because I have a "newer" (11.3) DX already installed.
|
Index 
Flat 
Re: Windows 10
Reply
Re: Windows 10
