Pi 4 display issue with lr-genesis-plus-gx

sad_muso

Has anyone else seen this issue? Ri 4 running latest 4.6 build on 4K TV forced to 1080p in config. Only seems to happen when using shader (only tested with zfast crt standard), and even then it's intermittent on booting a ROM; maybe 5/10 times.

video

Ecks

Maybe try out another core and see if the same thing happens again?

quicksilver

This seems to be a reoccurring issue. Ive seen this reported a few times now in the last few weeks. From what I heard it is a retroarch issue (not specific to one core). Hopefully it gets fixed soon.

Ecks

Just saying but i tried out that Pico version (i think that is what it is called) and tested out all my Genesis games and didn't come across any of the issues he was getting so it could be a core thing on the Pi 4 just saying.

sad_muso

@Ecks Yeah, maybe I should switch over to Pico. I tend to always use the default cores as I assume they are the 'best'

dankcushions

hmm, this seems like the same/similar issue as spotted by @GreenHawk84 in this thread: https://retropie.org.uk/forum/topic/25665/odd-megadrive-genesis-video

do you also overlays, @sad_muso ? i'm curious if it's only affecting the lr-genesis-plus-gx core, as that's a common thread in both of these occurances.

quicksilver

@dankcushions https://retropie.org.uk/forum/topic/26177/black-overlay-when-launching-snes-emulator

lr-snes9x2010 and possibly Mame too

dankcushions

@quicksilver oh, well great that it's been logged: see https://github.com/libretro/RetroArch/issues/10541 - any fixes/updates will be posted here.

GreenHawk84

This is awesome news, I was losing hope. I felt like I broke something when I am certain I have not messed with any settings.

GreenHawk84

I tried to go into Retroarch and save Core Overrides with Settings>On Screen Display>On-Screen Notifications>Off, but they still load. I am not sure if this method of removing notifications to prevent the bug works.

Is anyone able to set notifications off and save it?

GreenHawk84

I am still unable to disable on-screen notifications upon game startup. Anyone having issues?

Clyde

@GreenHawk84

@mitu said in Anyway to turn off the footer when you start a game?:

You need to disable also the Graphics Widgets option, which is right below the Onscreen Notifications option.

mitu

@Clyde Actually, that might not work. I re-tested this briefly and it doesn't seem to disable all the new-style notifications - I think that's what @GreenHawk84 is reporting.

It could be there's more than 1 configuration option that would need to be toggled - but from a cursory inspection of the code it might not be possible without disabling the new notification style entirely at build time.

Clyde

@mitu At least it worked for me. When I disable Onscreen Notifications and Graphics Widgets, I get no messages in the games at all. I could check this more thoroughly for other options possibly involved when I get home.

mitu

Ok, I re-tested it and @Clyde is right, it should work - it's possible to fallback to the previous notifications' style without disabling the notifications, though I couldn't make it work via the RGUI on the first try

@GreenHawk84 Try adding this to your /opt/retropie/configs/all/retroarch.cfg:

menu_enable_widgets = "false"

Clyde

Maybe I should've mentioned that I'm using the XMB menu, although that shouldn't change the options rather than arrange them differently, if I'm not mistaken.

GreenHawk84

Confirming setting Widgets to OFF and saving Core Options does not disable them:

Clyde

As far as I understand it, you have to disable both to get no notifications. Disabling the widgets alone will only reset their style to the more simple one of previous RetroArch versions.

GreenHawk84

@Clyde these options do nothing for me. I get widgets either way and exposure to the pillar boxing bug. I am not sure why mine would be different than anyone else, I do not mess with settings in general, it's all defaulted.

I will have to try Mitu's suggested modification of the Retroarch.cfg.

Clyde

@GreenHawk84 Maybe you have a saved core configuration or override in place that negates the options which (you think) you are saving? See Config Hierarchy for the places to look for additional config files.