Zombeaver

You could swap ports with an AHK script. I have several CCS64 functions assigned to various controller buttons/combinations. I can't remember if I have one for joystick swap, but it could certainly be done. I can paste the entire script I'm using later today. Port 2 is more common by the way. Inputs with a joystick in port 1 could sometimes cause issues with the command line, which is why 2 is basically the "default". There are certainly plenty of games that use 1 though. "Internally the control ports are not read by dedicated inputs, instead they are attached to various points of the keyboard matrix, which goes to CIA#1. This causes some trouble when the joystick is set to autofire (random chars will be entered) or when a joystick is stuck in one direction it can lock out certain keys. Most games and programs make use of the Control port 2 as it is easier to handle - for example control port 1 joystick left direction is hardwired to the CTRL key and can cause trouble when scrolling out of the screen in basic programs (scrolling slows down)." (source)

If you do decide to try out Atari800, I've got some setup instructions here: There's also a RA core port of Atari800 which is quite good too.

FYI you don't need the custom UUID launcher .exe anymore. That was to address a bug with FS-UAE which has since been patched. There's an annotation about it in the relevant section of the video. Both your FS-UAE and FS-UAE UUID emulator entries can be directed to the normal Launcher.exe. They still need to be separate because they still have different checkboxes that are used, but Eirulan's custom launcher is no longer necessary.

Launchbox doesn't really install anything for you; you're just directing it to a file. Some DOS games you can simply import into LB, indicate they're DOS games, and start them up and it'll work, but often you can't. I install all of my DOS games though DOSBox prior to importing them into LB, as this ensures everything is setup properly beforehand. Assuming you mean Conquest of the New World, it's a DOS game, not 3.1 (though the Deluxe Edition apparently had a W95 port). The Deluxe Edition is available for DOS as well. I'm using a disc image of it, as an example. If you have a physical disc, that's fine too. I like to keep mine in the folder where I install the game, in a subfolder named "Disc Image": First you need to start up DOSBox and mount your drives. First, mount the location where you want to install the game. I want to install the game to the folder where I keep all of my DOS games, which is X:\Emulation\DOS\ I've created a folder there beforehand named after the game title, so for me I'll type: mount c "X:\Emulation\DOS\Conquest of the New World" Now I need to mount the disc image. I use a virtual drive (Daemon Tools, it's my "H:" drive) so I'm going to mount that drive with my image and then mount it in DOSBox, but if you don't have a virtual drive you can mount the image directly. mount d "h:\" -t cdrom or imgmount d "[path\to\your\iso]" -t iso Now we need to navigate to our "D:" drive which we've mounted. D: Now we need to see what all files are in there. dir /p This will show us a pausing list of all the files on the disc. In this case, we want to use the install.exe. install Choose "full installation" Select C as the drive to install to. Back the directory to install into all the way back to C:\ (it's not actually installing it onto your real C: drive, it's installing it wherever you specified, which it sees as your C: drive) Hold down CTRL and press F12 until your cycles (listed at the top of the DOSBox window) are about 250000 to speed up the install process. You can either have it auto-detect the sound card settings or specify them yourself. In this case, I'm just going to use Sound Blaster. Test them out afterwards to make sure it's working. Go to exit and select to save changes. Now you can close out of DOSBox and import it into LB. Just drag the entire "Conquest of the New World" folder in, indicate that it's a DOS game, select "Use the files in their current location", scrape for metadata, make sure the "attempt to automatically mount ISO or CUE files as CD-Rom Drive D (recommended)" box is checked (it is by default), and then ensure that "Conquest.bat" is the "Startup file". And now you're good to go! DOS games will often require you to create custom configs for them in order for them to run ideally (specifying custom cycles, output type, machine type, etc.) but this one seems to work pretty well with auto cycles and other settings that I use as a default. If you want to create a custom config, edit the game in Launchbox, go to the DOSBox tab, and in the custom dosbox configuration file field, click the "Create..." button. If you want to install a patch on top of an existing game, the process is the same, you'd just need to have installed the game, and then instead of starting the game you'd start the patch .exe and complete the setup process. That said, if you have a Windows version patch that you're trying to install onto a DOS version of the game, it's not going to work. The patch would need to be DOS-based as well. Now, you can install an instance of Windows 3.1 or Windows 95 into DOSBox, but that's a whole other can of worms that I don't want to get into here. There are tutorials on how to do it though. 3.1 isn't too bad to do - 95 is a good deal more complicated.

What is it your trying to do specifically? For what game? Do you know how to use DOSBox?

I'd really like to see a %rompath% function added, similar to the current %romfile% function, except that it only injects the path to the rom, rather than including the rom file in it. I've had this ongoing PCSX2 config project that I've been working on for about a week now. I use per-game custom configs for all of my PS2 games because there isn't a one-size-fits-all setting solution for games in PCSX2. These configs can be specified via the command-line. The format for this is --cfg="[path\to\config]". I have the configs for each game placed in a folder named after the game which also contains the disc image(s). Since these have to be specified for each game, each game has to be edited in LB with custom command-line parameters. For example: --fullscreen --nogui --cfg="X:\Emulation\PS2\Metal Gear Solid 3 - Subsistence" If a %rompath% function were added, no custom parameters would be needed for each game. You could just have default parameters of --fullscreen --nogui --cfg="%rompath%" in the PCSX2 emulator entry itself. I plan on sharing the configs on the forums, but a lot of people probably aren't going to want to add in custom parameters for each game. This would make it much easier for people to use them.

Yes, that's correct. Currently, Mednafen Saturn in RA does not do disc swapping. .m3us work in standalone. Disc swapping is broken in Enemy Zero, specifically, even in standalone.

I've got a little FYI on the media naming conventions here if anyone's curious:

Okay, so here they are (attached below). These can be imported like normal roms, just be sure to check the "Use folder names instead of ROM file names for game titles" on this screen of the importer to ensure that it uses the correct title. I split them up into categories like they're listed in the drop-down list in ParaJVE (I put "Test Cartridge" in an additional folder named "Other") since I'm sure most people won't want everything here like the tech demos. Make sure your emulator entry for ParaJVE looks like this and you'll be good to go: Game IDs.zip

No problem! I'll upload the folder/file set to make it easier for people once I'm done.

Yes. What I suggested works. I just tested it out. The file has to be named correctly (and it's case-specific). I extracted the names for the games from the xml (attached below), so now I just need to make some files to match. All it's doing is indicating to the emulator which game to start, they're not actually roms at all. The way to make this easiest for importing will be to use folders with each game title, and placing the "rom" (just a blank file) with the appropriate game-id name, and indicating to "use folder names" on import. Game Names.txt

So I just updated from beta 5 to beta 6 and tested. It did close as expected but I got an error afterwards: Afterwards, I could still hear BB music playing but I couldn't get back into BB and had to end task on it. I tried again a few more times and didn't run into this again. Looks like some kind of (intermittent) VLC issue I guess. In any case, closing itself is still working for me on beta 6.

I just tested on beta 5 and the script I listed is still working for me. I'll update to beta 6 and see if that's still the case.

Is this only an issue in BB then? It quits normally in LB? Do you have the "attempt to hide console window on startup" box checked?

Is it only for specific emulators or all? Try checking the "attempt to hide console window on startup" checkbox in one of your emulator entries and see if you're still having the issue afterwards.

That's nothing new for me - controller automation never worked to close Demul for me unless I added in the task kill on ESC script to the AHK section. I also have NoMousy in mine (MouseMove would work too), but adding this will make controller automation work to close it. ; This section closes Demul when pressing Escape $Esc:: { Process, Close, {{{StartupEXE}}} }

It does but you can't quite do the same thing with it as what ParaJVE, which does both overlays (bezels) and background art behind the game. You can kindof fake it by adding the background to the overlay image itself with a reduced opacity (something like 40%) but again it's kindof faking it (see this an example). You'd also have to make them (and specify them) for each game one at a time. ParaJVE does all of this automatically.

If you used -game= as a default command line parameter in the emulator entry in LB, and checked the box for "use filename only without extension or folder path" (and probably the "no spaces before ROM" box too) you wouldn't need to do that so long as the rom is named appropriately - Bedlam.zip or whatever.

Hey I just wanted to come back and mention that I really love the changes to the importer after several days of heavy usage - having it automatically pick the currently viewed platform and remembering the checkboxes are a godsend! One thought on that though - would it be possible to change the move to launchbox/keep in current location etc. section to checkboxes as well so that they could also be remembered? I literally never move my stuff which is in an external directory, so this would streamline it even more. Something else I'd really like to see is a "smart import" where you just drag your rom(s) into the appropriate platform and it then runs it through the import process using all of your previously selected checkboxes, no further input required (other than maybe the first screen to indicate whether they're roms, DOS, etc.). It would probably still need the final page of the importer as well just to confirm that the titles are correct. Anyway, loving the updates! Thanks!

I used to be suuuuuuuuper into Mugen, scouring innumerable obscure all-Japanese websites (before automatic page translation was a thing in browsers), various pages that looked like they were from Geocities, and a bunch of message boards for that one obscure character you saw on someone's video but couldn't find anywhere. The hunt for characters/stages and adding/arranging them was as much fun as playing for me. Unfortunately, the Mugen community is one of the most caustic, petulant, and insane groups I've run into on the internet - people that get extremely pissy about anyone hosting "their" character anywhere other than on their personal, highly unorganized site that looks like ass. Sorry guy, but ripping some sprites and adding some basic AI doesn't suddenly make you the creator and owner of Wolverine or Ryu or whatever. "Don't host my characters anywhere otherwise I won't release any to the public in the future." It was amazing to me how much of the scene was full of people that took this utterly childish attitude. I've still got my Mugen setup, the final tally being about 1100 characters and over 500 stages. I thought I'd lost it a while back but found it on an old hard drive that I hooked up to an enclosure. I backed that thing up to my Google Drive immediately afterwards haha. It's about 12GB

@Manuel Leiria So I did a little testing with disk sets. What seemed to work best was to actually save it as a save state and then load the state as the "rom" in order to load the set on launch. I haven't been able to figure out how to load the standard "Disk Sets" via command-line in either standalone or RA; I could only get them to work by manually loading it via the UI (F1 -> Disk Management -> Load Disk Set). However, you can accomplish the same thing with save states without having to do that. Load up the game, go into the Atari 800 menu via F1, go to Disk Management, add your disks in to D1, D2, etc. Go back to the main menu and go to Save State: Save it somewhere and name it after the game title. Then set that file as your "rom" in LB: When you start the game, it'll load all the disks that you added into Disk Management. This works in both standalone and RA, but it's easier do in RA because in standalone you need to specify the -state command line parameter for it to load it from command line. There doesn't appear to be a hotkey for the "Rotate Disks" function, so you'll still have to go into Disk Management and do that when needed (Alt+D -> R -> Enter -> Esc), but at least this way it loads all the disks from the beginning without having to manually "Load Disk Set".

Right, I was aware that was there as I've used standalone for quite some time, but I meant that in the RA UI there doesn't appear to be a section for disk management (Quick Menu -> Disk Control). A number of other cores have this like Beetle PSX, but there doesn't appear to be one for the Atari800 core. As far as what you're wanting to do, I'd probably just do it via Additional Apps. Add the individual disks as additional apps and use the list config as the default. As far as doing both at the same time... I'm not sure. As I said, I don't actually have any multi-disk Atari 800 games in my library at the moment. No problem! There's actually quite a bit of good stuff out there. Check out the "Lucasfilm Games" (prior to Lucasarts) stuff if you get a chance. I'm a C64 nut and a lot of those games were some of my favorites as a kid - especially Ballblazer and Rescue on Fractalus, and I was somewhat surprised to find they were actually better on the 800. That's the platform they were originally made for before being ported to the C64. Cavelord, Dimension X, Orc Attack, Rainbow Walker, Stealth, and Yoomp! are some other random recommendations. A lot of interesting and weird indie games out of Poland too.

Yes, I've converted over most of my stuff to the RA core rather than standalone at this point. I'm not sure what you mean by "disk sets". You mean multi-disk games? I don't actually have any Atari 800 games that are more than one disk currently. There doesn't appear to be a disk management section in the quick menu for the core.

3.1 is actually really easy to setup in DOSBox. And the cool part is once you do, you can save that install as a "base", and copy it into a new folder and install the specific game into it, set it up to autoboot the game when the OS launches, and then just import it into LB and it's good to go like any other game. The whole setup process for new games is only a couple of minutes once you get used to doing them. 95 is a good deal more complicated but definitely doable. I've basically got a 95 environment setup and haven't done much else with it yet. I've been focusing on 3.1 games for the time being. There are actually quite a few interesting and cool games for 3.1 - especially if you like first-person adventure/puzzle games.