FBNEO Screen Glitches. (CLOSED)

Drdave79

Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..) Raspberry Pi 4
Power Supply used: (If using a Pi) Unsure.
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.8
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used) Original RetroPie image from website modified by myself.
USB Devices connected: 2 Sinden Lightguns and 1 keyboard/mouse combo
Controller used: Two Dragonrise joysticks and buttons
Error messages received: None
Verbose log (if relevant): see below
Guide used: (Mention if you followed a guide) None
File: (File with issue - with FULL path) /home/pi/RetroPie/roms/arcade/sf2.zip
Emulator: (Name of emulator - if applicable) lr-fbneo

Drdave79

@dankcushions I now have a runcommand.log but it's empty.

runcommand.info:

arcade
lr-fbneo
/home/pi/RetroPie/roms/arcade/sf2.zip
/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/sf2.zip"

retroarch.cfg

video_refresh_rate = "60"
video_fullscreen = "true"
video_fullscreen_x = "1280"
video_fullscreen_y = "720"

Drdave79

@dankcushions I did use pastebin.com.

barbudreadmon

@Drdave79 again, you should make sure everything is fine with your synchronization settings, maybe you need

video_vsync = "true"
vrr_runloop_enable = "true"

?

Edit: also note that i just added a core option to force 60Hz, however you should only consider this as a last resort workaround since it'll make games run faster than they should...

dankcushions

@Drdave79 said in FBNEO Screen Glitches. Need advice please.:

@dankcushions I did use pastebin.com.

in what sense? the last logs you have posted have just been pasted directly - you just did it again now!

i appreciate this hobby can get technical and isn't always intuitive, but to support people in the least amount of free time there's lots of documentation and specific instructions on how to seek support.

read this first says about logs:

Format your posts! - put small logs in code blocks - see http://commonmark.org/help/ - and put large logs on a pastebin type site like http://paste.ubuntu.com/ http://pastebin.com/ or similar.

there's 3 options there, all of which are better than just pasting logs/configs directly into the forum (although even that is better than not posting them at all..). please read carefully the read-this-first page next time you seek support, which appears to be quite frequently. there is better things we could all be doing than repeating what has been said at the top of every forum page.

dankcushions

@Drdave79 said in FBNEO Screen Glitches. Need advice please.:

@dankcushions I now have a runcommand.log but it's empty.

runcommand.info:

arcade
lr-fbneo
/home/pi/RetroPie/roms/arcade/sf2.zip
/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/sf2.zip"

retroarch.cfg

video_refresh_rate = "60"
video_fullscreen = "true"
video_fullscreen_x = "1280"
video_fullscreen_y = "720"

i can see from this that you didn't run with verbose logging via the runcommand, although it should still generate the file regardless (and you still haven't run the command like i instructed). you should also paste all relevant configs, /opt/retropie/configs/arcade/retroarch.cfg, /opt/retropie/configs/all/retroarch.cfg (note: codeblocks, pastebin, etc etc)

but yeah, what's all these video settings? they're not stock.

sleve_mcdichael

@dankcushions said in FBNEO Screen Glitches. Need advice please.:

(and you still haven't run the command like i instructed).

I think that's what they meant by:

@Drdave79 said in FBNEO Screen Glitches. Need advice please.:

When I run that command, I get mono.520

dankcushions said:

but yeah, what's all these video settings? they're not stock.

Are you referring to:

retroarch.cfg

video_refresh_rate = "60"
video_fullscreen = "true"
video_fullscreen_x = "1280"
video_fullscreen_y = "720"

...? This is their /dev/shm/retroarch.cfg, automatically generated here at runtime; mine is identical to this (I am using a 720p TV.)

...unless you mean the:

hdmi_group=1
hdmi_mode=4

...in their /boot/config.txt; those, indeed, are not stock.

Drdave79

@sleve_mcdichael Thank you Sleve for helping to clarify. I'm not trying to be difficult at all. I've always appreciate everyone's time here. But yes, I did run the command and report back as @dankcushions has requested. He must have missed my response.

@dankcushions I wasn't aware I had to run verbose logging via runcommand. But even you admit that it should still generate the file either way. I can definitely add the additional logs you requested from pastebin. I will do that shortly.

If my /boot/config.txt isn't stock, where can I obtain the correct file to avoid more problems?

Drdave79

@dankcushions I must not be using pastebin.com correctly. I paste the log into the top. I give it a name and click create new paste. Then I hit copy raw which places it in the clipboard. Then I paste it in this forum. I don't want to continue to frustrate you.

sleve_mcdichael

@Drdave79 said in FBNEO Screen Glitches. Need advice please.:

@dankcushions I must not be using pastebin.com correctly. I paste the log into the top. I give it a name and click create new paste. Then I hit copy raw which places it in the clipboard. Then I paste it in this forum.

After you click "create new paste," copy the URL from the address bar and post that here, like: https://pastebin.com/DUj6i1Gi

We can click on that and view the paste in a new window.

@Drdave79 said in FBNEO Screen Glitches. Need advice please.:

I wasn't aware I had to run verbose logging via runcommand.

Yeah you have to enable it each run, or you could enable it permanently in /opt/retropie/configs/all/retroarch.cfg with:

# Enable or disable verbosity level of frontend.
log_verbosity = true

If my /boot/config.txt isn't stock, where can I obtain the correct file to avoid more problems?

You can extract the file from the stock SD card image using 7zip on your PC.

Drdave79

@dankcushions

/opt/retropie/configs/arcade/retroarch.cfg

https://pastebin.com/X6UqByyC

/opt/retropie/configs/all/retroarch.cfg

https://pastebin.com/7J9b0fzz

I hope this works.

Drdave79

@sleve_mcdichael Thanks again Sleve!

Drdave79

@barbudreadmon Under which config file?

sleve_mcdichael

@Drdave79 said in FBNEO Screen Glitches. Need advice please.:

When I run that command, I get mono.520

I have no idea what this is; it doesn't exist on my system, and googling it only shows me ads for wigs.

(Edit: that was for mono.513; mono.520 shows ads for bikes and laser printers instead. It seems your filename is changing.)

Is it still there? If you're curious like me, you would see what kind of file it was with the file command, like:

file /dev/shm/mono.520

...and if it said something like "ASCII text," you might even inspect it with nano or less to see what its content was.

If it's not there, or you're not curious, just do a reboot, and then try again to generate the verbose log.

@Drdave79 said in FBNEO Screen Glitches. Need advice please.:

/opt/retropie/configs/arcade/retroarch.cfg

https://pastebin.com/X6UqByyC

Does it improve any if you disable the overlay? They don't eat up too many resources*, but sometimes every cycle counts.

*(if you use shaders and overlays at the same time, it gets pretty heavy.)

Drdave79

@sleve_mcdichael Never really had an issue before with shaders and/or overlays. Tried removing the overlay and still saw the glitch a few times.

I did update to the latest lr-fbneo binary.

When comparing the standard config.txt and mine, I only noticed two differences. hdmi_mode=4 under one section. And an extra gpu_mem=256 under the [all] section. I've removed the last one and tried it again. Only saw one blurr in the 5 minutes of playing SF.

I'm not going to waste anymore of anyone's time on this. I'm just going to accept the random screen glitching. It's not horrible, just noticeable. I really appreciate everyone's help.

sleve_mcdichael

@Drdave79 said in FBNEO Screen Glitches. (CLOSED):

When comparing the standard config.txt and mine, I only noticed two differences. hdmi_mode=4 under one section. And an extra gpu_mem=256 under the [all] section.

You also had a few lines un-commented that are commented out in the default:

disable_overscan
hdmi_force_hotplug
hdmi_group
hdmi_mode

I've removed the last one and tried it again. Only saw one blurr in the 5 minutes of playing SF. (...) I'm just going to accept the random screen glitching. It's not horrible, just noticeable.

...but yeah, the one that really stood out is gpu_mem; I know that on the RPi4 it is generally not recommended to increase this beyond the default. I imagine this is going to be your best solution, going forward. Cheers!

Drdave79

@sleve_mcdichael Thanks again @sleve_mcdichael. You're a good guy :)

dankcushions

@Drdave79 said in FBNEO Screen Glitches. (CLOSED):

I wasn't aware I had to run verbose logging via runcommand.

you're never going to guess where this is clearly written... https://retropie.org.uk/forum/topic/3/read-this-first :P

But yes, I did run the command and report back as @dankcushions has requested. He must have missed my response.

you didn't give me the output. ls -l /dev/shm won't just output a filename, it will output the entire contents of the directory, permissions, etc. that's what i wanted.

@dankcushions

/opt/retropie/configs/arcade/retroarch.cfg

https://pastebin.com/X6UqByyC

finally this is how you use pastebin. thank you :)

/opt/retropie/configs/all/retroarch.cfg

https://pastebin.com/7J9b0fzz

# Menu driver to use. ("rgui", "xmb", "glui")
menu_driver = "xmb"

the default in retropie is rgui, which consumes the lowest resources. i'm not aware of others causing issues, but bear in mind.

shaders aren't neccesarily a problem, depending on which one you use, but coupled with overlays they are known to cause performance issues.

without a verbose log it's a lot of guesswork, though.