Page 1 of 1

VSCALE_BORDER not taken into consideration ?

Posted: Thu Jul 23, 2020 9:00 am
by mahen
Hi !

I'm using this aforementioned setting to reduce the picture size (along with integer scales) in some cores, depending on how "fine" (less blocky) I want the picture to be.

It seems the setting is not applied in the GBA core. I tried several values, I tried to set it as global, or just for the core (after [GBA]), to no avail.
The setting is applied properly in the GAMEBOY core for instance.

Any idea ?
Cheers !

EDIT : it seems the value is not applied anywhere anymore actually. Gonna check what is wrong.

Re: VSCALE_BORDER not taken into consideration ?

Posted: Thu Jul 23, 2020 4:28 pm
by JBeau
Hey! I tried this too the other day. Didn’t work for me either. If you’ve found a solution I’m all ears :)

Re: VSCALE_BORDER not taken into consideration ?

Posted: Thu Jul 23, 2020 4:53 pm
by mahen
It used to work actually !

Re: VSCALE_BORDER not taken into consideration ?

Posted: Fri Jul 24, 2020 9:29 am
by 12characters
I noticed some months ago that vscale_mode and vscale_border no longer work together. Only by setting vscale_mode=0 would the latter setting work. I chose to sacrifice this in order to keep the integer scaling.

And yes, it is not core specific.

Re: VSCALE_BORDER not taken into consideration ?

Posted: Mon Feb 08, 2021 2:09 pm
by Sorgelig
border is not applied to framebuffer mode. If you use GBA with 2x resolution, then it uses framebuffer.

Re: VSCALE_BORDER not taken into consideration ?

Posted: Sun May 30, 2021 8:46 pm
by mahen
Hi Sorge ! Actually, unless I'm mistaken, it's not applied in any core ATM ?

I'm trying to make the DOS (or SNES, Neo Geo, Genesis) core use a smaller form factor -- 5x is too much for me, I want to stick to 4x as the Amiga core, easier on my eyes, less blocky... The picture is closer to what I used to have on my small TV back in my childhood when this scaling factor is applied :)

I'm pretty sure it used to work. I used to apply it on the SNES & Neo Geo cores for instance. 1 year back or so ?

Cheers :)

Re: VSCALE_BORDER not taken into consideration ?

Posted: Mon May 31, 2021 3:54 am
by FoxbatStargazer
It seems like vscale_border needs integer scaling disabled (vscale_mode=0). So you pick one or the other. (Not sure how it interacts with some of the newer HUD integer scale options.)

However I'm not sure you need vscale_border to do what you want? vscale_mode=1 is going to yield 4x vertical integer scale for most cores at 1080p (maybe you are using 1200p?)

DOS is a bit tricky because the low res VGA is only 200p... so yeah that is a 5x scale. DOS text however is 400p. In the core video options there's something "low res = native" I think if you flip it to 4x, it will render 640x400 before upscaling, meaning it should end up 1280x800 AKA effectively 4x scale at 1080p.

Re: VSCALE_BORDER not taken into consideration ?

Posted: Mon May 31, 2021 5:13 am
by mahen
Hi ! Thanks for the reply ! Hmm, the behaviour must have changed then, because it used to work along with integer scaling.

Thanks for the suggestion but if I use lowres = 4x I cannot apply the scanlines properly to the base picture but only to the upscaled one !

Tricky one Indeed ! :) Would be awesome if there was some "max scaling Factory option" :) cheers !

Re: VSCALE_BORDER not taken into consideration ?

Posted: Mon May 31, 2021 5:57 am
by mahen
Just to be more accurate : in the past, when enabling both vscale_border and integer scaling, what would happen was :

- for instance, if you used a 1080p mode with a border of 50 and a 240p core
- it would find the biggest possible multiply of 240 in (1080 minus 50)
- in this case : it would make no difference as it would still be a factor of 4. But with other resolutions it would. For instance, compare Amiga NTSC vs Amiga PAL resolution.

- in modes with 200 lines, it would enable to reduce the factor from 5 to 4

I actually think this option made sense if you wanted to prevent overly big pixels ? Also it could be specified on a per core basis.

Re: VSCALE_BORDER not taken into consideration ?

Posted: Tue Jun 01, 2021 5:39 am
by FoxbatStargazer
mahen wrote: Mon May 31, 2021 5:13 am Hi ! Thanks for the reply ! Hmm, the behaviour must have changed then, because it used to work along with integer scaling.

Thanks for the suggestion but if I use lowres = 4x I cannot apply the scanlines properly to the base picture but only to the upscaled one !

Tricky one Indeed ! :) Would be awesome if there was some "max scaling Factory option" :) cheers !
15khz scanlines on DOS games is some real blasphemy :x (I say as I am enjoying consoles at 480p on VGA... :P )

Re: VSCALE_BORDER not taken into consideration ?

Posted: Tue Jun 01, 2021 7:04 am
by mahen
Hehe, yeah, I'm an ST/Amiga guy and was shocked back then when seeing the same games on my friends' PCs. They looked way blockier ;)

Re: VSCALE_BORDER not taken into consideration ?

Posted: Tue Jun 01, 2021 8:52 am
by mahen
I temporarily worked around this by specifying a vscale_border of 140 to get a 4x scaling with perfect scanlines on the DOS core. Obviously, it only works if games use a 320x200 resolution. Of the game is in 320x240 (ex. Blackthorne) scanlines look bad :)