hi, just following up on a very old topic!

Latest retropie build from the retropie site -downloaded sept 22. I have an ipac 2 and a physical joystick, that works Left Right Up Down and fire in all other retroarch emulators.

I initially had the same issue - I've set the keyboard to port 3 as above, and kempston as port 1 and both lr-fuse, and fuse, 'sees' the L R U D and fire inputs as kempston.

However - when I press a direction the game i'm playing pauses. Same if i use the usb keyboard attached. I've tried changing the options/time to release the key in MS and it seems related. its almost as if a direction key, holds down the key and freezes the emulator or game, until I move in another direction and so on.

I just tried port 1 to retropad and used the arrow keys on the usb keyboard - same effect.

Any advice please welcome how i can address this!

thanks

@Retro-Arcade-Fan
Last I looked it was still part of the setup script. Can’t remember if it’s an experimental/optional package though. But it does work. Just scraped with it the other day.

@mitu Ok, I think I figured this one out. I added the following line to the retroarch.cfg in the /opt/retropie/configs.hdmi/c64/ folder:

input_player1_select = "nul"

and that seems to have fixed it.

Thanks for your help! It did actually make me start looking at a few other things and pointed me in the correct direction!

@mitu

Great! Thank you!

I also see the optimized settings I did for each game in there as well. Perfect!

@MetalGamerFil
Please supply the information requested in
https://retropie.org.uk/forum/topic/3/read-this-first

In which mode are you using the controller?

I had some trouble configuring mine with a couple of buttons when it was in X-input mode (X + Start when turning on the controller). Some of buttons were showing up as analog axes instead of button presses. I solved it by changing the mode to either Switch mode (Y + Start) or D-input (B + Start) and re-configuring the controller.

I think part of the problem is EmulationStation doesn't want you to use an Axis when configuring certain buttons. Not sure if this could be fixed in the auto configuration. I believe you could manually edit the controller config to get around that though.

@dankcushions Thank you, I'll use that guide

If I connect the dots here and in addition to the merged changes [1] @pjft was referring to, I see also the option that the file log might choke caused by a specific combination of many log writes, threaded loading and slower file operations by rpi3 and/or sd-card (or even undervoltaging, which is crucial to sd-card operations).

While I am unable to reproduce it, it might be considered to reduce the log output of missing theme resources by lowering the log level (WARNING to DEBUG). It would reduce the probability of file log chokes and would also speed up the normal ES boot:

diff --git a/es-core/src/ThemeData.cpp b/es-core/src/ThemeData.cpp index cb1b265..45b54a6 100644 --- a/es-core/src/ThemeData.cpp +++ b/es-core/src/ThemeData.cpp @@ -517,11 +517,11 @@ void ThemeData::parseElement(const pugi::xml_node& root, const std::map<std::str if(!ResourceManager::getInstance()->fileExists(path)) { std::stringstream ss; - ss << " Warning " << error.msg; // "from theme yadda yadda, included file yadda yadda + ss << " Message " << error.msg; // "from theme yadda yadda, included file yadda yadda ss << "could not find file \"" << node.text().get() << "\" "; if(node.text().get() != path) ss << "(which resolved to \"" << path << "\") "; - LOG(LogWarning) << ss.str(); + LOG(LogDebug) << ss.str(); } element.properties[node.name()] = path; break;

Additionally a mutex for log file write operations might be used as outlined here [2] to make fprintf() [3] thread safe.

[1] github.com/RetroPie/EmulationStation/pull/774/files#diff-20f861dd5841312f45eb90d5a56cd5addad0657c66605d6235696a345907e15d
[2] https://stackoverflow.com/questions/43427405/c-writing-to-a-file-in-multithreaded-program
[3] https://github.com/RetroPie/EmulationStation/blob/52c04d77864287aa0ae7f484460966d8253079df/es-core/src/Log.cpp#L77

@Retro-Arcade-Fan which retroarch config files are checked and applied when present can be seen when you start any libretro emulator with the verbose logging (select verbose logging in the runcommand menu, this menu can be entered when the screen "Loading xyz.file ... Press any button to configure ..." screen is shown).

Not all folders and files must be there, but if they are, they are processed.

For instance this is shown on my side when I start Beach Head II with verbose logging:

[INFO] [Overrides]: Core-specific overrides found at "/home/pi/.config/retroarch/config/VICE x64/VICE x64.cfg". [INFO] [Overrides]: No content-dir-specific overrides found at "/home/pi/.config/retroarch/config/VICE x64/c64.cfg". [INFO] [Overrides]: No game-specific overrides found at "/home/pi/.config/retroarch/config/VICE x64/BEACHHD2.cfg".

Check the output with less /dev/shm/runcommand.log on the commandline. It will give you hints where to put the files on your setup.

HTH

@YFZdude
Thank you! Ill give that a try!

@Blooney92 said in Emulation Station Crashed!:

Also, probably another dumb question, but if Emulationstation itself is corrupted, will creating my own SD card and using that even work?

As long as your sd card isn't the cause of the original corruption then it should be fine. If your card is dying then a problem will likely develop at some point after you reimage it.

It turns out the issue was between the controller and the chair.

I'm posting my resolution here in case someone else ends up with the same issue and goes looking...

I miswired the controller (it came with no documentation), but I came across this blog post (https://cy-822b.blogspot.com/2016/08/the-cy-822b-usb-led-joystick-controller.html) that showed this image:
c0fb63ff-f849-4c20-b512-ae2dd514b54c-image.png

The controller board looks like:
856a91fc-99f3-4ced-b08c-acd40ff39054-image.png

The buttons have a 2-pin connector on them so I figured the connected to the lower edge of the image above. But the connection actually happens in the button housing and the 3-pin connector is more than just for the LED, it also contains the switch wiring. So the 2-pin connector connects into the button housing and the 3-pin wire from the housing connects into the controller board.

I went back to the original Amazon page and found that there are some pictures that describe the wiring, but not terribly clearly:
cd4a53c7-a851-42b4-875b-919802fd6439-image.png

In the end all on me. I hope this helps someone else in the future.

Cheers,

Steve

@sleve_mcdichael said in How Do I "Wake Up" My Retropie Audio Sooner?:

You can force the audio channel open with vcgencmd force_audio hdmi 1 but I'm not sure where you'd put this to have it take effect before the splashscreen. You could probably put it directly in the splashscreen script itself at /opt/retropie/supplementary/splashscreen/asplashscreen.sh, but it might get overwritten if you update.

I tried fiddling with this, but it became a bit too cumbersome. So I just added an audio queue to my splash that should help activate it sooner.

In the meantime, would it be possible to play two splash screens (one small one to "wake up" the pie's audio, then the second could be my main)? Or if I turned on an image splash as well, would that work to load it before the video in order to get the audio channel active sooner? Or is it just a one and done setting for a single video loading at startup and that's it?

@yserra Hmm, shoot. I wonder if I have a greater issue. I did as you instructed for the C64 and the keyboard is still having the same issues. FWIW, the same issue exists when I connect a straight up PC USB keyboard. I also notice the Scoll lock made no difference.. then again I test that after I edited the cfg, so maybe it doesn't work because I set it to "nul".

@Ashpool said in Can't get retropie 4.1 to boot in 720p:

. Is it possible to activate such a function here (please ignore if this forum actually is already warning the user about it) ?

It is activated, but the warning was probably shown to @RickyTan, your reply was later.

@sleve_mcdichael said in CEC control - Pi turns TV on when booted:

echo 'standby 0.0.0.0' | cec-client -s -d 1

Thanks @sleve_mcdichael. I did try both. It's odd that I can turn it on, but not off. But I've tried both methods. I appreciate the assist though. Maybe someone else will chime in.

@hjk321 said in Xbox One Controller won't connect the "official" way but WILL connect via bluetoothctl.:

So at first glance it might seem like a xpadneo issue, but it's actually not

It could be, if your controller has the latest firmware, but xpadneo's version is less than v0.9.2.
Update your RetroPie-Setup script, and then re-install xpadneo. Try pairing the controller again - either through the RetroPie menus or via bluetoothctl.

@windg that worked. thanks @windg and @mitu

@mitu There hasn't been a reply on that thread in months...

I'm getting both an 'xinit: unable to connect to X server: Connection refused' response to StartX
and a response " *failed to add service - already in use?" to emulationstation.

Do you think it is related to autologin settings? It's as though both the services are started but I'm outside them (I guess because George's script itself called Xinit ... though I uninstalled Meso, Box86 and Wine).

@mitu said in Which files/folders to backup?:

@retrodaniel said in Which files/folders to backup?:

know that I changed the configuration of some games specifically during emulation, but I have no idea where those are stored. Could anyone point me to where they are, please?

The overrides for cores/games should be stored in /opt/retropie/configs/all/retroarch/configs, each core has its own folder for overrides. If you're backing up /opt/retropie/configs/all/retroarch, it should be enough - you can restore them afterwards.

Other than that, the backed up folders you mentioned should be enough.

Amazing! Thank you for the help :)