@JuanZt

Just stopped by to thank you. I've used your steps and was able to get my PS4 controller (not original) to work.

@DavidDraper said in Issue with multiple "USB Controller " controllers...:

/opt/retropie/configs/all/retroarch/autoconfig
I thought whatever is in there is automatically copied into
/opt/retropie/configs/all/retroarch-joypads;

It's the same folder, the latter is a symlink to the former.

pi@retropie $ file /opt/retropie/configs/all/retroarch-joypads /opt/retropie/configs/all/retroarch-joypads: symbolic link to /opt/retropie/configs/all/retroarch/autoconfig

@mitu /opt/retropie/configs/mame-libretro/retroarch.cfg is already in that state (and it's identical to retroarch.cfg.rp-dist)

Well, you could download the new SDL2 based version and replace the existing one. Since it's better to unpack the archive on the Linux system, you can run from the terminal

wget http://spatula-city.org/~im14u2c/intv/dl/jzintv-20200712-linux-rpi-sdl2.zip sudo mc /opt/retropie/emulators/jzintv

This will download the new version and open up MC with the location of the existing jzintv version on the left pane. On the right pane, browse for the .zip file you downloaded and then just press Enter over the selected file, you'll see the contents of the archive and you'd be able to copy the new jzintv binary over to the left.

@Yobiwan Deleting the file from roms/scummvm works. Did you enable the 'Parse gamelists only' option in EmulationStation by any chance ?

@mitu
Ah, got it. I thought my method might be out of date but I'm new to digging this deep, and it's a frustrating but fun learning process. Thank you a ton for the help, I'll check that out once I get the chance today.

probably a question to better ask at the KODI forums. https://forum.kodi.tv/

@Chapster5 Thanks for sharing your solution. 👍

This is the results of vcgencmd get_config int.
enable_dpi_lcd and display_default_lcd are set to 1.

arm_freq=1500 audio_pwm_mode=514 config_hdmi_boost=5 core_freq=500 core_freq_min=200 disable_audio_dither=1 disable_commandline_tags=2 disable_l2cache=1 display_default_lcd=1 display_hdmi_rotate=-1 display_lcd_rotate=-1 dpi_group=2 dpi_mode=87 enable_dpi_lcd=1 enable_gic=1 force_eeprom_read=1 force_pwm_open=1 framebuffer_ignore_alpha=1 framebuffer_swap=1 gpu_freq=500 gpu_freq_min=250 init_uart_clock=0x2dc6c00 mask_gpu_interrupt0=1024 mask_gpu_interrupt1=0x10000 max_framebuffers=2 over_voltage_avs=-23750 overscan_scale=1 pause_burst_frames=1 program_serial_random=1 total_mem=4096 hdmi_force_cec_address:0=65535 hdmi_force_cec_address:1=65535 hdmi_ignore_edid_audio:0=1 hdmi_pixel_freq_limit:0=0x11e1a300 hdmi_pixel_freq_limit:1=0x11e1a300

@mitu Thanks

Just for someone else experiencing the same problem, make sure you have free space left on your sd card. Check if the expand fs ran successfully at some point.

@Jimi007 said in Amiberry 3.2 beta black screen on starting games:

Do you know if there is a difference with the pre-compiled and source version?

Yes, the binary is built from a different (earlier) version of Amiberry. The binaries are not automatically updated for each new upstream change.

I've seen this on one of the megadrive/genesis emulators. The reports indicate it is related to the widgets that appear in the lower left corner during startup.

I've been able to get going by pressing hotkey + B to simply reset the game. Always seems to work the after that.

@George-Spiggott Thanks for this, I have now run this version and working great.

@mitu Ok, thanks for all the fast help!

Thanks again, @mitu!

@mitu said in update Retropie 4.6 or Raspbian (old) image:

I'm not sure why you'd want to downgrade to 4.6 is you already have a 4.7 system (even if on Stretch) ? If the upgrade that broke your install is from the Raspbian updates, then I don't see why the RetroPie version would make a difference.

The reasons are complex, as the upgrade to 4.7 both introduced and removed some bug symptoms I was trying to debug on something else I am working on, and others report on RPi3 B+ stretch and RetroPie 4.6. And now I’m back to v4.4 from backup on the same SD card. I’d like to get back to the v4.6 state everything was in... ;-)

I don’t know for certain if the OS upgrade that broke other things came from “apt-get -y dist-upgrade” in the RetroPie upgrade script, or if I ran an upgrade my self.

Anyways, I guess I have to accept my losses, and let this be yet another life lesson on taking an image backup before making bigger changes. Think I got a little carried away in debugging mode... ;-)

This is not guaranteed to work, since some of the emulators have been updated and - as a consequence - some of the scripts in RetroPie have been updated to support it.

Ok now I think I understand better. The complete v4.6 “state” was lost with the removal of the binaries, and is not maintained with information about commit history for external and other source files to compile from the 4.6 install script?

I guess I will use this opportunity to upgrade to buster and RetroPie 4.7 on this RPi3 B+.
This day would’ve come eventually, anyways, and it worked like a charm on my RPi4.

Thanks for a great product and the support!

@Impy

Thanks for all the help guys. I finally got it to work yesterday. Seems I forgot to go back and configure the controller once the Bluetooth was set up. I just use the keyboard to bring up controller input and everything was good after that.

Thanks a bunch! 👍

delete this post thread ... just gonna use the working SD Card instead.