Zombeaver

You likely can't. AHK is very picky/finicky when it comes to joystick hotkeys. You can't assign the Xbox button on a 360/One controller in AHK (it doesn't recognize the input) so I would assume the same would be true for a PS4 controller. You can test by downloading the joystick test script here: https://autohotkey.com/docs/scripts/JoystickTest.htm Run the script with the controller connected and if it doesn't show a button name when you press the home button you won't be able to use it. If it does show a button name you'll just need to duplicate your script and use the button as the hotkey to trigger it. Something like 1Joy8:: followed by the close command.

Absolutely! Got a bunch of stuff left to do. I just needed to take a bit of a break. That C64 set took a lot out of me - that was about two solid weeks of work that absorbed 100% of my free time during that period. Been taking a bit of a rest and actually playing some games for myself the last week I think Star Trek: A Final Unity will likely be up next.

No problem. It's usually the small things

I'm talking about launching standalone and RA through Launchbox. It works fine. You uh... might wanna try adding a .dll at the end of your core there...

It's working fine here, both in standalone and RA. You'll need to send some screenshots. I need to see 1) the Launcher tab for the game 2) the DOSBox tab for the game 3) the emulation tab for the game and 4) the associated platform tab of your Retroarch emulator entry with the command line shown for MS-DOS. Things like joy2key and xpadder generally don't work over streaming services like Steam in-home streaming/Steam Link unless you're using VirtualHere (which has its own share of issues). DOSBox's own built-in mapper is quite robust, however, when it comes to remapping inputs and should work over streaming. It's accessible via Ctrl+F1 while DOSBox is running. If you want different mapping for different games you're going to need to create separate .confs directed to different map files. You really should be creating individual .confs anyway, to be honest with you. Many games need different settings and there's not just a one-size-fits-all setting solution when it comes to DOS games.

This is covered in the video. They're separate.

You're not really providing much useful information here. 1) Send a screenshot of the contents of the .zip you're trying to use. 2) Send a screenshot of the hard drive tab for the config.

You're not giving enough information here. Are you actually indicating in LB that you want to use DOSBox for them (default behavior for DOS games)? Because, if so, you shouldn't; not if you're planning on using RA. You'd need to uncheck the DOSBox checkbox first, then go to the emulation tab and select Retroarch as the emulator. You'd also likely need to create a .conf for the specific game with the correct start commands (mounting paths, etc.). Generally you can't just have a core in your associated platforms and fire up a DOS game like anything else. It's not like throwing a SNES game at it. I actually don't recommend using RA for DOS as it's 1) more convoluted than working with standalone DOSBox and 2) has some significant limitations not present in standalone DOSBox like not having access to virtual midi devices like Munt and VirtualMidiSynth 3) has a really awful way of handling cycles. That said, if you really must use RA for it, the way I usually do this is by adding it as an additional app, with the default being set to use standard DOSBox. So, in this case, the launcher tab is directed to the game .exe, the use DOSBox box is checked in the DOSBox tab, and I've directed it to the .conf that I've created for the game: Then, in the Additional Apps tab, I've added an app for Retroarch. I've named it "Retroarch", directed it to the separate .conf that I've created for the game for RA, and I have Retroarch selected as the emulator. Now I can start the game normally and get normal DOSBox or right-click on it and select Retroarch and start it there. If you were to only use RA, you'd need to uncheck the "Use DOSBox" box in the DOSBox tab, then select the .conf (or .exe, though this won't always work) in the Launcher tab, and select Retroarch in the Emulation tab.

I'm not sure what you mean by "zip folder" but I answered your question in the other thread. You just choose the add button and navigate to them.

You just need to navigate to them. Use the custom default config, go to the hard drive tab, click the add button and then select the zip you want. I show this in the video. If the folder that it defaults to when you click the add button isn't the right one, just use the up (parent directory) button until you get to wherever they are.

FXAA has the tendency to make things a little too blurry in my opinion. It most assuredly doesn't "completely fix" aliasing. It blurs everything, which makes aliasing slightly less noticeable while making everything blurrier in the process. It's not going to "hurt" anything in the sense that it'll break anything, but I don't think it looks better, personally. Small details, text, that sort of thing, often turns into a blurry mess. Pretty much, yeah. You can change to Blend bff/Blend tff or Auto (which will use one of the Blend modes) which will eliminate jitter, but will make everything blurrier (even during moments that would have no jitter with a Bob setting). Generally the jitter is only present during non-gameplay moments (like a pause screen or something), if at all, if I'm using one of the Bob modes. Some games have no jitter at all even with a Bob mode. The only games where any of this is relevant is ones that have "Bob tff" or "Bob bff" listed under "Interlacing" on the spreadsheet. Anything else is going to either be one of the Blend modes or Auto which will either be Blend or none.

Good deal! Happy to help! Haha. It's a habit lol

Yes, just use the configure button and then go into the video settings and change the scaling. I have some other tips in my config thread:

No problem!

Well there's your problem. I need to see the associated platform tab of your PCSX2 entry and the emulator tab of a specific game in your library. EDIT: And a screenshot of the name of the platform in your library.

Here's a quick video of the entire process from beginning to end:

It sounds to me like you don't actually have an emulator assigned to your library entries. That message sounds like a Windows prompt, not one from PCSX2 or LB. Send a screenshot of the emulator tab from one of the library entries.

Again, nothing's changed from the video. Follow the video/what I posted above, and it'll work. 1) Create an account with for OpenRetro 2) import your games into FS-UAE, 2) export them as UUID with the exporter, 3) import those UUIDs, using FS-UAE UUID as the emulator, tell it to use folder names in the wizard. If it's not working, you haven't done something. What you have and haven't done I don't know because I can't make much sense out of half your post. You have to make sure you're using the right checkboxes in the emulator entry as well (which are shown in the video). You have to create custom configs for games that aren't imported into your FS-UAE game list. This is shown in the video.

Okay, the standalone and import versions are now up on Zomb's Lair.

Nothing's changed as far as the exporter is concerned. What's in the video is still correct. The normal Launcher can be used for both custom configs (FS-UAE in LB) and UUIDs (FS-UAE UUID in LB). They still have to be separate emulator entries because they require different checkboxes to be used in LB. The only thing that's changed is that the custom Launcher that Eirulan made to address the saving bug is no longer necessary as that bug has been patched - there's an annotation in that entire section of the video noting this. The actual export/import process is completely unchanged from what's in the video. 1) Load up the exporter and direct it to the launcher.sqlite file in your FS-UAE\Data\Databases folder 2) Export your games into folders 3) Import those folders into LB -Indicate that they're Amiga games -Choose FS-UAE UUID as the emulator -Check the "use folder names" box in the wizard If you're importing custom configs: 1) Go into the FS-UAE\Configurations folder, and drag the .fs-uae files into Launchbox -Indicate that they're Amiga games -Choose FS-UAE as the emulator -Do not check "use folder names" in the wizard

I forgot one thing - if you want to use in-game saving in Project Firestart, you'll need a save disk. I took a blank c64 disk image and formatted it in the game so it's setup and ready to go. It just needs to be placed in the folder with the rest of the game files, and then selected when you want to save. If you were to ever need a different blank c64 disk for something, I've included it as well. Saves.zip EDIT: Here's an update package that includes the save and blank disks, as well as an updated Readme and updated C64 Dreams platform XML - I added some additional controls notes to the description for Project Firestart. Update.zip

You'd have to ask @alec100_94. I'm not sure what would cause that.

Alright, final version of the LB import package is now done. I implemented the above change, updated the readme, reset all the play counts to 0 and added a few more manuals that were sorely missing (Supremacy, Project Firestart, Times of Lore, Shadowfire, etc.). The Supremacy and Shadowfire ones I had to assemble manually from individual images The standalone package, writeup, and Zomb's Lair entry should be up tomorrow... err... today since it's now 1:40 AM. Download Link

So here I am basically ready to package this thing up, and I realized there was a way to improve it. The method I had in place for changing disks on multi-disk games was functional but had a couple flaws: 1) Because the script was based on finding the correct, specific position in a long list of files for a specific game, if you were to add games into that list that were in the same letter of the alphabet (it jumped to the first file starting with the relevant letter, then went down the list from there), the script is now essentially broken because now the number of positions to move down the list would have changed - not a big deal for this isolated set, but I want to give this treatment to my entire C64 collection, not just these 128, and even if I had them all squared away, adding new games down the line would break the scripts because of this. 2) Games that are more than 2-disks required more manual work on the part of the player as I don't know how to make AHK remember whether or not you've used a hotkey previously, so instead I just made it take you to the first disk for the game, and then you could move up or down and select the one you wanted. Both of these can be fixed by making the following change: Instead of having all the files in one giant list, move them into their own subfolders for each game, and set that folder as its own "Drive" in DOSBox to load from. Now it no longer matters where in the alphabet the game falls, because as far as CCS64 sees, it's the only game it has access to. Now it's always going to be the same position for disk 1 and disk 2 because they're always in the same spot for all games (down twice from the top for disk 2 and down once from the top for disk 1), because they're in their own folder. Now it no longer matters that I don't know how to make AHK remember whether or not you've pressed the next/previous hotkey previously, because CCS64 itself stays in the last position you were on in the disk list when you pull it up again later. Technically I could have done this with the previous setup because of this, but it too would have broken if a new game was added because of the reasons above. So after making lots of folders, moving lots of files, and replacing lots of text strings in those files... it seems to be working just fine. I've still got to update the locations in LB and then do some more final testing with it, but I should have a new version out tonight.