withgallantry / OneForAll

One For All gaming overlay software
Other
12 stars 9 forks source link

On Screen Display Scaling? #7

Open Unboundclassic opened 4 years ago

Unboundclassic commented 4 years ago

On the old and new versions of OneForAll the OSD size has been an issue with those of us with low resolution/composite screens.

For example here's my composite screen on my handheld build. The battery is just barely large enough to be usable. Would be better larger. All the other icons are unusably small. Even the heads up display hot key menu subtitles are tough to read. IMG_3003

I've tried troubleshooting with Helder and he believes the the .config information should affect the size of the OSD. We tried a bunch of settings though in the .config file and nothing seemed to affect it. Various framebuffer resolutions and such. Any ideas? Or is this just not doable right now?

Here's my config.txt configuration:

For more options and information see

http://rpf.io/configtxt

Some settings may impact device functionality. See link above for details

uncomment if you get no picture on HDMI for a default "safe" mode

hdmi_safe=1

uncomment this if your display has a black border of unused pixels visible

and your display can output without overscan

disable_overscan=1

uncomment the following to adjust overscan. Use positive numbers if console

goes off screen, and negative if there is too much border

overscan_left=21 overscan_right=25 overscan_top=24 overscan_bottom=18

uncomment to force a console size. By default it will be display's size minus

overscan.

framebuffer_width=320 framebuffer_height=240

uncomment if hdmi display is not detected and composite is being output

hdmi_force_hotplug=1

uncomment to force a specific HDMI mode (this will force VGA)

hdmi_cvt=320 240 60 1 hdmi_group=2 hdmi_mode=87

uncomment to force a HDMI mode rather than DVI. This can make audio work in

DMT (computer monitor) modes

hdmi_drive=2

uncomment to increase signal to HDMI, if you have interference, blanking, or

no display

config_hdmi_boost=4

uncomment for composite PAL

sdtv_mode=16 sdtv_progressive_scan=1

uncomment to overclock the arm. 700 MHz is the default.

arm_freq=800

Uncomment some or all of these to enable the optional hardware interfaces

dtparam=i2c_arm=on

dtparam=i2s=on

dtparam=spi=on

Uncomment this to enable infrared communication.

dtoverlay=gpio-ir,gpio_pin=17

dtoverlay=gpio-ir-tx,gpio_pin=18

Additional overlays and parameters are documented /boot/overlays/README

Enable audio (loads snd_bcm2835)

dtparam=audio=on

[pi4]

Enable DRM VC4 V3D driver on top of the dispmanx display stack

dtoverlay=vc4-fkms-v3d max_framebuffers=2

[all]

dtoverlay=vc4-fkms-v3d

gpu_mem_256=128 gpu_mem_512=256 gpu_mem_1024=256 overscan_scale=1 dtoverlay=hifiberry-dac dtoverlay=i2s-mmap

Unboundclassic commented 4 years ago

Perhaps if I simply change the size of the source graphics? Or are those scaled and locked by the code?

Unboundclassic commented 4 years ago

Important info may be that composite screens actually ignore the "framebuffer" resolution as it's an analogue signal.

The only affect framebuffer has on it is that the back end scripts like RetroPie Setup scale based on that configuration. Would be great if the OneForAll OSD dd the same thing.

Though optimally it would just be a setting the the general configurations file that you could just dial in with a 1-10 numeral or something like that.

Unboundclassic commented 4 years ago

So for the record scaling the graphics does have an affect. Though not perfect. The battery scaled really nicely. As I suspected though, the rest of the items were not positioned correctly once they were scaled and a couple of them didn't seem to respond to being scaled or wouldn't show up in the system once booted. Since the other items weren't showing up correctly I just removed them for now and just have the larger battery icon. Either a way a step up. I kept a backup of of all the original icons though. unnamed