Shaders for various emulators

[guest.r]

An issue has been opened with the slang version, maybe it's exactly the same as you describe:
https://github.com/libretro/slang-shaders/issues/100

OP's problems were mostly solved by a driver update to the latest nVidia drivers, the issue persists with the D3D12 backend though.

[Dr.Venom]

Originally Posted by guest.r

An issue has been opened with the slang version, maybe it's exactly the same as you describe:
https://github.com/libretro/slang-shaders/issues/100

OP's problems were mostly solved by a driver update to the latest nVidia drivers, the issue persists with the D3D12 backend though.

Thanks for the pointer. First I updated to the "Creator Ready Driver" (it's from march), and the slang output was still bugged. Then I updated to the "Game Ready Driver" (it's from May 5th) and yess it works fine now

Lagless vsync on WinUAE also still works as great as before, so all good here also.

[Dr.Venom]

Hi

Was trying out vertical games with both the MAME core and the Final Burn Neo core (fbneo_libretro.dll), which is an alternative to MAME, but am encountering an error with the Final Burn Neo core for vertical orientated games (all horizontal stuff is fine).

As an example, see below shot of Bombjack. There's a scaling issue with discoloring. Mostly it's a triangle divided by the diagonal of which one part gets discolored. In below shot there's an additional triangle..

I tried all possible options in the shader and RA video. Smart integer scaling in the shader does not help, nor does setting TATE mode. The only scaling option in RA that solves the issue is to set scaling to 1:1, but that gives wrong aspect.

When I disable the shader everything works correct, including all different scaling options in RA. Which makes me think it's a shader side issue?

Any idea?


P.S. The FB Neo core works the same as MAME, so you can load bombjack with it just as you'd do for the MAME core.


(click for large)

[guest.r]

When I disable the shader everything works correct, including all different scaling options in RA. Which makes me think it's a shader side issue?

Probably some coord manipulation by the core or RA while rotating stuff. I would rather say that some shaders are sensitive to this and crt-guest-dr-venom already has some mechanisms built in to prevent similar glitches. Since it works with other cores that are rotating the image i would leave it be for the present. Another good question is if same happens with crt-hyllian which also supports vertical scanlines?

Edit: moved my lazy **s and tested it myself, with the same core. Could not reproduce, unfortunatelly or fortunatelly.



With different aspect ratio:



Maybe it's another nVidia issue, could you test it with an AMD card? To make sure...

[Retro-Nerd]

@guest.r


Could you please check bsnes v108 Windows version? Somehow your CRT Trintron shader doesn't work properly anymore (v107 is still fine).


I mean these specifically.

[guest.r]

Originally Posted by Retro-Nerd

@guest.r


Could you please check bsnes v108 Windows version? Somehow your CRT Trintron shader doesn't work properly anymore (v107 is still fine).


I mean these specifically.

No crt shader that uses masks doesn't work properly, unless you use specific window sizes or the stretch mode. No way to fix it within shaders.

The author probably went for speed and used linear scaling so the shader isn't applied on left/right black borders.

If you have a decent machine it's best to stick with v107 for a while until this get's fixed. As i read the v108 changes are performance based, maybe with a little too much ambition enthusiasm.

[Retro-Nerd]

Yeah, i noticed it too that it works with "stretched" mode. Thanks for the info about the linear scaling method. Byuu drives me nuts. Every new release he changes things like that.