Low framerate on main EmulationStation menu - Pi 4
-
@roslof It doesn't appear so, I launched a game with verbose logging enabled and /dev/shm/runcommand reports a resolution of 1920x1080.
-
@rilight runcommand.log refers to what you launched. Not ES itself.
-
Hmm, I see... I'll try the option and see if it does anything.
-
@roslof I just added the hdmi_max_pixel_freq options to my /boot/config.txt and rebooted, still no luck.
-
I'm definitely getting more stuttering/tearing in Gambette at the moment than I would expect from the 4. I checked my temps, and I'm sitting at around 59°, so I think it should be working fine.
-
Can you turn on the FPS counter and see what's the current FPS in-game ?
To check your current resolution, you can runtvservice -s
from a terminal. -
@mitu
tvservice -s
reports 1920x1080 @ 60Hz, and the framerate counter in-game shows about 57-60 fps. So maybe the problem isn't the framerate itself, but something else... -
(Also, again, I'm definitely new to this so please correct me if I have any misconceptions or if you need more information!)
-
Is your TV set to 'Game Mode' ?
-
I'm not sure - this is actually a monitor, not a TV. I can try to enable those settings, but what confuses me is that using this monitor worked fine before on the 3B+. Come to think of it, could it maybe be something to do with my micro-HDMI to HDMI adapter?
-
I just tested changing my /boot/config.txt back to how it was on my 3B+ (not disabling overscan, not changing any HDMI settings, etc) and the problem is still there. I can include a copy of the config if that would help?
-
@rilight Sure, why not. Use code tags (
```
) to surround theconfig.txt
contents. -
The version I've been using up until this point (by which I mean, without the changes to make it more like the 3B+ config):
[pi4] max_framebuffers=2 ## Overclock settings # Uncomment to overclock the arm. 700 MHz is the default. #arm_freq=2147 #arm_freq=2000 #arm_freq_min=500 #v3d_freq=750 #over_voltage=6 # Enable turbo temporarily at boot to speed up times #initial_turbo=60 # Increase the SD reader clock speed (default 50) dtparam=sd_overclock=100 [all] # Enable DRM VC4 V3D driver on top of the dispmanx display stack dtoverlay=vc4-fkms-v3d ## Base settings disable_splash=1 boot_delay=0 gpu_mem=256 ## Audio settings # Enable audio (loads snd_bcm2835) dtparam=audio=on ## HDMI Settings # Remove black borders on display when scaling disable_overscan=1 # Request "Game Mode" edid_content_type=4 ## Disable the optional hardware interfaces dtparam=i2c_arm=off dtparam=i2s=off dtparam=spi=off ## Disable 4K? [hdmi:0] hdmi_max_pixel_freq=200000000 [hdmi:1] hdmi_max_pixel_freq=200000000
-
Configuration seems fine. Do you have WiFi enabled ?
-
@mitu I have wpa_supplicant enabled, yes. Does that cause performance issues? To be clear, this isn't a problem with laggy inputs. It's what's being displayed on the screen that's the problem.
-
I have wpa_supplicant enabled, yes. Does that cause performance issues?
No, just checking what might cause any interference with the HDMI signal. At this point I'd probably try another mini-HDMI to HDMI cable or switching to a lower resolution (720p ?) and see if the problem still occurs.
-
Unfortunately I don't have another mini-HDMI adapter... I haven't seen anything from other users of the adapter indicating it could be causing problems like this (the part number for reference is B07K21HSQX). I'll try changing the resolution.
-
@mitu I changed the resolution to 720p with
hdmi_mode=85
andhdmi_group=2
, and performance in the main menu of ES is all but normal again. Gambette is no longer showing the same kind of tearing issues, though the framerate does occasionally dip just below 60fps (EDIT: I checked the game I'm running in a benchmarking spreadsheet and I believe this is normal). Why would this be happening? I thought the Pi 4 had more than powerful enough of a graphical processor to drive 1080p. -
@rilight said in Low framerate on main EmulationStation menu - Pi 4:
I thought the Pi 4 had more than powerful enough of a graphical processor to drive 1080p.
The 4B can handle it. We haven't figured out your issue quite yet.
If it helps, here are some of my config.txt settings:
hdmi_group=1 hdmi_mode=16 hdmi_max_pixel_freq:0=200000000 hdmi_max_pixel_freq:1=200000000 dtparam=i2c_arm=on dtoverlay=vc4-fkms-v3d max_framebuffers=2 dtoverlay=vc4-fkms-v3d enable_uart=1
-
The 4B can handle it. We haven't figured out your issue quite yet.
That's reassuring at least 😄
It looks like the only difference in config you have listed there related to video is the
hdmi_group
andhdmi_mode
settings, I can try that out.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.