Zombeaver

Start Atari800.exe Press F1 Go to Display Settings Go to Video Mode Settings This is what I'm using: I also use a custom palette (in Display Settings) but we can get back to that later. Press Esc twice to get back to the main options screen Go to Emulator Configuration Select "Save Configuration File" You can also enable "Save Configuration File On Exit" but I recommend leaving this off in case you mess something up while changing settings - it won't be saved until you manually save it. It also keeps you from having cartridges or disk images remaining "inserted" after exiting the emulator. Pres Esc to get back to the main options screen Select "Run Atari Program" Navigate to your rom and press enter If you try to load a cartridge format rom it will ask you to select the cartridge type. This varies by game but "Standard 16 KB cartridge" is what it will be most of the time. F2 = Option F3 = Select F4 = Start F12 = Warp (fast forward) F9 = Exit (I have these bound to buttons on my controller via AHK but again we can get back to that later) If you're using an Xinput controller (I use a wireless 360 controller) it should be detected automatically and the left joystick should control the joystick in game and A (on a 360 controller) = fire button. Atari800 works fine via LB too but we need to verify that you can get stuff working outside of that first.

Your files have to match the checksum for one of the versions of the game that it looks for. If it doesn't, it won't be imported on the scan. In some cases you'll need to create your own configs for these as I go over in the video. Something else to consider is that if you're using WHDLoad games, you need to make sure you're only trying to import games with compression that's one level deep. .iha is a compressed archive format just like zip; it just so happens to be used for some WHDLoad Amiga games. Because FS-UAE can only read compression one level deep, you can have 1) a .zip that contains a game folder plus a game.info file (this is the format that KillerGorilla uses) or 2) you can have an .iha file. You cannot have an .iha in a .zip (an archive within an archive). If you have zips that contain .iha files, just extract the .iha files and they'll work just fine. If you have zips that contain a game folder and a game.info file those will work just fine as is.

I use Atari800 personally. It's not the most intuitive emulator in the world but it's not too bad either. Try that one out and if you have any trouble let me know.

I'll have to check this out tonight. Most stuff works decently well with the 4DO RA core but there's some stuff that doesn't work with it that does work with standalone 4DO, like Crash n' Burn. Probably my biggest issue with 4DO is that it doesn't support Xinput, which means it doesn't work via Steam Link unless you're using VirtualHere. Does anybody happen to know if Phoenix supports Xinput?

Sometimes if you have one application in exclusive fullscreen and then start another on top that's running at a different resolution the two don't get along. My guess is the resolution is being changed by the emulators that you're using and Kodi isn't readjusting after you exit it.

Yeah there doesn't appear to be an equivalent for playlists, and opening up one of the xmls just has the same fields that are in Launchbox. Honestly I guess it kindof makes sense that playlists wouldn't have those fields. Like, for instance, I have playlists for "Shmups" and "Favorite RPGs". How would you put a year for those? It's not an actual platform/console - it's a specific category of games. You know what I mean? There certainly could be instances where someone might have a playlist where that type of data would be relevant but in a lot of cases it probably wouldn't be.

Yeah, there might not be for playlists, I'm not sure. There are instances where this issue comes up for platforms and for those you just go to Manage Platforms and add in your notes/other data. For playlists though... I'll take a look here in a few moments and see if I can find anything. Worst case scenario you could probably edit the playlist xmls to add it in.

It comes from whatever's assigned (or, more to the point, not assigned) to them in the LBGDB. If the DB doesn't have anything for them in those fields, it's not going to assign anything to those fields in LB. You can add stuff in manually in Manage Platforms -> relevant platform though. EDIT: I'm not entirely sure where the data is pulled for playlists though. For platforms it's from the LBGDB (and Cave has missing data in the LBGDB).

Ah, okay that makes sense. Something you may want to try is the %romfile% switch. You can add this into a command line section and it will inject the relevant path/filename into the command line. I use it for multi-disk Atari ST games via Steem, but it should work in your scenario as well since it should inject the entire absolute (not relative) path; though I'm not sure how it would handle a :[gamename] immediately after it - it might not work. It's worth a shot though. I've got an example of how I use it below:

I agree. While I appreciate the enthusiasm, I think it would be premature at this point to put you in a moderator position @nikeymikey. I don't think you've been a member long enough or active enough to warrant that at this point. That's not to say that it wouldn't be a good fit eventually, so long as you stick around and are active on the forums for a while.

I can't comment on Android but it works just fine in 64-bit RA.

Well the way it's called is just like a Windows shortcut. You're directing X file to Y .exe and you can inject command line parameters if you wish. If you go to the manage emulators section in Launchbox and edit an entry it'll show you what command line parameters (if any) you're using in either the main emulator tab or the associated platforms (for setting custom command line parameters on a per-platform basis). The end result of a rom in LB directed to an emulator entry with custom command line parameters is indistinguishable from a Windows shortcut with an equivalent custom target path. Emulator: CCS64 Associated Platform: Commodore 64 Default Command Line Parameters: -autoload Rom: Times of Lore Is the same thing as a Windows shortcut with a target path of "Path\To\CCS64\CCS64.exe" -autoload "Path\To\Rom\Times of Lore.d64"

Also... the diehard Trekkie in me would love to see a Big Box version of this!

Nice job! Welcome to the community! You can upload these directly to our server via the "Downloads" tab above and clicking "Submit a file". We have a section specifically for startup videos. Looking forward to seeing more!

It's likely a shader issue like Monkus mentioned. The Mupen/Glupen cores are incompatible with cg shaders and, as result, will be black if you try to use one. You need to use either no shader or a glsl shader (or slang if you're using a Vulkan renderer). You can create a per-core override to set a different shader for that specific core. With content (a game) loaded, go to the quick menu -> shaders -> load shader preset and choose a shaders_glsl preset, then quick menu -> save core override.

I'm not entirely sure I follow. Are you saying you've trying to use one of those multi-game disks (I had quite a few of these on my real C64) and individually select one of the games to run via command line? If so...I'm not sure if that's possible or not. I need a little more context here. Is it actually a multi-game disk? If so, why not just use the separate/individual d64s with separate entries in your library?

So I made an improved version of the CRT Deinterlacing shader earlier today and in the process realized that the one I uploaded previously had absolute (not relative) paths setup so... it wouldn't have worked for anyone other than me anyway. I've updated the original post with it and I went back and updated all the relevant overrides to use it rather than the previous version.

Did you ever upload this anywhere? I'm definitely interested in this.

What, you don't have a bunker and a generator to play all your old video games when the post apocalypse comes? Pffsh...

Well it took a little longer than I intended but the download section has been brought up to date

.ipf is a floppy disk format that was created by the Software Preservation Society (formerly CAPS) for the preservation of original, unaltered (ie non-cracked) Amiga game disks. It's sortof similar to the C64 Preservation Project's .nib files, though unlike those .ipf format is actually supported by emulators (including FS-UAE). However, you might run into instances where the game asks for a password from the manual or something similar because these contain all of the original copy protection. I highly encourage people to try WHDLoad format. These will either be .zip or .iha format. If it's a zip, it will contain a folder with the name of the game and an .info file - these can be imported as-is. If the zip contains an .iha file, the .iha file needs to be extracted and then that file can be imported into FS-UAE. WHDLoad is just a lot more convenient than floppy formats, in my opinion. You no longer need to mess with any disk swapping, the load times are much faster than floppies, and there are no cracktros even though the copy protection has been removed. There are, of course, instances where a game simply hasn't been converted to WHDLoad format yet and you'll have to use a floppy format, but whenever it's available I always use WHDLoad.

Hahaha yeah... we already had a fireproof safe with some physical documents in it so I was like "You know..." and bought a 5TB and dumped a bunch of the important stuff on it and locked it up. I'll definitely feel better when everything is backed up offsite but it's gonna be a good long while. I'm about 1TB down with about 7TB to go... The good news is, Backblaze appears to prioritize the smaller files first (which is a good thing) because that 8TB was comprised of about 1.2 million files and now, with about 7TB left, it's saying I've only got about 8000 files to go... which tells me that basically everything left at this point is big stuff like movies, disc-based roms, etc. which is...basically all the stuff that's replaceable anyway. You can login to your account and actually see everything that it's backed up and the stuff that I'm most concerned with (primarily the project files/masters for my music) are already covered.