@jonnykesh said in Error formatting 64Gb USB:

@landyvlad Windows is a pain the the ass. Use a third party tool like this https://www.sdcard.org/downloads/pls/index.html or this https://www.easeus.com/partition-master/best-fat32-format-tool.html

The former didn't give me any options and formatted the usb stick (which it said was an sd card) as ex-FAT rather than FAT32.

The second easeus worked fine and quickly. Cheers

thanks!!!! i missed this.... :) PS: i had spaces in rom's name.... removing spaces they works. now seeing the story of cfg mapping :)

@monkeydisco don’t give up on heat sinks. They can help a lot (they do in my setup). But use a thermal compound instead of mystery tape.

Ok. Thanks for the answer !
Wasn't sure if you needed that driver for any on/off switch hooked up to the pins.

@lostless

Try it again later (if you have not done so already). Had the same issue and just worked on another system and went back to it the next day

Fixed with last commit update to SDLPoP
https://github.com/NagyD/SDLPoP/pull/141

@pacmanlives this is fixed in RetroPie if you update. It deletes the broken repo.

@thomen Normally, I would suggest checking RUNCOMMAND, but you mentioned you are using Attract Mode. I would have expected Attract Mode you to be explicit about which emulator gets used, meaning, you would know what emulator because you had to set it up that way.

Perhaps someone more familiar with Attract Mode can add a better answer.

Yea I've played around with it a fair bit though so it could be related to something non standard. Just wanted to set the retropie menu view to Basic and everything else to auto in ES and thought this was a way...

@ckp sometimes the filename has (!) or (u) right before extension, and the scraper don't recognize the game just because of these things. Take a look and try again without these things.

@mrinfected101 Well, I am at a loss. Since your original post says that the emulators work with the keyboard, just not with the joystick, I gotta believe there is something amiss with the adafruit/retrogame configuration. In some ways, RetroPie is working, but your adafruit stuff isn't.

I know controller setup is the most common challenge people face with RetroPie, but this one might be better asked of Adafruit. Perhaps they have some specific suggestions for when this comes up. I would definitely open a dialog on their forum if you haven't already.

@trailjacker said in Lightning Bolt / General Electronic Question:

Many users worry that that they may "supply too much power" by using a higher rated supply.

Yes, because they do not understand that in electronics, a device will draw the current that it demands. For example, I buy a green LED. It requires 25mA to illuminate. I decide to power it with a 3A power supply. The power supply laughs at it and delivers the 25mA with 2.975A spare capacity to power other things like a Pi.

There are a couple of themes which would work with this frame, like crt-centered:

alt text

But it would still be nice if the theme had the matching shader applied for the scanline/pixel smoothing effects...

I finally got this to work. The key was installing both xboxdrvr and xpad. I also copied the working xbox 360 controller config from the wiki (here) and restarted the computer. After that, all the controls started working except for the d-pad. I had to go into the retroarch RGUI menu (the keyboard was also working now, so I had to use it to navigate the menu since the d-pad wasn't working) and adjust the controls for the d-pad in all the emulators. For some reason, it was the only part that wasn't working. I did notice that my triggers are handled differently for the two types of controllers. The 360 controller the triggers act as axis while the rock candy one is treated as buttons. This changed the axis that are used for the d-pad (which might also be weird. I would have expected the d-pad to be buttons, but that's no the case).

At any rate , I finally got this working. Hope this helps if someone else is having similar issues.

@dankcushions said in How do I delete a rom that is causing problems when I can't type?:

@princegumball the screenshot you posted is already in the command line, assuming yours looks the same. i don't know why you wouldn't be able to type.

I missed you saying this. Maybe I wasn't clear enough. Both me and the other person can't type after that error. Yes, it's a command line. I've found the only keys that work once it gets to that point are shift+3 and shift+~ and those just make little symbols. Can't press enter. Tried unplugging and replugging they keyboard. Nothing. Tried everything everyone has mentioned above to try to get a command line before the error comes up and that hasn't worked. The other person never said if anything worked for them.

@ckp bad connection on the supply probably

@mitu I've already reinstalled retropie like 4 times and I swear, every time I touch the controls and attempt to enable the analog stick on FF7, the controls just break forever. Even if I don't save anything. It's so incredibly weird.

I've reinstalled for the fourth time and it's working (without analog) on FF7, so I'm just going to not even touch the settings. I really don't want to redo my RetroPie image anymore.

I'm just honestly baffled I'm the only person that's ever had this problem with FF7 on RetroPie.

Is the controller compatible with Linux ? The only genesis style hyperkin controller on the vendor page says it's compatible with any 'Genesis' system, but doesn't list any other.

Try running jstest to test if the buttons on the controller register in the system - https://retropie.org.uk/docs/RetroArch-Configuration/#determining-button-values.