Glad to hear that!

@mitu problem solved! Saving the core config was the game changer. I still get the "controller not configured" message, but now it works :)

@mitu said in Logitech F310 not working: @raspy said in Logitech F310 not working: I would recommend leaving the switch on "X" and the mode button off (no light) That would probably be the correct choice, but the poster said it seems to be clone of the original controller and BUT I do not have the X - D switch on the back that seems to be everyone's issue That's correct, I don't have any button along the back side, so it could very easily be a clone. I didn't think of that, which could explain why all the front buttons are numbered 1,2,3,4, etc. Even the shoulder buttons are numbered in the same vein. I've been trying to sort things out from the advice given, but so far, no luck. The controller isn't being recognized. Even when I use a keyboard to navigate and try to configure the controller. ☹

Bingo! Thanks for the assistance

@dankcushions said in Weird issues regarding retropie-setup and mupen64plus.: @r4l get rid of the overclock. any stability/freezing problems = get rid of the overclock i don't know why you're editing files. mupen64plus should get automatically configured when you configure your controller in ES. if you're using a proper n64 controller you may need to do some manual tweaks after that to get the c-buttons working nicely, but i would take one step at a time. Do you know how buttons are mapped in mupen64plus? They are automatically configured, often times the WRONG way. You have to turn off hotkeys in autoconf.cfg and make controllers fully manual in mupen64plus.cfg. Then you have to set the right button mappings in InputAutoCfg.ini. Basically I set up the controls in ES, then I fix them in InputAutoCfg.ini because if I don't, they are totally wrong. As for the overclock, I am using a Mackertop 5.25v 3a PSU. Even at 1.4GHz, the system is totally stable. Everything else works fine, except N64. I guess I could try going to 1.3GHz and seeing what happens, but I don't think that's the problem.

One of the creators of retrorangepi was able to solve the issue for me via Facebook: "from terminal: wget http://www.retrorangepi.org/asplashscreen sudo cp -v asplashscreen /etc/init.d/ If you want to change the boot screen and tune or enable splash video, edit the file: sudo nano /etc/init.d/asplashscreen (in plain terminal) OR sudo pluma /etc/init.d/asplashscreen (in Desktop mode terminal) comment/uncomment lines in do_start function (remove or add #)" Worked like a charm. Hopefully this might help anyone who runs into the same issue.

That guide is outdated (I think it was around RetroPie 2), the mk_arcade_joystick module can be installed from the Retropie setup drivers menu.

thank you, I will do that! I appreciate your response.

@colebeansbroskie if you have two sets of joysticks and buttons you have to set up the buttons the exact same way. You never have to configure player 2. Once you set up one, after rebooting your system both will work. If the buttons are different on player 2, it means you put them in the wrong order. You need to set up player one then reboot. Then go into a game that uses all your buttons and in that game press a button on player one and see what it does. then find that same button on player two. Now put that button in the same spot player one has it. Keep doing that until all the buttons match.

@Caligula88 first thing to note: Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first Now, 2 questions: Did you configure your joysticks on emulationstation? Paste here the output of this command: ls /opt/retropie/configs/all/retroarch-joypads/

@Bender2k no bt problems here. Do you have a heatsink on your processor? If so it could be causing issues. You could try turning the heatsink 90 degrees so the heatsink fins are facing another direction. The heatsink can act like an antenna and cause issues. Other than that not sure what to tell you to help you.

@WhyCan'tIJustDie Thanks, I am new to these forums, if I can can how would I mark this a solved I think if you asked the questions with unresolved then you can mark as resolved. I'm actually not sure how it works lol

i figured as much as far as i understand he installed retropie 4.1 and attract 2.0 the only thing it has is some themes and art files added for attract mode and a few sections pre set up in attract mode ...no roms or bios files included ...i guess it was worth a shot of seeing if it mattered or not ... i would still like to know with just a normal install of retropie 4.1 and attract mode 2.0 when you add the emulator in attract mode, which is working and playing roms in emulation station, could it be that a .cfg file in attract mode just is not listing the start command properly ? from what i understand attract is just an overlay and alternative that still references retroarch to run the emulators ?...or is this just a problem with supported emulators in attract mode thing? thanks for the answer though as i may try just that with full clean installs

I'm new to this stuff myself, and it is happening to me also. I mistakenly did a kernal update while trying to navigate around, and 20 minutes later I had no way to exit apps like Retroarch and only tested with GBA roms, but both I attempted would not work right for my NES30 Pro. I'm going to have to start over also. I hope they fix this issue soon. I've had to unplug twice because of this, and going to learn SSH before trying any more games.

@Rascas This seems to have worked! Thank you. If it stops I'll let you know.

@acraigl I don't have a great answer for you. Specifically for GLideN64 there is a source code repository I have been checking since the project lead gonetz said a new version is imminent. It actually was just published as a specific 2.0 release yesterday. Still has some regression issues like Mario64 though. GLideN64 code repository blog Not sure how active mupen64plus or glupen is for actual emulators.

I have the exact same problem. Though I have two usb controllers. How did you debug and change the UDEV stuff?

Ok can we slow this down a bit please, I currently don't have access to my pi and I think my roms are in the right place because they are coming up, I used the USB transfer method. I will get back to you when I can access the pi