Zombeaver

To my knowledge, no. There might be a way to rig something up with an external application and/or AHK, but I couldn't tell you specifically. Windows does have its own built in on screen keyboard function from 7+ in Ease of Access. It doesn't have F-keys though. You could probably use something like this + an AHK script to pull it up/hide it with a button/combo. I do know this is a feature that Frode's planned on adding for quite a while. To my knowledge, no. Not that I ever discovered anyway. I wish there was as that would certainly save time. P-UAE doesn't support WHDLoad unless you were to manually install an instance of Workbench to make them usable or converted them into .hdf format. It doesn't have pre-made configs for each game either.

No problem! ?

The platform names don't match. It's called "SNK Neo Geo AES" in your associated platform screenshot and "SNK Neo Geo" in your game entry screenshot. They need to be the same between them in order for it to know that you want to use one with the other. If your Neo Geo platform is just called "SNK Neo Geo" then you need to change the platform name to that under associated platforms.

The problem with that is that now you're beholden to someone else to make something work for you by doing some proverbial black magic behind the scenes. The more you can move away from that - not just in RL, but in LB, or anything else really - the better off you'll be, because when that thing breaks down, and it always will at some point, then you won't be up shit creek without a paddle. All of these tools provide a basic framework that goes a long way, probably far enough for the vast majority of users, but truthfully none of them gives me 100% of what I want - and whenever some niche need isn't met, I'd rather just take the time to figure out how to fix it exactly to my needs instead of relying on someone else who probably, understandably, doesn't see the need and isn't likely to assign any great priority to implementing it. There are all kinds of niche, non-sexy/flashy things that I'd like to see in LB that probably aren't ever gonna happen, but that doesn't mean they're completely out of reach in spite of that. I'm not a programmer by any stretch of the imagination, but I've managed to teach myself enough by way of a multitude of resources that are out there to achieve what I want. I think a certain amount of that is just inherent in this hobby to be honest. I would probably argue that if you're in the emulation scene and you don't like tinkering then you're probably in the wrong scene. I do understand the desire for things to "just work" though, certainly. And if it's filling a need for you, go for it. It's a tool, like anything else. That said, if it stops working or creates some other tangential issue (which I can tell you isn't exactly uncommon), however, you'll be in trouble - especially given that you're immediately cutting down on the number of people around these parts that will be able to help you. You have to keep in mind that we end up fielding questions about "How come this isn't working?" all the time, and as soon as someone says "I'm using RL by the way", a good 75% of us have just left the conversation.

I feel like this would be fairly easy to accomplish with Antimicro (similar to joy2key) and an AHK script. It already works based on profiles and those profiles can be loaded from command-line. It's easy enough to use them on a per-game basis, would just have to make a script and/or a plugin that would let you create these directly through the LB UI. I'm sure I could come up with an .ahk script, but I know nothing about plugin creation. I'm sure someone here could though without too much trouble. I'd say you're definitely in the minority there, but more power to you. I don't think there's anything particularly cumbersome about pulling up the RA UI and selecting Quick Menu > Controls though... This is actually quite easy to do through LB. No complex scripts required. You just add a disc as an additional app, check "automatically run before main application" and "wait for exit". This assumes that you have some sort of mounting software like DT or VCD or if you're using W10 it supports mounting natively. If you want it to unmount it afterwards (not required as any new disc image would replace the current one anyway) you could make a script for that, which would vary depending on the software used. You'd just add it as an another additional application and tell it to "automatically run after main application". The contents of this .bat are simply: "C:\Program Files (x86)\Daemon Tools Lite\DTLite.exe" -unmount_all People are welcome to use whatever they want, but in my opinion RL's proverbial bag of tricks continues to look less and less impressive as time goes on; while it's simultaneously adding in an extra layer of complication and another point of potential failure, mostly unnecessarily at this point.

This is going to be implemented into v0.19. It should be noted however that: 1) This is not a one-and-done affair, as this function is specified (or not) not only in the central retroarch-core-options.cfg, but in every single .opt file that is created for games in special cases like when joystick port 1 needs to be used, true drive enabled, etc. These are located in C64 Dreams\C64 Dreams\Retroarch\config\VICE x64. There are over 350 of these currently. I've already changed them all on my end so they'll be updated in the next version, but any cases where these are present the field will need to be updated. The easiest way to do this is to go into that folder, sort by type, select all .opt files, drag them into Notepad++ and then do a find and replace of vice_mapper_x = "---" with vice_mapper_x = "RETROK_F11", then select "Replace All in All Opened Documents", save all, close all. 2) There will be a handful of exceptions where this won't be used, because of custom mapping that's using the button, like in the case of Fairlight: A Prelude.

It's in the tutorial.

I'm using a 360 controller in the tutorial.

I'm not sure, although your platform is named Playstation 2 which I don't believe is the default (Sony Playstation 2). I don't think that in and of itself should be a problem so long as you have it setup to scrape-as correctly. Beyond that the only thing I know to suggest is to maybe try unblocking the .dll - that can sometimes cause issues.

Might have been the previous version, I'm not sure. It does look right now.

Use the attached. It has a .bat for swapping in the blank overlays just like swapping to the other options (C64 Dreams\C64 Dreams\Utilities\Overlays). I've also corrected the core override. You still had overlays disabled. It's not going to do anything so long as those are turned off. 1920x1200.7z

Replace C64.png in C64 Dreams\C64 Dreams\Retroarch\overlays with the image below and it'll work (it's just a 1920x1080 image that's nothing but transparency). Make sure that you haven't turned off overlays. EDIT: You do have overlays turned off in the core override you provided:

I could probably work the virtual keyboard in in the future. There's still a small amount of wiggle room with the controller mappings.

I can't give you a number but it's pretty unlikely that 100% of them are covered and that 100% of what's covered is correct considering I ran into problems with a test sample of only a couple hundred games. The reason the games I mentioned didn't have issues anymore is that the configs have been updated since then - their db is just like the lbgdb, it's user-maintained. Better than when I made the video? Sure. 100% perfect? Highly unlikely. I couldn't tell you what else is missing or wrong at this point. Any time I've needed to change something from the automatic config, I've made my own config. If there's an easier way to resolve your specific issue, I'm not sure what it is. You would be better served directing that question to Frode himself on his Discord. It's not working for me either. I'm getting an error on both the normal version (Oil Imperium) and the ReLINE one (Black Gold). The .adf version (specifically I was using "Oil Imperium v1.1e (1989) (reLINE) [cr MWB - Ikari]") seems to work though. I'm not sure what the deal is with the WHDLoad versions. Might want to ask Frode. The data that's on OpenRetro for the WHDLoad versions appears to be wrong as well, probably from an older version. The checksums don't match.

Ah, yeah 3281 is what the update will be using, but that's not out yet. The current configs are using the version that's in the opening post.

That should only happen if you're using an older version of PCSX2. Are you using the one I linked in the opening post? I have a specific version included that you should be using if you're not.

You use the right stick or arrow keys to move up and down the list. That's not too common, but some trainers do it.

Try replacing the Windows 95.cfg in the Obsidian\configs folder with this one and see if that helps: Windows 95.cfg

lol I'm gonna start using that Glad you got it sorted. As far as "how to play", while it obviously isn't going to cover everything, you may want to consult the game details spreadsheet if you're having issues. There's a link in the opening post and there's a shortcut to it in the C64 Dreams\C64 Dreams folder. In some cases there will be information there that you'll need. I've been in the process of making custom notes which you can toggle for specific games as well. A few games include this like 221B Baker St for example. For Raid Over Moscow specifically: I can personally recommend the Mayflash F300. It works great. You can go cheaper with the F101 or more expensive with the F500 too. These all support Xinput on PC, so they're treated just like an Xbox controller.

Then there's either something wrong with your keyboard or there's something that's causing it to not be recognized/read by Retroarch - my guess would be your keyboard encoder joystick. It could be that it can only accept one keyboard at a time and it's seeing the joystick first. My suggestion would be to disconnect it and see if that fixes it.

Are you pressing N (no) or Y (yes)? It's asking you to choose the trainer options - that's what the (Y/N) is for. You have to press one or the other three times there (once for each option) to continue. If pressing N or Y on an actual keyboard isn't working there, I'm not sure what to tell you other than there's probably something wrong with the keyboard. This is the most common scenario for trainers - it's why I have N and Y mapped to the controller. Most of the time they'll just ask you to press those to choose your trainer options. Some will ask you to press H or T for high score saver or trainers, some will then ask if you want to load or reset the high scores by pressing L or R. You just have to follow in the instructions in the trainer.

As I say in the opening post, a keyboard is required. The shortcut keys deal with the most common scenarios but you'll never be able to account for every situation with just a controller. There's too wide a range of inputs required, not to mention the 60+ text adventures in the collection and 100+ that are keyboard input only. I can't speak to the keyboard encoder, as I have no experience there, but 360/XB1 controllers most assuredly work with this as I use both. Anything that's xinput based should work. I have a Mayflash F300, for example, and it works as well. Core and, in some cases, per-game remaps are used (C64 Dreams\C64 Dreams\Retroarch\config\remap\VICE x64), so if mapping changes aren't sticking, that's probably why. You'd have to overwrite them. My suggestion would be to do something to reconfigure the inputs on your controller so that they match the keyboard controls (listed in the opening post), however. No matter what though, you're going to need a keyboard either way. I'll add Drelbs in the next batch.

Sorry for the super late reply, but relative paths are usable in DOSBox .confs. They're relative to DOSBox's location. .\ = DOSBox's folder ..\ = Up one folder from DOSBox's folder ..\..\ = Up two folders from DOSBox's folder etc. So let's say DOSBox is located in C:\DOSBox and your game (we'll use Dreamweb as an example) is in C:\DOSBox\Games\Dreamweb mount c ".\Games\Dreamweb" ...would mount that folder as your C drive. If you wanted to mount a specific subfolder as a cd drive, the same rules apply. You can also do this with disc images, so you could do something like: mount c ".\Games\Dreamweb" imgmount d ".\Games\Dreamweb\Disc Image\Dreamweb.iso" -t cdrom (or -t iso) If it wasn't located in DOSBox's folder, you'd just need to adjust the paths upwards to the point that it was an accessible subdirectory. It does have to be on the same hard drive as DOSBox. Let's say your folders are: C:\Emulation\DOS\Emulators\DOSBox\ C:\Emulation\DOS\Games\Dreamweb\ You'd just use: mount c "..\..\Games\Dreamweb" etc. Using relative paths, you can move the folders wherever you want, so long as DOSBox's location is moved along with them. This is essentially how all the DOS stuff I have on Zomb's Lair works, DOS games on GOG, etc. They use a predesigned structure that contain the game and a copy of DOSBox, which means you can take the folder that contains both of them and move it wherever you want, and the path structure will remain intact, because they're still the same, relative to each other.

That's awesome to hear! That's exactly what I wanted to accomplish with this. Have fun! Hope you enjoy it!

You can press numpad minus + F1 or back + xbox button on a controller. I can give you some specific suggestions that are likely to fix it though - I've been meaning to mention this in the opening post [EDIT: Added them under a section called "Performance"]. If you're having performance problems, you should go to C64 Dreams\C64 Dreams\Retroarch\config\VICE x64 and open VICE x64.cfg. There are three lines at the bottom that you should try adjusting: The first thing you should do is adjust video_frame_delay down by 1 at a time, down to 0 if necessary, and see if that fixes it (it probably will). If that doesn't work, the second thing you should do is set video_hard_sync to "false". If that doesn't work, try setting video_threaded to "true". I really don't recommend that unless absolutely necessary though. The previous two will produce a small amount of additional input latency, but threaded video increases it more significantly. It does have the benefit of letting it work on basically a toaster, however.