Update:

PI Imager on Windows 7 runs fine but stuck at the downloading progress. I managed to complete the task with UUByte DMG Editor.

Appreciated for all the suggestions in above! Have a good day!

@ReadyPlayaWon said in Mad Dog McCree Dos Box Help:

3DO

Hi ReadyPlayaWon

May i ask ... i did get my pi 4 and im enjoying it alot

i just tested the mad dog on 3do emulation and i was wondering , im using the dolphen bar/wii mote to use as a light gun ... i dont know how to reload ... any advice or tips?

@mitu said in Can't exit game in MAME:

@Rhees
Look at the Runcommand start message - it will tell you what emulator it's starting.

EDIT:
Also try

input_enable_hotkey = 8 input_exit_emulator = 9

You don't really have a gamepad, but a keyboard, so the _btn might be extra. Where have you added these settings ?

MAME4ALL Alternate Fix: I battled this issue for a few days before I found a fix that worked on my system (RPi 3B) when the solutions above didn't work.

With both Joypad/Controller and Keyboard plugged in to RasPi...

start a game that uses MAME4ALL press TAB on keyboard once game starts (brings up User Interface menu) use keyboard arrow keys and ENTER to... select "Input (general)" arrow down to "UI Cancel" - this is the exit game command ENTER (waits for button to map) (on Joypad/Controller) press and hold both your the buttons you have already mapped for enable_hotkey and exit_emulator. Note: I don't think you have to use those specific buttons, it just keeps it consistent with your other games and systems I hit enter again on the UI Cancel line and hit the ESC button on the keyboard to make sure both the joypad combo and esc still worked to exit. arrow key up or down to "Return to Main Menu" arrow key down to "Return to Game"

You can use this method to map the other UI controls (UI Up, Down, Left, Right, Select) so you can navigate the UI without a keyboard in the future. It's a good idea to set a two-button combo to bring up the UI menu (Config Menu is the first line of the Input - General menu).

Later I found this video that walked through the steps:

@mitu fixed

I did some more tests and I guess I found out what was causing this problem. After cloning the sd card everything works fine until I copy my rom's to the ssd. I just attached the ssd with the usb adapter to my Ubuntu machine and copied everything there to get faster speeds. But it seems that this method changes something in the filesystem that then causes all sorts of problems when booting from the ssd.

I now simply copied the sd card to the ssd again to get a fresh start and then copied everything with SFTP and now everything seems to be running fine.

Scratch this. I have to rename (or symlink) the folder to megadrive. I will try it out when I am back at my Pi and report back.

@Darksavior said in PI4 8GB & Retropie - Is it supported?:

@Clyde I'm not sure if installing from source are made to use the extra ram, but it'd be a plus if it could.

The buffers / disk cache that show up in free -h and your desktop tool shouldn't be affected by the installation method, as AFAIK they are managed by the Linux kernel itself. But as such, they'd only speed up repeated loading of the same files, e.g. the pictures or videos when browsing games in Emulation Station.

@stoo Having lots of differences between FBNeo & MAME for system16 based hardware isn't surprising, system16 is a historical driver for Final Burn (first FB driver and first emulator to run that hardware, the emulator's name is actually based on "After Burner"), current FBNeo driver is built upon that initial driver. You should report the glitches at https://github.com/finalburnneo/FBNeo/issues, we can't fix what we don't know about :)

The pastebin link is ok; the error Bluetooth messages seem to be the only ones available (no detection info), but they don't provide any indication where the fault is, unfortunately.

@mitu
I'm using dpad always I'll try the test and report back.
Jstest passed all presses worked.
It seems to be behaving after following a youtube
Guide for resetting the controller and holding down analog sticks for 30 secs etc.. Also I cleaned the sticks.

I know I'm not using analog IN ES but if they are sticking sometimes maybe it causes issues.

I get the problem almost everytime and so far the last 4 reboots it's been fine.

Update problem has not come back since cleaning and following analog drift fix guides on YouTube. I didn't have to take apart controller. Very pleased.

@MRivera279

Checkout the Wiki

https://retropie.org.uk/docs/Cheats/#enable-cheats

@Oxopi said in Controller with retropie:

The left analog up, down, left and right says already taken if i hold against the setting it then says not defined
The same goes for the right analog

That indicates the analog sticks might emit the same input data as the D-Pad. I notice there's an Analog button on the controller - what is the function of it ?

You can exit EmulationStation (via the menu or just pressing F4) and test the gamepad's buttons with the jstest command by running

jstest /dev/input/js0

and pushing the buttons and operating the analog sticks - see if the analog sticks are overlapping with other buttons/D-Pad. Exit the test by pressing Ctrl+C.

Also what should the hotkey be set to

You can leave it as default - don't set one and you'll be asked to use Select - or try to use the raspberry button at the top.

Correct, @mitu , I created a separate system that lists the conf files:

<system> <name>p2000t</name> <fullname>Philips P2000</fullname> <path>/home/pi/RetroPie/roms/p2000t</path> <extension>.conf .CONF</extension> <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ p2000t %ROM%</command> <platform>p2000t</platform> <theme>p2000t</theme> </system>

Runcommand looked good:

Parameters: Executing: /opt/retropie/emulators/dosbox-sdl2/bin/dosbox -conf "/home/pi/RetroPie/roms/p2000t/Monkey.conf" fluidsynth: warning: Requested a period size of 64, got 480 instead fluidsynth: warning: Failed to set thread to high priority fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible. DOSBox version SVN Copyright 2002-2019 DOSBox Team, published under GNU GPL. --- CONFIG: Loading primary settings from config file /home/pi/RetroPie/roms/p2000t/Monkey.conf SDL: Current window pixel format: SDL_PIXELFORMAT_ARGB8888 MIDI:fluidsynth: loaded soundfont: /usr/share/sounds/sf2/FluidR3_GM.sf2 MIDI: Opened device:fluidsynth One joystick reported, initializing with 4axis Using joystick Xbox 360 Wireless Receiver with 6 axes, 15 buttons and 1 hat(s) Using driver "opengl" for renderer

I am happy to investigate more if it helps the community. If we collectively believe this is a problem with a 20-year old emulator, I am also content to call this one good enough and run without a joystick. :)

@Oxopi said in so all generic USB n64 controllers work nowadays?:

https://thepihut.com/products/raspberry-pi-compatible-wireless-gamepad-controller?variant=38135423121

That's not a N64 controller, that's not what @peggytam009 asked.

@dankcushions Thanks for the response! Unfortunate but understandable.

Hi toghether,

@mitu , moving the File out of way had no effect.

@BuZz here is the Config.txt

# For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # 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 #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # 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 [all] #dtoverlay=vc4-fkms-v3d overscan_scale=1

Greets Trekinfo

It's a known problem - see https://retropie.org.uk/forum/topic/26504/.

The safest option would be be to install the latest Raspberry Pi OS Lite - which should have the USB boot supporting firmware on the/boot partition - on the USB disk, then perform a Manual install of RetroPie. The EEPROM bootloader is already updated, so USB boot should work.

You really got me confused with that config... so just a few thoughts:

Here is Ultimarcs Default Setting [under Tab: Installation] for the I-Pac#, and the ones in your config seem to be mixed/messed up with the (I-PAC) shifted defaults (player 1 defaults for the joystick/d-pad are cursor u/d/l/r)...
And my curiosity about your .cfg reminds me: At first I should have reminded myself (and you) that third party images are not supported on this forum. To debug/help you on this, if your builder wasn't a friend who had set it up with an official build and got paid for the hardware alone and added your roms on your behalve, I think that another sd card with a fresh retropie install (keeping formerly as a backup in case you need stuff from there) would be a good start. And by doing so, regardless what your son may do in the future, you will be prepared to set it up again!