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!

@momaw27 i know this is quite old, but I decided to make a Gameboy color border of my own, because the green one is too small, credit goes to @DieKatz for the Gameboy Pocket border, along with @momaw27 for the Gameboy Color Logo. gbc-gcase-grid-resized.png

I have had to add the line video_shader_enable = "true" to the emulators I want the shader to work in as well. I may not be doing it right, but I don't use shaders on all emulators, so I just use the line in the individual configs to enable it. I did find out the other day that I need to configure the settings within the in-game retro arch config for scaling and nearest vs linear too or else the default to "don't care" and don't look the way I want them to.

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