> Editing related BGFX files is easy. You simply edit the parameters in .json files
> (mame>bgfx>effects).
Says you! I gave up honestly, couldn't relate to what I was actually doing and having to set-try-goback-set-try-goback-set-try-etc a hundred times and still not getting the look I wanted tired me away from the thing. I use d3d and the raster.ini, easier, faster less trouble.
> Slider change saves, where always problematic. It was the first feature that was
> cutoff after initial release of HLSL.
Yet editing with sliders is the best thing, and having those settings save directly is what everyone expects in the end, no need to edit files manually that's why RA's shader systerm is popular even if it's badly made.
I guess if that's not implemented in MAME yet is because it's a big deal technically speaking to make that work right.
> I believe that the anikom15 changes, where a first step to enable HDR in MAME, but it
> was never finished. So we are left with something, that looks more worse then before
> and with parameters that have no real meaning in current state.
Can't say I have noticed since I always start from a more or less cleaned up raster.ini, basically copying most default values from the mame.ini (esp the colors-related)
And I don't use all HLSL effects.
Again I might be wrong and misunderstanding your point, but I think the problem is that MAME is delivered with unwanted setting by default instead of the most neutral, both in d3d and bgfx, and that's what we see when activating it.
> the fact that Retroarch offers barely better shaders.
Ouch er, I wouldn't say that, there's nothing as great as Royale yet for instance. Rather what's in MAME now is decent enough, but I'm sure there will be more in the future anyway.
> MAME isn't about playing the games anyway.
|
Index 
Flat 
Re: HLSL changes by anikom15
Reply
