I too ended up compiling the current stable build. Had same issue as you did with SDL 2. SDL 1.2 works great. Only items needed on the make builder were

./setup_t -t larm -api sdl

Enjoying Ancient Art of War on the Mac via RetroPie :-)

@mitu Thank you very much for the clarification!

#uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

#uncomment this if your display has a black border of unused pixels visible
#and your display can output without overscan
disable_overscan=1

#uncomment the following to adjust overscan. Use positive numbers if console
#goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

#uncomment to force a console size. By default it will be display's size minus
#overscan.
#framebuffer_width=1280
#framebuffer_height=720

#uncomment if hdmi display is not detected and composite is being output
config_hdmi_boost=4
hdmi_safe=1
hdmi_force_hotplug=1
hdmi_drive=2

#uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=2
#hdmi_mode=9

#uncomment to increase signal to HDMI, if you have interference, blanking, or
#no display
#config_hdmi_boost=4

#uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

#Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

#Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

#Additional overlays and parameters are documented /boot/overlays/README

#Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
#Enable DRM VC4 V3D driver on top of the dispmanx display stack
#dtoverlay=vc4-fkms-v3d
max_framebuffers=2

#flip screen 180 degrees
lcd_rotate=2

#disable touch screen
#ignore_lcd=1

#disable onboard bluetooth
dtoverlay=pi3-disable-bt

[all]
dtoverlay=vc4-kms-v3d
start_x=0
gpu_mem=128

That depends. First and foremost, it's a secure behaviour to only give yourself administrator rights (e.g. via sudo) when absolutely necessary. Also, if you happen to change the file's owner or permissions by accident in a way that the normal user can't access them anymore, it can cause further problems.

In short, by training yourself to use sudo only when necessary you avoid future problems and, at worst, security holes.

In your particular case, mere editing an existing file shouldn't make you any trouble, but if the file doesn't exist, you'll create it with the owner root instead of pi. Because a new file will be created with only write permissions for the owner, any application like an emulator that's run by pi wouldn't be able to write to this file afterwards.

Again, that may or may not be a problem depending on the file, but avoiding to use sudo will negate this uncertainty alltogether.

🙂

In general, if the command line does strange things, it's a good idea to check if the command was entered correctly. As in this case, one missing or wrong character can be the culprit.

@GeekOB
No Prob.
I‘m very happy for the pi4 Version:)

@mahoneyt944

Thank You Very Helpful , I Appreciate that

@helloThere Well that’s weird. Mine is completely empty. Hopefully the image attaches correctly but the box has no code in it like yours. Maybe I missed a step?666C68D6-5BA0-45D6-8402-FC7B9A265938.jpeg

EDIT: I have looked into it more, and realized that it was because overscan was disabled. I neglected to remember this for some reason, but I have fixed it.

@simpleethat thanks!

@gomisensei That worked perfectly, thanks!

One more piece of the puzzle...at the end of my script, if I remove the GPIO.cleanup(), then the light stays on.

But, in subsequent calls to my script, I receive a warning that the channel is already in use. It doesn't stop the code, but the programmer in me doesn't like warnings.

My question now is why does the cleanup function change the output of the GPIO pins?

@helloThere I use win32diskimager on my PC and it works very well. The interface is fairly intuitive too. Hopefully it works for you.

@Folly

Thanks Folly

this really is going to help me

Thank you !!!!

The hotkey is defined in the RetroPie controller config. You can then customize the hotkeys in RetroArch.

Or I believe you can set up "shift key" behavior in the I-PAC config to do the same thing.

If you still want separate buttons that's fine, was just a personal preference to have my controls be minimal.

I haven't installed any leaf buttons/sticks myself, I guess you can check the other forums here or google around for more info.