Over- and underscan (Quake 1/3 screen too big)

backstander

The only problem is the Ports (i tested with Q and Q3)

I'd still recommend experimenting with changing resolutions for Q and Q3 from their respective settings menu.

Also the the reason I suggested the additional settings for the TV was in hopes that you wouldn't need to use any overscan settings in config.txt ;-)

backstander

@Xyb0t
Here's the short documentation about TVs to "prevent any overhead due to upscaling":
https://github.com/retropie/retropie-setup/wiki/Speed-Issues#tv

Xyb0t

Game mode seems to deal with smoothing and can create lag. Luckily i have no issues with that.

As i stated in my initial post, changing the resolution in Q and Q3 doesn't do much, since the screen is scaled to 1080p afterwards anyways. The picture stays the same size (which is perfect size when i turn on overscan compensation, but turning it off gives me black bars).

The non-technical description of my experience would be something like this: It's like the Quakes are perfect for my TV, but all the rest of the Pi gives me black bars... If i turn off the black bars, the screen 'grows', also the Quakes, but then they're too big despite the rest of the Pi fitting perfectly.

Anyways, thanks for your input. I'll experiment some more this afternoon.

Xyb0t

I've been investigating some more, and i am fairly sure that i'm correct in stating that Quake and Quake3 dos not have scaling settings in the runmenu.

So, everything on the Pi runs beautifully fullscreen BUT Quake and Quake3 screen is bigger than the rest of the stuff, which makes it go beyond the edges of my TV.

In Quake3 it's not really obvious besides the screen after the level is finished. But in Quake, the lower half of the statusbar is beyond the screen.

Setting various screen resolutions does not affect the issue
Settings on the TV does not affect the issue
I can have perfect Q/Q3 screens if i turn off oversca_scaling and overscan compensation in the config-file for RetroPie, but then EVERYTHING else will have black bars.

So, is there any way that i can turn on compensation as per emulator? That way i can disable it globally (having nice Q/Q3), and then just compensate for everything else manually?

Xyb0t

I should add that for Quake, i use Darkplaces. For Quake3 i think there is only 1 program. At least, i use the deafult one :)

Xyb0t

Seriously? No replies at all??

Is this because i amway off? Or is it that no one confirmed the same effect? Or maybe i am just the only one to discover this? :)

It really is a pita for me, since i love fullscreen, and i love both retro emus and ports :S

backstander

@Xyb0t

So, is there any way that i can turn on compensation as per emulator? That way i can disable it globally (having nice Q/Q3), and then just compensate for everything else manually?

The only thing I can think of is to use the runcommand-onstart.sh and runcommand-onend.sh scripts:
https://github.com/retropie/retropie-setup/wiki/runcommand#runcommand-onstart-and-runcommand-onend-scripts

I'm not advanced enough in script programming to tell you want to actually put in those files :(

In /opt/retropie/configs/all/runcommand-onstart.sh you might put something like:

# if you're launching quake then change the overscan settings
if [ "$1" = "quake" ]
    ??? some code here to change the overscan ???
fi

And in /opt/retropie/configs/all/runcommand-onend.sh:

# if you're exiting quake then change the overscan settings back
if [ "$1" = "quake" ]
    ??? some more code to change the overscan back ???
fi

Xyb0t

@backstander
This sounds VERY promising :) I was not aware that these scripts existed (i'm still fairly new to RetroPie).

So, Would anyone know if i can stuff these scripts with the ordinary parameters also found in the config.txt file and such?

edmaul69

@Xyb0t if you want it to work fine on everything without special code, in the config.txt leave it to the setting where you have the bars. Now at the top you see the up down left and right overscan settings. Remove the hashtags (#) and play with the numbers until you get it full screen. Then everything will work correctly.

Xyb0t

@edmaul69
Holy moly.. this actually did the trick!!!! Thanks so much for helping me out, man!

edmaul69

@Xyb0t glad you got it working good now.