@tr33x0rs Glad you're sorted.

My suggestion was really to lower the entire volume in ES's sound settings - I was hoping that, on Windows, it wouldn't change the entire OS volume settings.

Have a great weekend.

@jdog35421 said in Controls mess up after I open a game.:

When I restart my pi by turning it off

are you pulling the power cord? if so, you could be corrupting your card!

@mitu I never tried typing \retropie\ in like that before but it worked. Not sure why it's still not showing up though. Thanks!

Thanks! That solved the issue!

Performance-wise, if your Waveshare 3.2" is able to reach 73.7 Mhz or higher, you will get a solid 60fps on the display. In such case, you can try enabling NO_INTERLACING in config.h. SPI bus speeds 66Mhz and higher will also in practice run at 60fps. 40Mhz-60MHz generally resort to interlacing every now and then, and < 40 MHz will typically run fully interlaced (e.g. ILI9486 based displays)

This video

is running a Raspberry Pi CM3 with a Waveshare 3.2" with SPI bus at 66MHz.

@lostless Changes are apart of life haha. Most have been a problem i was totally oblivious of. Glad you like the update, i'll just have adapt. Thanks for even understanding what i was trying to explain and taking the time to reply Lostless. I expected zero replies to my question honestly. Have a great weekend!

@douga Thank you!

@kessler94 Press Start+X to open the RetroArch menu, navigate to Settings -> Video -> Aspect Ratio, and change it to something you like. When you're done, remember to go to Configurations and save your changes.

@dankcushions
Thanks. Emulation is always funny. I will mess with the nes emulator settings from that guide. I love this project though, such a good use of raspberry pi.

It works.
Thanks

Not sure if this helps. I had problem where the 2:nd player use the P1 controls.
. Needed to add:
usbhid.quirks=0x16c0:0x05e1:0x040
To the /boot/cmdline.txt to get the player 2 control to be detected. Not sure if this is related at all.

https://github.com/RetroPie/RetroPie-Setup/wiki/Xin-Mo-Controller

@odosayshi
Will do the same If I found a fix!

The build fails because of a missing header file

./libretro-common/include/glsym/rglgen_headers.h:27:10: fatal error: EGL/egl.h: No such file or directory

Normally this should be part of the package libegl1-mesa-dev - you can manually install it before attempting the installation with:

sudo apt-get -y install libegl1-mesa-dev

The gist of the Getting Started guide for Arcade is that users need to 1) pick your arcade emulator and then 2) you find the exact romsets designed for that emulator version

Your emulator is mame2003 and it will only work with a MAME 0.78 collection. If you have a MAME 0.78 romset collection you will not get CRC errors and the games will, generally, play.

The MAME 0.78 romset collection is very easy to find on the internet. No Dark Web required, just a search engine :)

I was struggling with the config file saving using lr-atari800. I uninstalled it and installed the regular atari800 emulator. Now the config file works. I also had to set the display to something I could see first. There are presets for the display that work fine.

@rlmariz See https://retropie.org.uk/forum/topic/3/read-this-first - we don't support 3rd party images. Ask the image creator about it or install the RetroPie provided image from retropie.org.uk/download.

@tgilly If you'd like to diagnose the problem, then you'd have to provide the necessary info. No, I don't think 4.4 is unstable, but your problems look like a power supply problem, the system throttling itself down automatically, or more related to the fact that your ROM folder is mounted over the network.
Check if your power supply is right up to the specs and then try running the ROMs from the sd card for a test to see if you get the same symptoms.

FYI : Just opened a similar question here : https://retropie.org.uk/forum/topic/17843/retropie-4-4-stability-controller-issues

Nothing worked too fix the issue. What I did was, rebuilt a new image. Then I used the ssh interface to do all of my keyboard commands. As soon as I connect a keyboard directly to the pi. RetroArch starts acting up.