MAME not working with HLSL

[Dogway]

Hello, running this simple line doesn't work with MAME.

Code: Select all

D:\HyperSpin Backup\Emulators\PCB MAME\MamePlus_v0.153r5133\mame64.exe" 88games.zip -hlsl_enable -rompath "E:\HyperSpin\ROMS\PCB MAME

if I remove -hlsl_enable it does, but I don't know why. It's not with all games.
The version of MAME is a compiled one called; MAME .153 x64 NoNag+HiScore+NeoGeoXtra+Autofire+NeoGeoOverclock+DirectInput.exe
And I use the modded post.fx, but also tried with the original without success, and d3d and gdi.

This is the error I get:



This is my mame.ini: http://pastebin.com/a7AsDHj4

[austere]

Please state your system specification including your graphics card make and model number along with its driver revision.

[Dogway]

Win7 Ultimate 64bit SP1
EVGA GTX 750 Ti SC (02G-P4-3753-KR)
Driver 337.88

Other i5-4670K (not OC) on Gryphon z87 board.

I also included mame64 on the nvidia control panel, and set it to max performance.

[Ixmucane2]

Please try the official MAME binaries at http://www.mamedev.org/release.html; unofficial variants might have extra bugs along with extra features.
Also, do you recall when did it stop working (MAME updates vs. drivers and software updates)? Do you have a working configuration, maybe without shaders? Do you use a frontend?

[Dogway]

Works now, not sure what has changed, but definitely after using the vanilla build.

Initially did run this and didn't work:
"D:\HyperSpin Backup\Emulators\PCB MAME\MamePlus_v0.153r5133\mame64.exe" 88games.zip -hlsl_enable -rompath "E:\HyperSpin\ROMS\PCB MAME"

Then added the new official mame64.exe and loaded the same game from HyperSpin.
Took it out, and repeated the same with my "faulty" mame64.exe, and now it loads the same game, and also others I was having issues with.

Again, repeated my initial command, and this time worked:
"D:\HyperSpin Backup\Emulators\PCB MAME\MamePlus_v0.153r5133\mame64.exe" 88games.zip -hlsl_enable -rompath "E:\HyperSpin\ROMS\PCB MAME"

So I can only think official build changed something along the way to its working state, I really would have wanted to know what is mame64.exe supposed to touch/change. I might give procmon a twirl to check, but I'm not sure where to look really.

edit: I think I'll be keeping an official build close by for these cases...

[Ixmucane2]

You probably overwrote a bad configuration file. You were lucky, but blindly overwriting files is dangerous.

I have a habit of extracting new Mame binaries and accessory files into new directories and merging them carefully with my real Mame installation directory, selecting the best or newest version of each file and occasionally renaming files to keep them around (e.g. obsolete/replaced dot mask images) or merging different versions of one file (typically my own customizations and new entries in the main configuration files).

I use Beyond Compare (http://www.scootersoftware.com/) but WinMerge (http://winmerge.org/) is free and almost as good.