If it's higher than that, it will assume it is interlaced and the scanlines will be jumping up and down, because it will be trying to emulate the correct field locations of an interlaced signal on a real CRT. If it's tiny like 320x240, it won't think the signal is interlaced, and will not flicker. Depends on the resolution of the system you emulate. Just a few examples of googling "crt royale flickering". I also suggest saving your modifications as a "global" or "core-specific" preset in RetroArch via its shader menu, so that CRT-Royale always loads with those fixed settings. Then just enter the in-app shader properties and disable interlace-detection there.
#Bsnes hd download update
And update the RetroArch shaders so that you have the latest shader version with this improvement. You must, as mentioned above, run the Vulkan output renderer so that you can use slang shaders. Hizzlekizzle has updated the slang shader to make the interlacing detection into a runtime option, so that we can set it inside our Shader Properties in RetroArch's GUI instead of editing config files. The others (CG or GLSL) don't have any config files so the issue can't (or would be very hard) be fixed there.Įdit 3: Great news in the discussion below. So you should be using the "pure" BSNES core (the one without any special modifiers after the name) the correct core is currently named Nintendo - SNES / SFC (bsnes), which will give you the latest bsnes!Įdit 2: It was clarified below that to be able to edit the interlace_detect value in user-settings.h, you need to be using the slang (Vulkan output renderer) version of the CRT-Royale shader.
The evolution was bsnes -> higan (rename/expansion of bsnes project) -> bsnes-mercury (fork of higan) -> bsnes (the project made a return!). Toot toot!Įdit: Comments clarified that bsnes is the most up-to-date SNES core. Now I'm off to enjoy some Final Fantasy 4. The shader even says "static option for now", which is why this hellish issue cannot be fixed via the realtime shader configuration GUI, sadly. but editing the user-settings file is the only way for now. Hopefully a better fix is available in the future. The problem is entirely in the shader, which believes any high-res content is interlaced even if it is progressive. But OpenGL and Direct3D renderers failed as well. PS: I am using the Vulkan renderer, and a nVidia graphics card. Screw flickering! I am writing this guide to help others so they won't spend 3 hours trying to configure every setting of every SNES emulator and seeing that NOTHING works. Static const bool interlace_detect = false The shader now supports changing this property in-app thanks to this Reddit thread.) Edit it as follows: (Edit: Don't do this anymore.Static const bool interlace_detect = true Detect interlacing (static option only for now)? The path is your RetroArch data folder on other operating systems). Open the file C:\Users\\AppData\Roaming\RetroArch\shaders\shaders_slang\crt\shaders\crt-royale\user-settings.h (this is on Windows.So, as a last-ditch effort, I decided to attempt the "correct" solution: Turning off interlaced handling in the shader itself. Even if it did, it wouldn't work, as explained above, since the emulators that had low-res modes didn't fix the issue either. And it doesn't even have any way to turn off the hi-res mode. I am using the BSnes-Mercury Accuracy core, which as far as I know is the best emulator for SNES.
I did everything old guides said to do and it simply does not work. I tried Snes9x, Higan and BSnes, and tried other people's suggestions to "enable integer scaling, disable high-resolution SNES support, etc etc". This is terrible and unplayable.Īs far as I know, it mostly affects the SNES cores. The CRT-Royale filter uses always-active Interlace Detection, which makes it think that any high-resolution content is interlaced, and as a result it starts flickering and juddering the image since it attempts to treat the signal as alternating interlaced fields. It is a very close emulation of CRT monitors. It's widely accepted that CRT-Royale is amazingly good. They've added the ability to easily toggle deinterlacing emulation inside the shader properties in RetroArch, thanks to one of the developers seeing this Reddit thread! You no longer need to tweak the shader files yourself.
0 kommentar(er)
