I reverted to an older fw. All is good. Protip, never buy vizio. They remove features. They removed chroma 4:4:4 in later fw updates and it screwed everything up.

@Dezmancer you are correct in that component is superior to s-video, my bad, I read component as composite.
but in old consoles s-video can be enough to look very crisp unless you are using a state of the art tv.

edit: also I have a retroduo too and the output is very crisp and clean in comparison to a regular snes.

Leave SHADERs and use OVERLAYs which simulates scanlines.

1 - install overlays from the retropie menu
2 - go to the folder:
/opt/retropie/emulators/retroarch/overlays/effects/scanlines/
take an overlay file and copy it to your computer, as well as your configuration file
3 - The overlay file is a png that can be cut into photoshop or other simpler programs. cut to fill exactly 640x480 in length.
4 - so remember in the configuration file and png file names etc where you have some resolution (example 1280x1024) you replace with 640x480

note that you are creating your 640x480 overlay from scratch

5 - enable overlays and select the one you created that has 640x480.

this is the method i found to make scanlines correctly match the pixels displayed on the screen

OBS: My english is bad, i am using google translator, i hope nothing written has got double meaning here too. Because in my post about EMULATIONSTATION LOCATION one person even complained.

@megaJekan as said in your other thread, 480p is unnecessary for a pi3b+ and pcsx. psx emulation has been running full speed on pis since the pi2. if you're getting slowdown at 1080p and NO shaders, you have a system issue.

as for curvature shaders - zfast should be full speed at 1080p on most games and is the fastest one available. they won't look at 480p as it's just not enough resolution for that effect to look good. it's not enough resolution for a non-curved scanline shader...

@skykid said in Shaders not displaying properly, weird issue / CRT-PI etc.:

I have the backup of the retroarch.cfg I had before I replaced it with the dist version. To restore the console retroarch.cfg’s I should be able to pull them from a previous backup - but do I need to replace all the console files?

You can easily compare the versions you have on your backup with what you currently have installed.

The switching of the resolution between frontend and rom sounds like it was set prior in the runcommand, but I assure you it wasn’t! When I went in there today it was all totally vanilla. I never messed with anything in there before.

'in there' where ? How do you check it ? The video modes switch should be saved in the /etc/retropie/configs/all/videomodes.cfg file, you can also check there.

I did give a try a few minutes ago. If I sit far away from my TV the shader looks okay but if I'm up close I can tell a difference. I don't know enough about the inner workings of shaders to say exactly why it looks worse up close, but it does. Hmmm.. I guess it's back to 1080p then as a nice shader is more important to me than marginally smoother menus.

Actually, thinking about this further, it might really be best to move the scanLineWeight * BLOOM_FACTOR out of the pow call. All this does is apply a nonlinear filter to the scanlines (why?), which should increase aliasing artifacts.

Another thought I had considered was using a quadratic Taylor series approximation to the gamma filter given by x^a ~= x*(1+(a-1)(x-1)), which works pretty well as in this quadratic approximation. A cubic approximation is even closer (but may not be necessary), as shown. But I note that someone seems to have had a similar idea here with these new "zfast" shaders, so perhaps those are already doing this sort of thing...

@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).

Sorry to reply to such and old thread, but did you get it working? Trying to use crt-pi to and crt-pi vertical but it doesnt work. I have seperate config files for every arcade game, that change screen size and if its vertical or not. I copied from my retropie on raspberry pi, but crt-pi will not work. Load presents in retroarch menu doesnt work either.

@Pietze I'm not able to see the game art on the game lists (I've downloaded the NES pack and placed it on ~/.emulationstation/downloaded_images/nes/, is that enough?)

@buzz said in CRT-Pi Shader differs on Pi Zero vs. Pi 3?:

@riverstorm I set render resolution to default (video res) and video res to 720p. So they are both 720p. Looks good to me on my screen.

Thanks Buzz this worked perfect and runs the older games listed above just fine. In either 720 or 1080 with both Udb's overlays on and crt-pi shader enabled. Stock is a bit--bit sluggish at 1080 but is completely playable. Overclocked is no problem. I did not have FPS up but just more going off feel.

I also tried Udb's overlays. The 1080 overlay worked in both 720 and 1080 and fit perfect. I am guessing it's just downscaled in 720. You need to set both the group and mode to get the output set to 720. Just the mode doesn't work.

I also did not know the difference between video and output settings in the quick config as they seem like they should be the same logically thinking but video is the one to choose.

One thing that was off and didn't work correctly was Dank's custom shader configs. I used a stock 4.3 image and updated the script, retroarch core and lr-mame2003. When I ran a game it would just show me the top left corner of the game like it was really zoomed in. I am not sure if it was something as simple as a setting to get them working again.

I did get a modest overclock on the arm but decent on the gpu & sdram. The arm_freq up to 1075 (7% increase), gpu_freq (which includes the core_freq & v3d_freq) up to 525 (24% increase) and the sdram_freq up to 525 (24% increase) also.

The arm_freq is a bit modest. It is the same SoC as the Pi 1 but the manufacturing technique improved in the 4 years between releases and they were able to release it as 1,000 MHz stable whereas the Pi 1 was released as 700 MHz stable at the time. I would guess it's really pushed to it's limits already at 1000 but I see some that are getting good silicone at the top of the bell curve of variance are getting 1.2 GHz.

It's already overvolted to 6 but a simple small heatsink barely protruding through an acrylic case kept mine more than cool enough with nothing special.

A good base starting point is 1000 for arm and 500 for gpu & sdram and I worked up from there.

I did get some annoying static-ish feedback noise in Elevator Action but games like Rastan, old classics, etc. worked great.

For shaders 480 looks muddy (I prefer the solid jaggy graphics over this), 720 is acceptable but at 1080 you can clearly see a difference on a 4k TV and looks great. It might come down to performance when choosing which resolution and if using overlays and shaders.

I do like the zero but it seems like a niche market for handhelds or some special project. It's sluggish in everything from bootup, loading games, etc. compared to the 3. I think if you have room the 3 is the way to go but the zero is nice and incredibly small. Easy to velcro to the back of the TV or something. Using thin HDMI and power cables would make it easy to hide as it's quite a bit smaller then the 3 with a case.

@davej Sorry, I've not edited these type of files myself and just assumed like other config files that a # meant to ignore the entry. Learnt something there.

Yes @shazza6887, this is the way, but you do not need to use VGA to Rsinc adapter, you can use a vga 2 rgb cable (like this https://www.amazon.com/VGA-RGB-Cable-Male-1-8m/dp/B0096TTOHG) or and VGA to Scart (in this web explain how to make the cable http://www.idiots.org.uk/vga_rgb_scart/)
And force the pi to output at 15khz (https://github.com/raspberrypi/firmware/issues/637 this way have some problems only if you want to use multiple resolutions).

I dont have a solution, sorry, for me its been the same since june.