> I had the same problem yesterday… I spent like an hour trying to update my video card > driver, update directx, change mame64.exe version… until I realise that turning HLSL > on and off actually caused this error. > > You just have to copy the HLSL folder (version 202) over the old one and that's it…. > mine was maybe 199 or 200.
0202 comes with the new one, EVERY version of MAME comes with whatever the correct one is at the time of release.
You have to actively try to subvert the upgrade process in order to not get the correct one.
If people can't even update the HLSL folder properly I dread to think what the state of their other support folders is and MAME is only going to become more dependant on files that are not the .exe as time goes on. (I imagine we'll end up pulling all the dipswitch names and default values from external files at some point)
MAME IS NOT JUST AN EXE FILE
MAME HAS NOT JUST BEEN AN EXE FILE FOR NEARLY 20 YEARS
Index 
Flat 
Re: Apparent Direct 3d bug in mame64 202 (non patched)
Reply
