@reesk92 said in ROCKPro64:

shoddy says who?

Up until a few days ago, I was under the impression that it was widely accepted that N64 emulation was notably lacking when compared to most other systems. I've since come to learn that this is somewhat of a controversial matter. Personally speaking, I find the current state of N64 emulation to be sufficiently flawed enough that it doesn't appeal to me. However, everyone has their own threshold as to what they find acceptable and that's certainly as it should be. While I will personally continue to wait for things to improve, I'm truly glad N64 emulation has reached a state that many can be happy with.

@dankcushions @jamesnj thanks for the replies, @jasonw how did you install your fan< did you put a hole in the case and place the fan there? and if not how did you install it because the case I will use has 2 holes/vents for airflow, one at the top and one at the bottom, so I am wondering whether the fan should go at the top or bottom vent or should it be installed into the case.

@breyyne If you have afolder for DS then it is probably installed. A
Are the rom extensions .nds or .zip?

OK, so I've been googling up a storm looking at the options. I think I'm either going to go with a piglow, and use some code folks have already put together. Seems like the three arms can show something like Temp, CPU Load, something else (I can't remember).

But what really looks like it'd be cool is the Displayotron. Seems I could set it up to show the system and ROM running on Retropie. And I figure the backlights could be setup to have a color that'd match the system (like Red for Nintendo or something). And then use the bargraph to show CPU load. But what I'd love to do is use the joystic on the Displayotron as a safe shutdown button. Could I do that? Does it sound at all reasonable?

@war3zlod3r How about checking the news and the download page ?

Please give more details about your system (https://retropie.org.uk/forum/topic/3/read-this-first), especially the version of RetroPie used.

@gregbrooks9802 said in NES Retro8 Controller Not Detected in Emulator:

How do I remove the udev rule? I don't know if I have it or not. I presume I do because earlier I was attempting to change it.

You just delete the line you added from the file you edited.

@lkmaster Replying to a 2 years old thread will not get you answers for the current version. Please start a new topic and state your problem/question there.

No problem.
Oh and i would suggest testing out most of your games using fbalpha first before going to mame cause i found some games works better using fbalpha over mame.

If you have the games in the zip folder still it wont read it which is why you would need to extract the image files in order for it to show up.
So the formats that it mainly reads are ISO, IMG, Bin/Cue and PBP so make sure your games in that format when in the folder ok.

I only own pi's and a cheap pc with RetroPie installed so i wouldn't be too much help when it would come down to using a TinkerBoard.
But i am sure there might be a video tutorial of something that got it working which you could follow what that person has done and see if you get it working for yourself.

@mitu Nothing , i only put my usb stick in the raspberry.
But i had it and install it from new now its working like u said .

Thanxx Mitu :)

Hi all,

I used mame4all because I was doingt it wrong.

After reading the instructions on the link mediamogul post I moved to lr-mame2003 wich seems to work well for the 3-4 games I have played.

I just got two arcade joysticks form amazon and will mount tomorrow. Lets see how it works....

ahhhh I forgot to comment, I own Rapsberry 3...

Regards and have fun

Funtana40

I had the same issu, and tried to update and test this game from time to time.

I am happy to report that this time the game did not crash after the cut scene

I am using retropie 4.4, with reicast default options.

I don't know if this is fixed with a very recent reicast update, but the only differant thing I did beside the update is format the VMUs, by booting to the Bios (press A + B + X + Y + START while booting a game) choose FILE erase all on both VMUs of controller A.

Suggest your power supply. A compatible power supply and one that is GUARANTEED to give the extra power the PI3B+ needs are very different

I could buy an adaptor here in UK for cheaper than you paid that claims to be 2.5A but under load would drop drastically causes no end of grief. Great for low power device like charging mobile phones but hopeless for a high power device that NEEDS a good steady supply like the PI3B+.

People seem to rate the CanaKit 2.5A power supplies, maybe look for them

http://www.wirelesshack.org/what-is-a-good-power-supply-for-the-raspberry-pi-3.html

I personally bought an official 2.5A power supply for the PI3B I have, a lot more expensive than a 'standard' power supply I could have usually bought, but its never given me any complaints after reading power supplies can give lots of strange problems as they work then don't or random errors

My set-up doesn't stress the supply in any way and never had had weird instructions,. I'm overclocked to the limit, running a 1TB USB powered external hard drive for RetroPie, running OSMC for KODI and running a USB powered wireless dongle for the PS3 compatible joypad, plus USB keyboard. All works fine, plus a tiny fan to keep the huge heatsink cool

@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.