@bluedevil9754 said in Errors are logged to /dev/shm/runcommand.log after selecting default emulator:

Any leads into what I might be missing?

Yes, a couple

The N64 emulator is installed from within the RetroPie-Setup script, not with the procedure you described. The Errors are logged to ... message is a generic runcommand information message and doesn't mean an error has occurred, but in the event of an error, this is where it would be logged.

RetroPie setup already sets up one of the N64 Emulators ( I think Mupen64 ), so you don't have to install anything, especially macOS binaries that don't run on a RetroPie. Make sure your ROM is valid and try removing any game resolutions you've set, it seems the problem is from your TV not accepting the resolution you set.

@quicksilver Thanks, got it now. :-)

My first impression about the new case (BIQU Aluminium case) is fantastic. It dropped at least 20° Celsius while idling or watching preview videos at around 52° even with moderate overclocking (arm_freq=1300 core_freq=500 sdram_freq=500 over_voltage=2). Before this case, it was sitting around 70° without any overclocking. Now, I don't know how to test properly, but I am happy if it stays stable and cool and if I don't get any over heating warning symbol while playing 8- and 16-bit console games with shaders.

@thelostsoul

want dank said and the jump from a 1.2 GHz clock to 1.4 GHz

@madmodder123 said in Overclocking doesn't seem to work:

Try these out and use mupen64plus-GlideN64 for Star Fox 64
I can run at about 25-30 FPS with occasional dips down to 20-22 FPS, it is totally playable

Start Overclock Settings

arm_freq=1350
gpu_freq=525
core_freq=525
sdram_freq=500
over_voltage=6
v3d_freq=525
force_turbo=1
avoid_pwm_pll=1

End Overclock Settings

Keep in mind using force_turbo & over_voltage together will add the void warranty flag. Not that most care, but it is something to keep in mind for people who may not know.

@zac No pi is created equal. You can start off with the example settings from https://github.com/retropie/retropie-setup/wiki/Overclocking and tweak it from there. You also need proper cooling like a flirc case or a heatsink with fan.

If it's a voltage issue on the NesPi case, that seems to be very common. Some sellers on ebay or other places even disclaim that before you buy it. Running the Pi in the case for basic emulation or use seems to work fine but once you overclock and/or push it to the upper limit the voltage issue comes into play. I have a NesPi myself with the same issue. If you take it out of the case it works fine.

There is another thread about this you want to check out:

https://retropie.org.uk/forum/topic/12762/under-voltage-warnings-on-retroflag-nespi-case-best-power-supply/24

@ethanmlego there is a very technical equation to determine the closeness of the fan, size and rating of cpu, and the size of the fan.

But I will simplify it as distance should be directly proportional to the size of the fan. Judging by the distance away I'd recommend the following fan:

Primary concern would be to have proper ventilation to pull out the hot air being dissipated by the heat sink. I would recommend trying a few different placements while checking the temp from the terminal to see what works best.

Sorry to necro this topic, but according to the following link, avoid_pwm_pll=1 was removed from the firmware in October 2015 and is now always enabled.

https://github.com/Hexxeh/rpi-firmware/commit/260bc9c7589b3359485fc02fed8f56d4c5eaad9a

Does this affect overclocking and, if so, how?

The Wiki still contains the following, which may now be incorrect. Does anyone know for sure?

By setting avoid_pwm_pll=1 (which negatively affects 3.5mm audio quality) you can overclock the individual GPU components with the parameters:

v3d_freq - speed of OpenGL 3D graphics processor isp_freq - speed of Image Sensor Pipeline h264_freq - speed of x264 video decoder (not used by emulators, used by Kodi)

@H3X1C https://retropie.org.uk/docs/Overclocking/

@edmaul69 seems logic :) so yeah I'll start by the standard installation of everything, then try to run every games I wish to play on, and then see if I need any other manipulation ! (I'll buy and install the raspberry pi in the fan equiped case in case of I need to try it out.)

thanks for your guidance edmaul69 !

Nice!0_1482936644126_8 Bit Logo.jpg

I SO NOT TROLL

@dankcushions thanks what is the RAM value txt for the config.txt file edit pls.

Hi all. To make my question crystal clear, basically I'm looking to know the following.

Do you benefit at all from setting "gpu_freq=500"? Does it set the frequencies for the various GPU blocks to 500 MHz without "force_turbo=1" enabled?

I'm hoping it does because being forced to disable the dynamic clock driver to do this seems like an unfortunate design oversight for a hobbyist circuit board. It's bugging me so much I think I'm going to be trying to determine the answer with my test bed Pi3 tonight. Hoping someone out there has an answer for me though. The way the documentation is written seems to indicate that "gpu_freq=500" might work, but setting the individual blocks (such as v3d_freq=500) doesn't, or that's one way to interpret it anyway, its not 100% clear about that. But in the worst case scenario, if the 3d block is locked at 250 MHz, it will probably stay that way as I really don't like the idea of disabling dynamic clocks lol.

@Wizardling Glad I could help. That 5V fan should keep things nice and stable at 1300 MHz. I do not recommend overclocking the CPU at all without active cooling, but sounds like you have that covered. Best of luck to you in your experimentation friend.

Excellent work....very very thorough. Love it!

@BrockBoyts said in Active vs Passive Cooling:

@dankcushions

I was hoping that overclocking would fix any subtle lag issues. This has mostly been noticeable in games that require accuracy.

well, overclocking can potentially improve framerates on CPU-bound games, but 'lag' can mean many things. if you mean input lag, well that can potentially just be a problem with the emulator or emulated hardware, or your controller, or your tv, etc. overclocking won't help here.

Examples:

Galaga on Lr-Mame2003 without shaders and overlays plays super smooth. If I turn on the overlay and shaders (CRT effect) there is a subtle lag.

this sounds like GPU being your bottleneck, or possibly RAM being the bottleneck. you'd need to experiment with overclocking both to resolve this (or perhaps use lr-fba-next and see if that does better with this game)

Metal Slug 1 on Lr-Mame2003 when two people are playing and there are a bunch of sprites are on the screen there is noticeable lag.

this is probably just what the original hardware would do. there are other solutions - see https://retropie.org.uk/forum/topic/2305/metal-slug-slowdowns-rpi3

Mega Man Zero games on GBA have a lag too and those games need accurate response times to play.

no experience with this.

I am only considering a cooling solution because the inside of the cabinet gets pretty warm and may contribute to the pi overheating if I overclock. If I do not overclock the Pi I have no concern for the heat.

the pi is pretty good at protecting itself from heat and will let you know when it's temperature throttling via on-screen symbols. IMO if you still want to overclock, just do it and then work out if cooling is required from how it reacts.