Mame HLSL

Myrddin

If I make changes to the way a game looks in Mame, via the tab->slider controls menu, I presume this then creates a dedicated cfg file for the hlsl effects for that specific game? I can't find such a config file anywhere though, as I'd like to apply the changes made to ALL games, not just one in particular - any ideas how it can be done?

Star Lord

It's in the mame.cfg file as far as I can remember... ?

LoGiE

From what I can remember the defaults are in mame.cfg unless another config file is present <rom_name>.cfg

TechnoFreek

I think I read that in the latest version of mame (162) the default hlsl settings have been adjusted considerably to better match a crt and scanlines without and fiddling required.

Myrddin

I can find the global HLSL settings, they're in the ini folder. However, if I change the settings for a specific game, I can't find where that individual games settings have been stored I want to copy the settings, & paste them into the global ini file, but can't find game specific hlsl configs....

Myrddin

Seems this is a known 'thing'. I have to write down the numbers from the slider screen, & manually input them into the mame.ini :rolleyes: http://www.mameworld.info/ubbthreads/showflat.php?Cat=&Number=323630&page=16&view=expanded&sb=5&o=&vc=1

PaulPriest

Note that there's always been this internal conflict in MAME/MESS.
* The .ini system allows for cascading options and overrides: mame.ini, horizont.ini/vertical.ini, arcade.ini, [driversource].ini, [parentgame].ini, [clonegame].ini.
* The internal settings for e.g. controls are explicitly set globally (same scope as mame.ini), or per-clone (with no support for sharing between parent/clone - in many cases they have different controls anyway)
* Frontends can either configure the *.ini files (Emuloader-style), and allow MAME to cascade, or effecitvely rewrite a single mame.ini file, or control it entirely via overriding the commandline options (QMC2 style) and store the settings as they see fit in an internal db. Technically, if you enabled the HHTP frontend, it could even update them at runtime in some cases.

As a result of the above - it's not as simple as saying - I wish MAME would save my settings. Should it do it at the game level, global, or something inbetween. What if you updated a setting that was already set at the sourcefile level, should that be applied ot the sourcefile? The global? The individual game?

I'm a proponent of the static configuration (I added most of the cascading .ini options originally), although an option to persist settings automatically at the most fine-grained level (e.g. the individual sets) would be welcome for things with internal UI.

Myrddin

PaulPriest wrote: »

As a result of the above - it's not as simple as saying - I wish MAME would save my settings. Should it do it at the game level, global, or something inbetween. What if you updated a setting that was already set at the sourcefile level, should that be applied ot the sourcefile? The global? The individual game?

Cheers for the above. My slider settings are actually being saved (though where that is I don't know), but they're being saved on a per game basis. What I want to do is apply the changes I've made with the sliders (in one game) - globally, and not solely for that game if you get me. I'm running MameUI x64 through Hyperspin if that changes anything.