Jump to content
LaunchBox Community Forums

Best overall Shader for CRT effect


johnnyskullhead

Recommended Posts

You can also create per-core and per-game overrides for things including, but not limited to, shaders. Some shaders look good in some scenarios but bad in others depending on the type of content. If you decide you want all PSX games to use X shader, go into the Quick Menu and tell it to save the core override. If you decide that you want a specific PSX game to use a different shader from the rest of them, go into the quick menu and save the game override. It'll prioritize using them as Game Override > Core Override > Base.

Link to comment
Share on other sites

As far as "which one is best" it's a matter of personal preference. CRT-Hyllian Multipass is the one I use for pretty much everything. Other noteable ones are CRT-Hyllian Glow, CRT-Easymode Halation, CRT-Royale, and CRT-Royale Kurozumi (this one is in the "cgp" shader folder, not "crt"). Hyllian Multipass and Easymode Halation look good even without integer scaling, the others not as much.

I've got some examples of quite a few of them in the thread below. I recommend downloading the zip I attached in that post and looking at them that way. Some of the image previews don't work right in the post and they have to be viewed full screen anyway otherwise they look weird.

 

Link to comment
Share on other sites

I use a slightly different approach with Retroarch shaders:

I setup a main shader per core, then i create small XXX_shader.cfg files containing this line:

video_shader = ":\shaders\<name of shader>.glslp"

Each file has a different shader and if i want to bypass the main shader for specific games i add in the Custom Command Line parameters:

--appendconfig "config\XXX_shader.cfg"

 

Link to comment
Share on other sites

5 minutes ago, Crush said:

I setup a main shader per core, then i create small XXX_shader.cfg files containing this line:

video_shader = ":\shaders\<name of shader>.glslp"

Each file has a different shader and if i want to bypass the main shader for specific games i add in the Custom Command Line parameters:

--appendconfig "config\XXX_shader.cfg"

That's exactly how overrides work though. It just creates a file for the changes that you make (which could be a shader change or anything else). If you open one up it'll only have "video_shader = [whatever]" and or anything else you change. Just takes a second to save and they're loaded automatically.

Link to comment
Share on other sites

23 minutes ago, Crush said:

No, i just moved to 1.4.1 but i already have the .cfg files ready from 1.3.6

 

Again, there will be instances where they're not going to work anymore. "Per-core configs" doesn't even exist in the UI anymore. It was deprecated in nightlies a while before even 1.4.0.

https://www.libretro.com/index.php/retroarch-1-4-1-major-changes-detailed/

Quote

 

Configurations

Radius greatly improved and expanded the config override functionality, adding the ability to save overrides directly from the RetroArch menu, rather than having to create them manually with a text editor. He also added the ability to save per-core and per-game shader presets, which is the main thing users wanted to change from core to core (along with retropad mapping, which is already handled via the per-core/per-game remapping function). With all of this added functionality, we decided to completely remove the conflicting and often broken and unpredictable “per-core configs” option, which had already been deprecated but kept around for legacy/transition support.

 


Control remapping is split out as well into core and game remaps. They work much the same way as overrides (change your controls and save a core remap or game remap) but are independent and can be used in conjunction with overrides.

Link to comment
Share on other sites

I rarely use Retroarch to change settings. I usually have a few generic configurations already setup, then i change a few settings in a text editor (shader, overlay, save path), i save the config with a new name and i have a new config for a new core.

Specific core settings are saved in a separate file anyway - retroarch-core-options.cfg, so you can use generic configs for everything else without breaking anything.

 

Edited by Crush
Link to comment
Share on other sites

Yes, if you are using the DX11 plugin select DX10+ when installing ReShade in the Demul directory. The installation is simple: you install ReShade in the emu folder and enable it with Shift+F2. Choose shader, change parameters and you are done. If you want to remove ReShade you simply delete the files it copies in the Demul dir.

 

Edited by Crush
  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...