@seedyeh said in Older Ipac 2 button mapping question...:

The ipac keystrokes are the ipac default ones. I am unable to update the firmware on this Ipac (confirmed by Andy over at Ultimarc).

Providing the details listed here avoid later querstions, which most of the time will be needed without it.

I-Pac pre-2004 Era? I am just in possesion of a 2015+ one and don't know what defaults are used on the older ones. Though it ain't part of the problem: you can reconfigure/reprogram the keystrokes send by the I-Pac by using the legacy application for it, or?
What Mame Cores have you tried? As the I-Pac is treated as a KBD here, there may be conflicts between the keyboard input recognized by mame and the additional retropad input send to it (for some cores that may be disabled/configured in the rgui, so that they either see the keyboard or the retropad input, for others (or in addition to that) it may be needed to edit the mame inifile to react only on either one of those signals).

@duglor

I looked at the source of lr-bluemsx and the problem is already fixed :
https://github.com/libretro/blueMSX-libretro/commit/a0a63d4f38069872195b8afec442848fdf04f12f

Not sure, right now, if the binary still has this problem but the problem should automatically be fixed when a new binary is shared for the install.

Only the docs would need an update.

I have added a port for ARMHF: Feel free to try it :-)

ja2-stracciatella-0.18.0.

You want to use the armhf.AppImage.

No, there isn't one included in RetroPie, only the 'embedded' variant is included.
You can install one of the releases for Moonlight-Qt since it provides packages for Linux which should work on Ubuntu/Debian.

You may have more success asking in the RetroArch forums, this is a RetroPie dedicated forum, there's probably very few users using an Nvidia Shield here.

@mitu I figured that was the case. Thanks for the response!

You can't connect the joystick directly to the PI's GPIOs, you need an ADC chip in-between.
Take a look at https://grantwinney.com/connecting-an-analog-joystick-to-the-raspberry-pi-and-using-it-with-an-rgb-led-to-simulate-a-color-wheel/, which uses an MCP 3008 to connect a joystick to the PI.

You need to press the button you've mapped to A during the input configuration dialog. If you wish to exit, just press Escape if you have a keyboard available.

@duglor It is Fixed. I was in the SSH and typed sudo raspi-config and chose to
2. chose System options
Step 3: choose "3 Boot Options... Configure options for start-up"
Step 4: choose "R1 Desktop / CLI... Change whether to boot into a desk"
Step 5: highlight "B2 Console Autologin... Text console, automaticfally logged in as a 'pi' user
Step 6: tap 'right' on your keyboard to highlight "OK"
Step 7: highlight "Finish"
Step 8: Would you like to reboot now? "YES". Since then it boots up from "exit" like before.

@mitu I got it to work by remoting in with SSH and running it from there rather than using f4 on the pi directly.

@pjft This seems potentially very exciting news. I had a fiddle around with the Next a few months ago but got terrible framerates except by running it in a Raspbian environment outside of Retropie. If it could be made to run as an ES system that would be awesome.

No idea, since I'm not familiar with the installer/script you're using.

@mitu I opened a couple and they seem ok. I will check the space left on the card. I don’t think that’s it though. It’s a 64 gb card and I formatted it before using and the only thing on it is RetroPie and the ROMs. Maybe I’ll start with a fresh new SD and new install and see if that solves it. Thank you.

I help myself ....
If you install pixeldesktop and pikiss and vulkan driver on retropie (now I had upgraded to retropie 4.8.2 )you can simply integrate lr-ppsspp vulkan driver support installed by pikiss simply editing es_systems.cfg and add a new system called (for example) ppsspp vulkan and edit the command line to execute with xinit lr-ppsspp (from the new directory created by pikiss)...
So retroarch in emulationstation remain the same (without vulkan support) but when you execute from emulationstation the new emulator lr-ppsspp vulkan driver supported is correctly launched and executed ....
You don't need to install retroarch from pikiss because retropie won't see the new retroarch...
Yes this is a (great) trick ...but works on
Duckstation and lr-ppssspp installer by pikiss (with vulkan drivers) and launched from emulationstation with desktop initialization thank to xinit command before the launch script of every emulators...
You can watch my solution

@mitu Heya! As an update, I got it working! Worked with a friend of mine who is a Linux expert and he walked me through it step by step, which did include the steps that you had pointed out. Thanks so much for your help!

@Retro-Arcade-Fan The shops listed on the pi website are approved resellers and are reliable. I would then compare them to see which ones charge less shipping.

Hello Thank you for the information.
It was useful for me as well.

Please allow me to add:

How to find out the Vendor ID and Product ID
It is briefly displayed along the info message on the bottom left hand side of the screen:
Tetris Opening Screen showing Error message and the values for the controller presenting the issue

With lsusb we can see in Hexa the values
Bus 001 Device 014: ID 045e:0b12 Microsoft Corp. Xbox Wireless Controller (model 1914)
Changing the controller does not change the ID.
However, changing the controller for a generic controller changes the ID:
Bus 001 Device 016: ID 045e:028e Microsoft Corp. Xbox360 Controller
Hence causing this to happen AGAIN, which is annoying.
We have to manually edit the config file again.

One thing that bothered me is that in all know previous versions of Retropie this was not an issue and now it's presenting one new, more issue than the previous version.
I've used Retropie for years now and I have never had this issue.
The only "new things" I have are

Operating System [Ubuntu 22.04 LTS freshly installed]; THIS Specific controller (Tested and proven to be working in all other games, also the old controller presented the same issue); USB Cable (Tested and proven to be working on other games, and able to "quickly charge" a Phone and perform fast data transfers)

Please let me ask:

Is there any way I can make it Automatic when I change controller to change the configuration.
-- Bear In mind I did the controller configuration at the start of Retropie every time I change the controller, and I tested quite a handful of times, I went as far as deleting , removing configuration files, and recompiling Retropie from the source 3 or 4 times. Would there be any test you'd like me to perform?
-- I may test it again on another Ubuntu version (or Ubuntu based distribution);
-- I don't discard the possibility to install it on a different Linux Distribution;

Thank you very Much.