sundogak

The adding header issue only applies to cartridge binaries. Cassettes and floppy disk images don’t need the header so that tool doesn’t apply to that media. The Atari 8 bit series had a cartridge slot and ability to connect a cassette player and a floppy drive. Many games were made in multiple formats. However some were only in one format. On bios only need two typically which would be a Basic bios and a Pal/NTSC. I have the others from stand-alone emulator.

On the Atari OS issue that is due to the emulator not knowing location of the Atari BIOS file. Check your .atari800.cfg file for the correct paths in the RA directory. Example of my paths in my CFG. As to the crashes, hard to say since can be a variety of things. Like I mentioned earlier, the RA version is ancient and suspect some may be due to older version such as the crashes on title page. Also, I have seen crashes like the "address" error, if attempting to launch a binary file that is a cartridge-based game that you don't select the correct header type, or a mis-headered *.car file (cartridge based game). For the binary cartridge files missing a header this tool here helps with converting them to *.car files so don't have to worry about selecting header and/or having wrong one and crashing. Note that only applies to cartridge games and not floppy disk versions (ATX for example). RA for any computer system in my view is more pain that worth so I stick with Altirra or the Atari800 standalone emulator for anything computer disk based. Edit: ETA Prime has an older video for the RetroPie that might be helpful. The emulator itself is the same. Starting at 7:24 is discussion on the missing OS and way to do it without direct edit to CFG file. Also gives some pointers on the emulator that may be useful as well.

@MarkAmiga500 Not sure where it would pop up with the note "for use for a real Atari". But overall, there is no "Retroarch rom set". Most of those cores are based on standalone emulators like the Atari 800 emulator. The Retroarch core for this uses an older version of the Atari 800 emulator and info on the setup for Retroarch specifically is here. As noted at the RA page you have to have the appropriate BIOS file (ROM) for the Atari 5200 and Atari 800 to run games from them. Check that your BIOS files have the same exact MD5 checksums noted in the RA page. It sounds like you said this isn't the issue and if that is the case then the issue is either a setup file issue in RA (Atari 800 is not easiest to setup), or the game files are not readable to the emulator. Game files have to be in format that Atari 800 emulator can read. Typically, it will be an xex, atx, atr, bin, or a52 (5200 cart) file. You may also see a "*.car" extension (bin files natively) on some which are Atari 800 series cartridge games with the appropriate header to tell the emulator automatically what type of cartridge setup to use. If it is a cartridge game and no header, then Atari 800 emulator will pop up asking for which "type" at boot up. If atr file then a floppy disk image and no header issues to worry about. Typically, once get into floppy and cassettes then Altirra standalone is easier to manage. If your bios file and game images are seemingly okay then not sure without a screen snap and example of what you are trying to run.

I assume you are using Hatari RA core. If so, double check file you are trying to open is not IPF format (if zipped, look inside zip to see file type). Currently, the RA core doesn't work with IPF unless compile core yourself due to some rights issues with IPF. If not IPF (say STX), then likely issue is RA cannot find your hatari.cfg file. You can also run via the standalone Hatari emulator here which runs IPF with no issue. The RA core uses a relatively ancient version of Hatari.

Enabling a controller does not disable the keyboard on FP, so something else going on there. You should be able to use keyboard, mouse (if toggled on) and controller at same time. You might have some conflict of keys either in LB and/or in FP. Double check your Preferences and Game Keys/Controls settings (example below for XBOX One controller, but had 360 prior). Only thing have had to do is set FP to Windows 8 compatibility mode. Never had to change dpi compatibility mode. Also, using BAM fixes some of the memory issues in FP where get texture issues. You can download here but make sure to follow instructions and backup your key files for FP. FP hasn't been updated in 15 years, so BAM patches some things to help with newer Windows OS as well as add new features newer tables utilize (like TerryRed's tables).

Forgot to add that somewhere along line VPX changed their command lines. For 10.7.2 this is the current allowable commands (note no longer "exit"):

Try this for VPX: -primary -minimized -play Also, double check your resolution setting with the TV plugged in and launching VPX. Should work either way in window or exclusive if you have resolution set correctly. I normally keep the exit and start screens off for pinball in LB because it adds another layer of complexity to troubleshooting. But if I turn on, set to force exclusive and make sure my resolution matches my screen(s) then works on a two screen setup. I suspect some of this may also be due to laptop screen resolution vs your TV in that you said when put in fullscreen window mode it is not upscaling that implies that VPX res setting isn't correct. VPX should show all resolutions for your monitor that is plugged in and set to primary. You should double check what options for resolution are showing in VPX. My guess is that picking up the laptop screen resolutions. If there are any monitor scaling/changes while starting (i.e., resolution set is different than monitor) then with the LB screens for startup/exit it will be hit or miss if they don't pop up above the main window. Particularly with VPX when using separate DMDs or B2S backglass you will run into layering issues with LB and the exit/start screens as well (Future Pinball is another).

Cannot be done currently. It has been requested in various threads, just not enough votes to get in at this stage.

You cannot hide a platform or category. If you hide all games within that platform it won't show up in Big Box.

@vaderag Videos, and scroll down a bit further for link to media pack (logos, screen shots etc)

You would log in to your cabinet via Steam and install since they are tied to your Steam login account. You have to have Steam up for FX3 to work if you have the Steam version. You cannot "export" them without hackery.

There was some info on this issue in the RA github site here. I messed a bit with it using the command line for RA: G:\Emulators\RetroArch\retroarch.exe -L minivmac In theory this should work (but didn't on my setup..just loaded disk 1): G:\Emulators\RetroArch\retroarch.exe -L minivmac "G:\Emulators\Apple Macintosh\Mini vMac II\System 7.0.1.dsk" "G:\Emulators\Apple Macintosh\roms\Wizards Fire.dsk" There was a person on the github site indicating the issue was properly escaping the quotes. But they were using RA on a Mac so what they indicated wasn't working when tried on Windows (plus seems would gag on LB on one disk if that were the case). So unclear if just improperly formatted command or just the core isn't passing it at all or correctly.

You are in essence using the command line interface for RA/LB. For command line and MiniVmac in Windows you have to pass each disk path to MiniVMac at launch in quotes separated by a space. So outside of LB, a command to launch two disks looks like this (your paths will vary). If you are not in the minvmac exe folder, you also have to put full path to EXE as well from CMD line: "Mini vMac II.exe" "G:\Emulators\Apple Macintosh\Mini vMac II\System 7.0.1.dsk" "G:\Emulators\Apple Macintosh\roms\Wizards Fire.dsk" In LB it is same basic logic only LB already has path to emulator and has full path to one disk if imported already. I don't use RA for this emulator so my example below using non-RA Mini vMac executable directly. But will be similar logic for RA as well. LB is pointing to the Wizards Fire DSK in the launching line. Then in custom command line under emulation you can add in the other disk explicitly using full path and quotes. You could also add it to the emulator command directly but then that means it will always use whatever disk you reference with that emulator. If third disk you would add with space and path similarly. Ultimately, I find it is just as easy to use the miniVmac drag and drop interface in most cases or using a HD image versus floppy. Unfortunately, LB doesn't have a variable for Additional Apps (like %ROMFILE%), so you are stuck with always naming additional disks explicitly. This is the same for other systems like Apple II.

If you use the MAME Arcade Full Set Import wizard it will generate the playlist if you check it:

There is no fix and you cannot bypass the error. The digital video add on has not been emulated within MAME so any game needing that cart (DVC) will not work.

There are many Supermodel threads including a recent one on control setup (search Supermodel in top right box of forum). You will also see in search results a plugin to help with importing ROMs for Supermodel. But for setup here is commands in this thread:

See this thread on setup. If using ignore aspect and full screen commands, then you don't need the resolution since it will be overridden.

Depends on which core you are using, and you didn't specify. NeoGeo CD core: No command line parameters FBNEO core: --subsystem neocd

Answered above saying that that resolution won't work for Daphne. You will get an error. Also noted above: The fullscreen and ignore aspect commands will make game full screen and stretch no matter the original resolution of the media and is discussed above in relation to the batch file command: -fullscreen -ignore_aspect_ratio

No, it is within your batch files you call to launch Daphne from LB. Highly unlikely you are putting the entire command line needed in LB to run. See G22's example above.

If you are putting stuff in the RA directory for MAME then you to have all bios and software (i.e., cartridges) there as well unless you tell RA to look for ROMs outside normal RA path. With AES you are not only using neogeo bios files but also software carts. So it isn't a "normal" arcade" setup with point to a ROM and go. It needs two pieces plus the HASH folder which is the "map" for MAME to know which software carts/files go with particular bios. However, there is a setting that allows you to avoid duping your ROMset into the RA folder. See below. With an option setting in RA, you don't have to put your ROMs in the RA directory. However, you do have to do certain folders, particularly the HASH, samples, and INI folders. ROMs can be pointed to in a normal setup outside RA. These are the only folders in my MAME RA folder (Note looks like MAME folder but substantially truncated and no ROMs): The MAME ini folder will have a dumbed down version of a normal MAME.ini file. The key here is you have the paths to your "normal" (non-RA) MAME folder with all your ROMs and full software set. This special RA version of MAME.ini basically is only used to point to ROM paths outside of RA. So don't just copy over your normal MAME.ini into RA, you have to adjust paths. See example below but you will have to adapt to your paths. Make sure your Rom path and SWpath point to a full set MAME rom set and software rom set. Anything in the paths below that says it is in the "retroarch" folder path has to be in RA folder (it won't work outside RA because of glitch in the MAME core). Then in the RA config folder under MAME, have a mame.cfg file with: game_specific_options = "true" Then also in the config folder a file called MAME.opt (this contains the options settings in RA): The key ones are: mame_mame_paths_enable = "enabled" <<< this is the one that allows option for RA to use paths outside normal structure. But it was coded incompletely and documented poorly. It ONLY works with ROM and Software paths outside RA. They have never bothered to fix it to work with other paths. These others are also key, particularly the CLI enabled one. mame_boot_from_cli = "enabled" mame_boot_to_bios = "disabled" mame_boot_to_osd = "enabled" You can set these in the RA interface but find it easier to do in the config files. This is why setting up MAME in RA is pain, because you are overlaying a complex MAME setup, with a jury rigged RA version that has parts that must be "RA way" and others that have to be "MAME way".

@ElhoraMAME and RA overall are a headache, particularly when using software MAME set. But if using the MAME RA core here is how setup for AES: "aes -cart \"%romfile%\"" This is an example for MAME RA emulator settings. It is different than a normal MAME RA Arcade set up so I setup a separate instance of RA and called it "Retroarch_MESS" (you can call whatever). It still points to same exact RA setup as your main, it just tells LB slightly different launch commands: Using Art of Fighting as example, LB just points to the normal zip file (AES cartridge) for that game within a regular MAME software set (i.e., the cartridge "software" is not in the arcade set for MAME).

The fullscreen and ignore aspect commands will make game full screen and stretch no matter the original resolution of the media and is discussed above in relation to the batch file command: -fullscreen -ignore_aspect_ratio Keep in mind this just blows up the video and stretches it. There is no "upscaling" within Daphne and most definitely not at 4K. There are some enhanced Dragon's Lair and Space Ace video files that are actually upscaled using AI at 1920x1080. But in most cases these are 480p generation games, so none are truly wide screen. If not using full screen option, then the screenres command tells Daphne what resolution to use via command line or batch file. You can see examples above. In theory, you could set the resolution command like below, but you will get an error within Daphne since it will not recognize that high of resolution: -x 3840 -y 2160 -fullscreen Daphne is an old emulator so 4K isn't going to be option. So best you are going to do is use wide screen resolution like: -x 1920 -y 1080 -fullscreen But again, this will stretch almost all the Laser Disc based games. The easiest is just to use the fullscreen command (without any specific screenres setting) and let the emulator size realizing it will have black bars on the sides.