deaftolightParticipant11/10/2014 at 23:26Post count: 42
For some reason, with moderate overclock settings, NES and SNES games are now running around 50 fps with choppy audio. I don’t know why… they always used to work fine with moderate overclock settings… Now I have to overclock to high or turbo to get them to work.
The Guardian Legend and Mega Man II were my test roms. Anybody experiencing this?
Model B+ Pi 512MBAnonymousInactive11/12/2014 at 21:16Post count: 17
I would suggest to try a few things in your retroarch config, with or without overclocking>
# Video vsync. video_vsync = true # Forces cropping of overscanned frames. # Exact behavior of this option is implementation specific. video_crop_overscan = true # Video refresh rate of your monitor. # Used to calculate a suitable audio input rate. video_refresh_rate = 60.00
Make sure you aren’t using a fancy shader, and make sure you don’t have smooth video enabled with the shaders.
Hope that helps.deaftolightParticipant11/13/2014 at 08:09Post count: 42
Thanks, but unfortunately it didn’t work.
The only way I can get games to run at full speed (60 fps) now is to set the overclock to the highest setting, turbo, at 1000 mhz. It’s odd, because I don’t remember having to do that before. Having the overclock set on medium before seemed to run everything fine. I checked top, and retroarch is the only thing running… using 90% CPU and 5% MEMdeaftolightParticipant11/14/2014 at 00:23Post count: 42
This is really throwing me off. I don’t know why all of the sudden the Pi can’t handle this. I can’t think of anything that would have caused it. I hadn’t used it for about a month, and then I installed XBMC standalone alongside… but that wouldn’t cause a slowdown. It’s not like XBMC is running while the Pi is playing ROMs. And the SD card has tons of space still.AnonymousInactive11/15/2014 at 03:50Post count: 17
When was the last time you ran
It may or may not help….I’m having an issue with one particular game doing that to me, and the sound gets all crunchy like it can’t handle it and fps drop like crazy.
I’m playing with my overclock settings as well and what I mentioned above seemed to help me. If I find out more I will post back.deaftolightParticipant11/16/2014 at 00:23Post count: 42
I ran one two weeks ago. now that I think about it, this may have started happening after the update.AnonymousInactive11/16/2014 at 01:41Post count: 17
I know it sounds funny but try pulling your Sd card out (With the pi off :)) and connect it to a windows pc and run a checkdisk on it, including the sector check. I know it won’t “find” anything but give it a go anyway and see if your problem persists.
I fixed my low FPS problem with swapping out a couple bad roms on snes, I also updated my sound settings in my config file if you want to try it out>
#### Audio # Enable audio. # audio_enable = true # Audio output samplerate. audio_out_rate = 44100 # Audio resampler backend. Which audio resampler to use. # Default will use "sinc". # audio_resampler = # Audio driver backend. Depending on configuration possible candidates are: alsa, pulse, oss, jack, rsound, roar, openal, sdl, xaudio. audio_driver = alsathread # Override the default audio device the audio_driver uses. This is driver dependant. E.g. ALSA wants a PCM device, OSS wants a path (e.g. /dev/dsp), Jack wants portnames (e.g. system:playback1,system:playback_2), and so on ... # audio_device = # Audio DSP plugin that processes audio before it's sent to the driver. Path to a dynamic library. # audio_dsp_plugin = # Will sync (block) on audio. Recommended. audio_sync = true # Desired audio latency in milliseconds. Might not be honored if driver can't provide given latency. # audio_latency = 64 # Enable audio rate control. # audio_rate_control = true # Controls audio rate control delta. Defines how much input rate can be adjusted dynamically. # Input rate = in_rate * (1.0 +/- audio_rate_control_delta) # audio_rate_control_delta = 0.005 # Audio volume. Volume is expressed in dB. # 0 dB is normal volume. No gain will be applied. # Gain can be controlled in runtime with input_volume_up/input_volume_down. # audio_volume = 0.0deaftolightParticipant11/16/2014 at 04:55Post count: 42
Bummer. I just tried the suggestions, and I still get lag even on NES games if the pi is clocked to anything under 1000 MHz. Really stumped. It doesn’t make sense, NES games should run fine at 900 MHz, or even less than that.
Also, I read in another thread http://www.raspberrypi.org/forums/viewtopic.php?f=78&t=6750&start=350 that the fact RetroArch is taking 95% CPU just to run NES games should be a bit of concern.deaftolightParticipant11/17/2014 at 00:30Post count: 42
I think it has something to do with the resolution on my TV. If I force VGA by uncommenting hdmi_mode=1 in /boot/config.txt, the NES games run full speed again. However, this makes emualtionstation look awful. I thought runcommand.sh was supposed to take care of this!
Unforcing VGA, and allowing to display in 1080p, emulationstation looked great, so I tried changing the runcommand.sh parameters in es_systems.cfg
I tried changing runcommand.sh from 4 to 1, but it did not help. I thought these parameters were supposed to allow us to see ES on our big TVs nicely, and then change the resolution when emulating.birthdizzParticipant01/05/2015 at 00:13Post count: 1
Similar issues here. I found a good compromise by setting the hdmi_mode to 4 which is 720p I think. Something that I did that might have hurt the experience is commenting out the overclock setting in the /boot/config.txt. I read that by default the RetroPie is OC’d. If that is the case when I switched to 720p I commented that out because I was thinking “oh crap I don’t have a heat sink”.petrockblogKeymaster01/05/2015 at 01:05Post count: 1827
We’ve been doing a lot of work to understand the impact of voltage and temperature on lifetime, and are now able to offer a “turbo mode”, which dynamically enables overclock and overvolt under the control of a cpufreq driver, without affecting your warranty. We are happy that the combination of only applying turbo when busy, and limiting turbo when the BCM2835’s internal temperature reaches 85°C, means there will be no measurable reduction in the lifetime of your Raspberry Pi.
so I wouldn’t worry :)
- You must be logged in to reply to this topic.