Thank you for sharing your solution. The question remains why the save function from the shaders menu doesn't work for you and me, although the RGUI says that it did save the settings. If you want to dive deeper into the "failed saving config" error, please open another topic about it (for tidiness and all), start any game from that core with verbose logging via the Runcommand menu, try to (fail to) save the config, and post the contents of /dev/shm/runcommand.log in a code block in your new topic. 🙂

@TimZett said in General questions on applying shaders (video filters): The vertical shader I just took for testing purpose, because it shows something significant ;-) Currently I'm using the bilinear (blur) shader since I find the Atari games in all emulators way too blocky. I use CRT + smoother for everything. Then again, the only stuff I really play on RetroPie is SNES and PS1.

@TimZett I think @dankcushions posted a link (maybe in another topic) to the Shader docs in Retropie's documentation - https://retropie.org.uk/docs/Shaders-and-Smoothing/.

We don't offer support for 3rd party images, especially the ones loaded with ROMs. If you want support here in the forum, start with the RetroPie provided image from retropie.org.uk/download. Otherwise, contact the author of the image and ask for support.

very cool! the libretro forum's images show the difference more clearly. it would be cool to benchmark this, crt-pi, and the zfast crt shader.

@trekdrop It's not possible at the moment. The shaders are only available in RetroArch, so they're applied when a game starts.

Yes I do but nothing change

Ok, so after I wanted play some games now, I realized the bottom part of the lr-snes9x games are always black. I can't say how many rows, but maybe 10th. The other sides are all on the edge of screen and Emulation Station is shawn correct, lr-nestopia too. Is there a setting I miss? The strange thing is, in RetroArch menu the whole screen is used. The emulator makes the image of game smaller and shows a black bottom border only. EDIT: Ok so, after quick testing, it happens also in PC Engine, but not the other emulators.

Hi @sixspeeddeath Im trying the same thing on my tv. The crosstalk you are talking about is caused by the distance between eyes, you need to move the warning message so if you see it without 3d lenses it overlaps with each other. I edited the first lines of the glsl to this #define eye_sep 0.605 #define y_loc 0.32 #define ana_zoom 1.3 #define WIDTH 2.4 #define BOTH 0.52 #define HEIGHT 2.4 #define palette 1.0 #define warpX 0.00 #define warpY 0.00 and now its almost perfect on my tv anyway (and LG 3d with passive lenses). The only problem I have now its that the result image only uses 50% of the tv realstate

@dankcushions Yes I think that is what it looks like. But it's much easier to see in motion. It's not related to the resolution (I tried several).

@floxblah said in Shader and ratio configuration issues: @dankcushions said in Shader and ratio configuration issues: @floxblah don't say 'any emulator'. give me an example. give me an example game. if it's not doing 4:3 what is it doing? I use lr-fceumm emulator with duck tales (europe version). If i set 16:9 it will apply the 16:9 ratio and if i set 4:3 i have the game default ratio value (like the ratio value is unset). ok but the default ratio will be 4:3 on almost all old games. some PAL (europe) versions will have borders but that won't be solved by changing your aspect ratio - they would have had borders on 4:3 tvs also. fceumm will have options to change how it displays borders perhaps - select + X to get to the retroarch menu, then quick menu > core options. it will be the overscan options.

@tkrypton OK, I've bought a card with shader support. Grmpf... But now no errors anymore ;-)

@davej Looks like that's it! Turning threaded video on allows for both to coexist without the noticeable slowdown. Strangely enough, I have no recollection of having turned that off. Looking at that other thread you linked it would appear that "on" is the default, right? I will admit to the possibility that I may have switched it off not knowing what it was for, but I don't recall having done so. I'm also now finding that the Threaded Video reverts back to OFF after I exit out of a rom to retroarch, despite selecting to save the core override. When I check the contents of the retroarch.cfg threaded video is set to "true". Any thoughts on that? EDIT: After going into the RetroPie Setup It appears that while retroarch.cfg was set to "true", all of the problem emulators were set to "false" (which I believe overrides the retroarch.cfg). Going into them individually and changing them seems to have sorted this out. For anyone else who might be in the same situation, I found these by going to the RetroPie section in Emulation Station and hitting... RetroPie Setup > Configuration / tools > configedit >advanced configuration>Configure Libretro Options>and then choosing the emulator/retroarch.cfg and turning video_threaded from false to true. Thanks again for the help!

I came across your shader while messing around with settings last night, and I just want to say that you did a phenomenal job. This is the shader I have been looking for and didn't even realize I was looking for it. Finally I can turn off integer scaling and get rid of all that pixel wobble. I highly advise everyone to give this shader a shot. If you like that "perfect pixel" look but can't stand the artifacts that come with it, this is the shader for you.

@Darksavior It's probably due to your heatsink why mine heats up more (planning on building a custom cooper heatsink + alluminum fins). Normally my pi stays under 65 on any system, but with shaders hits in the 80's which i don't like. This shader was also just for fun and to give it some sort of dimension, not really suppose to do anything else .As for The reason why the shader was never ported as a sort of overlay is probably due to it being sort of difficult.

Turns out it still doesn't work ! :( I thought it did since I used the alternate line AFTER I changed the shader using the Retroarch GUI. Now even if I delete the new line or change it, no change to the shader :( Somehow, changing the shader through the Retroarch GUI does it, whatever is in the retroarch.cfg file. Now what I'm thinking, could it be something to do with file permissions ? That shader line, does it tell the system to change another file properties and maybe it isn't able to do it because of file permission ? I am thinking about this since I see other posts about file permission issues, requiring to do something like : Sudo chown pi:pi /opt/retropie/configs/ Could that help ??? At work right now...

@dankcushions said in Two shader directories in 4.1?: @batesman said in Two shader directories in 4.1?: @dankcushions So is it possible to be able to cycle through the shaders without setting one as a default? i think so. by default you need to hold your hotkey (select on your control pad) and press n or m on a keyboard, i believe. You got it. I had to hold select on the control pad, then press m, n to cycle. Based on the way the hotkeys were defined in the retroarch.cfg file I thought I only needed to press m or n. Thanks!

@DieKatz Awesome even I do like the DMG-01 shader lots more. Thanks for your work!