Hmm not sure on what mame is doing. Reshade dumps a reshade modified dxgi.dll into the directory of the mame.exe and if its using directx it should use that dll. the only time that wont work is if the dxgi.dll is 32bit and mame is 64bit or vice versa.
I have an idea. Why not just use the MAME Core from RetroArch and the slangp version of Sony Megatron Color Video Monitor?
2 Likes
Just got it working - change ‘video d3d’ to ‘video bgfx’ and add the line that @hunterk posted above i.e bgfx -bgfx_backend d3d11. Or do as @cyber said and just use retroarch’s mame.
2 Likes
I got it to work now, but some other things are now not entirely clear, chiefly that with the Megatron shader and autoHDR both enabled, the picture is incredibly desaturated, almost black and white, judging by these Final Fight screenshots. Disabling AutoHDR and switching to SDR in the Megatron shader params alleviates things considerably, but I should be able to use HDR methinks.
I
My monitor is an HDR capable monitor, but how would the monitor pick up that I’m displaying HDR content? With Retroarch you can enable HDR in RA, but I don’t use Retroarch for Mame. I like my high scores to actually save. So how can reshade tell my monitor to switch to HDR?
Got a few more questions, but will leave those for tomorrow.
1 Like
This almost certainly that the AutoHDR addon isnt working for some reason. Have you added it into reshade - can you see that its active? You will need to have HDR on in Windows - see display properties. We’ll get you there. You might need to edit the shader as well as reshade is not as good as retroarch in providing different resolution support but we can get to that after you fix the hdr problem.
Anyone else noticed an update to this shader has broken HDR with vulkan? The colours are washed out unless I select SDR in the parameters, yet the screen is running with full HDR brightness. DX11/12 are fine. Older megatron presets are working fine using vulkan so I compared files and the main difference is this: scale_type_x2 = “viewport” scale_x2 = “1.000000” scale_type_y2 = “viewport” scale_y2 = “1.000000”. I removed that section from my preset then HDR worked normally again… very odd.
3 Likes
Ok so thats really odd - I dont even remember adding that. Ill take a look and update/fix this. Thanks for letting me know!!!
This probably was @hunterk when he updated the repo presets so that viewport like passes were set to viewport. This is so that when someone uses the append action to append another preset on top.
That said, it’s not something that “should” affect anything, but obviously from your tests it does affect it.
2 Likes
Back again. yeah, so HDR was not enabled through Windows 11. I changed that now, I can select HDR on my monitor. Meanwhile, I confirm AutoHDR addon seems to function, at least it is there in reshade and I can select it and modify params. Unfortunately, things are still depressingly dim and non-vibrant. Like playing the Saving private Ryan version of Arcade games. 
TV HDR
Home tab reshade
Statistics tab reshade (Note it says D3D11 now under API), which is funny because in my mame ini under OSD Video options I only added bgfx under ‘video’ and none of that other stuff Hunterk mentioned yesterday, but my megatron shader no longer gave me a ‘failed to compile’ error so I guess all is well in that regard.
1 Like
Right so thats not the autohdr.addon you are looking at thats the autohdr.fx which is a shader you can use if you’re not using the SonyMegatron.fx. Remove the autohdr.fx and go and look at the ‘add-ons’ tab instead.
Hm, ok interesting. looks like this is where things may go awry. Please check the screenshot. !
I navigated to where my addon pack is where it says addon search path, then went back to home tab of reshade, saw autoHDR.fx and assumed that was the addon and all was ok. As you can see, there is nowhere in the addon tab where I can choose HDR even though I use reshade 5.8.0. addon version
Not sure where the issue is.
1 Like
Ok wow things are improving, in that same screenshot I now do see the HDR checkmark. !
But it is also giving me error loading addon message. 
here is the error from the log
I think I get it. my addon being used is the 64 bit version and that works, but in that directory there is also the 32 version and I guess that’s throwing up an error, but it’s an error which I assume has no impact whatsoever for me. Right?
1 Like
Hmm, I don’t think that would be me, since I only touched the base megatron preset and the crt-sony-megatron-aeg-CTV-4800-VT-hdr.slangp preset (for some reason lol; I probably did one and then looked at the number of others and was like ‘eff it’) and I only added the combined x+y scaling, not separated:
but in any event, yeah, dunno why that would have any effect 
3 Likes
Looks like you’re good! I can see the higher brightness in your shots. Id ignore the error as its just saying you are running a 64bit program and reshade failed to load the 32bit addon. So the big question: does it look better?
I think the base Megatron preset is included in all the rest of the presets. Not a problem though - the big question is why does this seemingly unrelated change break hdr on vulkan? When I get the chance Ill take a look and try and fix it as I guess its affecting other shaders in hdr as well.
3 Likes
No problem. Were you able to replicate the issue?
2 Likes
Sadly I haven’t had a chance yet but Ill keep you posted
1 Like
That’s a good question. It has improved visibly since the last time when colors were exceedingly washed out. But it’s not quite there yet and I’m not sure what’s causing it. The colors do not seem right, do not seem natural, do not seem punchy compared for instance to when I would use the CRT Royale shader via Reshade. The AutoHDR addon is enabled, I checked. Mind, I’ve got the Megatron shader params at default level. When I up saturation a bit for instance things do improve, but the general feeling that colors are where they should be isn’t there. It’s like there is a blue-ish tint to the colors or something like that and things still remain a bit on the muted side. My 4K monitor, the Aorus FV43U, is purported to be a HDR 1000 so I’m sure it’s more than capable. I’m not sure how to change the params. When I change them from HDR to SDR, things do improve, but I’d imagine that specific param to be set at ‘1’ which is the HDR setting. Any tips are welcome, I assumed the default setting would be just right.
1 Like
It’s normal to need some configuration. I think adjusting the paperwhite setting is often necessary on each display.
When it was washed out, that is how an HDR image looks on a display that doesn’t support HDR. I’m not saying your display doesn’t support it, but that the shader was probably doing the correct color profiling on its end but something else somewhere wasn’t holding up its end of the bargain.
3 Likes
So yes as @hunterK says once you have HDR working you have to calibrate it - sadly for HDR all displays are different as in they have different capabilities as no display meets the full spec yet. This is relatively trivial though: set your peak brightness in the shader to 1000 ie the max nits of your display (see rtings as a good source of this as manufacturers fib a bit). Then set your paper white value just go up and down until things look right. Id use the 240p test suite (its a rom file for most old consoles) to do this but its not essential.
1 Like