Noticed another small problem. When I launch a MESS console system with an image attached, MAMEUI creates a default ini for that system based on MAME.ini.
What this means is I launch SNES, with ssridersu attached, and instead of it just reading MAME.ini and RASTER.ini and coming up with a raster HLSL display, it instead copies MAME.ini to SNES.ini and creates a bottom-level .ini that overrides everything.
On my system, MAME.ini defaults to HLSL off, and RASTER.ini changes that to HLSL on. So because it's creating a game-level .ini file based on MAME, I get no HLSL.
The inheritance works fine in official MAME. Inheritance also works fine with roms that don't have an image attached (tested with 005, it worked). But when I attach an image via "mount item" in "media view," MAMEUI creates the ini file.
The obvious and easy workaround is just to find SNES.ini after it is created and edit it to "hlsl_enable = 1," but MAMEUI should do inheritance consistent with baseline MAME. It shouldn't be creating the .ini file at all unless I change the game specific properties or the driver properties.
EDIT: Workaround doesn't work. MAMEUI overwrites the existing SNES.ini file. It only works the first time you do it.
Edited by Zaghadka (08/31/17 06:08 PM)
|
Previous 
Index 
Next 
Flat 
Re: Something is wrong with 0.189
Reply
