@rasp_renegade hello. As with ColecoVision and Intellivision...all emulators....Google is your friend for any BIOS/ROM files. And also keep in mind, there are variations to some that you have to keep trying versions until you get the right one.
going off on tangents here, but: RetroPie -> Run Command Configuration -> set Joy2Key version to udev (instead of sdl) seems to have fixed the issue with the config menus not responding to controllers in the latest RetroPie update, although the pop up option to edit emulator configs no longer seems to show up during game loading
PPPS: Re-enablng the launch menu from the same area will fix that last part.
To clarify on backends.cfg: If it shows jzintv="dispmanx" the emulator call gets these environment variables passed in: SDL1_VIDEODRIVER=dispmanx SDL_DISPMANX_WIDTH=1600 SDL_DISPMANX_HEIGHT=1200 /opt/retropie/emulators/jzintv/bin/jzintv ... (but has no effect on the emulator), if it is absent or configured to SDL2 KMS in _Configurations/Tools _ (results in jzintv="default" in backends.cfg) no env variables are prefixed to the emulator call. So long story short: No need to explicitly set something in backends.cfg.
On readline: You are right, if it is disabled in the build, a simplified implementation will be used. So I will leave libreadline-dev in the dependencies.
Will file the two PRs shortly, will use $__archive_url.
Okay, solved and this is one I recommend making more clear in the documentation. My issue was that I ALWAYS keep a wireless keyboard connected to my Retropie. It's just a tiny dongle taking one port so why not? It's so much easier for certain tasks.
However, I kept wondering why the test rom for Intellivision was reporting that I was on controller 2 and every other comment pointed to controller one. Then I noticed posts where people said that Daphne and Intellivion (jzintv anyway) assign the first controller they see, which in this case was the keyboard -- and that explained why the keyboard worked. Ugh.
I sent back and took a CLOSE look at emulators.cfg (where you add the link to the hack file) as I found it odd that mine was already there.
What I realized is that it was there, but for the tzintvecs (which I assume has something to do with running things in the expansion port). So, I added it to the main program as you can see below, but still nothing. Changing the JS1's to JS0's also made no difference after this fix.
Yes. So this needs to go, I think, after the -config option for those custom jzintv commands. It wasn't working for me until I did that. If all else fails, this version of the xboxdrv line worked for me:
But you will need to update RetroPie from source for the PS3 buttons to show up in event_diag.
Now if I could figure out why the config menus no longer work with controllers (I need my keyboard to use them)...
For updaters: RetroPie -> Run Command Configuration -> set Joy2Key version to udev (instead of sdl) and then re-enabling the launch menu from the same set of options will fix this
@Unknown I made the same mistake when I first started looking into building my first Retropie then remembered that the NeoGeo home console (AES) was essentially the same hardware as the arcade unit (MVS) but could only have one cartridge as opposed to the up to six cartridges of the cabinet.
If there is no /opt/retropie/emulators/jzintv folder after installation, then it means the installation didn't complete correctly. Note that the install doesn't add a hackfile, so if your configuration included one, you'll have to add it manually.
I think quicksilver may have found your issue as your BIOS files should be in /home/pi/RetroPie/BIOS/ and your setup appears to want them in your roms folder. You could try copying them there if they are not already and see if it works. My Intellivision retroarch.cfg just points to the global one in /opt/retropie/configs/all/retroarch.cfg I dont have any custom values in it other than the input remapping (maybe you have something else?) in the global file you should have system_directory = "~/RetroPie/BIOS"