SentaiBrad

I'll laugh and pretend I know who the hell that is. It reminds me of the 80's and Back to the Future Part 2's odd view of the future though.

Did you change the driver that LaunchBox / Big Box is looking for? I assume it's read as a controller, so either the driver needs to be selected right or the check box to "use all connected controllers" would need to be checked. I would say to check in there first, but I don't know what has changed in the set up to suddenly stop working, and I don't have one of these myself.

What @spycat! Thanks.

Sweet! I very much appreciate the help! You are right in that Jason wants to improve ScummVM, and it's becoming a heavily requested revision, but he just hasn't gotten there yet and that is why I was asked to hold off on it or I would have had something ready to go already. I'm also famously (or infamously?) not a RL person, so I welcome the extra view for someone who is an RL person. I may not like it or thing it has it's place, but I know that there are a ton of people who do want it or do like to use it, but for me to create a tutorial with it would be disingenuous. So when a section of the audience that I can't help is helped, I am very much excited! This is awesome. There have been others who have created tutorials, of course we have Monkus who I couldn't ever thank enough, but we also get users who do tutorials in other languages than English which is also amazing. Anyone who takes the time to dedicate a portion of their life to genuinely help all of us out gets thumbs up from me.

Well to continue down the drive make and model line, do you happen to know if it's 5400RPM? It being a green drive vs a blue or a black WD can also make a huge difference in how it handles power consumption and performance. If it's on a SATA2, or even worse a SATA1 line, performance can also degrade. Even if the port is a SATA3 port, if the cable or drive are lower SATA then it won't matter. The drive, cable and port would all have to be SATA3. In the video that I posted, it does show that in terms of performance for reading your library CPU is most important as it pings the most, and while super fast hard drives may not improve performance too much, a super slow drive can more easily effect it in the opposite. I actually have my stuff on a 5400RPM 8TB SATA3 drive. I wish it was at least 7200RPM, but for the price per GB it was pretty fantastic to have it in an 8TB form, and it seems to do the job just fine. It will take a second to boot open if it's been left un-used for any length of time, but I can help that a bit I believe with some software tweaks.

Crap, now I do too.

It's actually BIOS files that are linked, so I am partially tempted to remove the video.

Crap, I was hoping that was it. It was a long shot, but you never know. I think it might be a setting off then. I know that the PS4 controller can sometime cast two inputs, or rather that it's normal drivers conflict with the Input Mapper drivers. Re-ordering them in the Game Controllers window to put the "360" drivers on top can help in some situations, and as well I wonder if the Direct Input check box shown off in @DOS76's screen shot are throwing anything off. It's using Xinput for the 360 stuff, so that's not even needed. The original drivers might be. So part of me now thinks it's a settings issue rather than a driver specific issue.

VLC is generally good software, so I am lost as to why it causes odd issues (not just this new issue, if that does seem to be the case).

The ones that we already talked about, and merging the few we talked about. Actually, when all is said and done, there will be more platforms than we currently have.

Which XML did you edit? Your platform XML's? If you edited Metadata.xml then this will reset every single time it's updated, which can be often.

Then I go back to my other solution, Grab Input Mapper. DS4W might be the issue here, but it's hard to tell. I've never had issues with using controller automation and my PS4 controller.

I could have sworn that the Supermodel set is completely different, completely separate.

Also, should see about replacing DS4Windows with Input Mapper. I believe DS4W is not being updated anymore? I don't quite remember. IP also has Macro's to launch stuff as well. As far as I know though, the Controller Automation input works with everything, including ePSXe. I don't see you mentioning that in your post, have you been using this? It's in the LB Options menu.

Those extra platforms should have been removed already, so I'll see if @Vlansix can move that up a bit. This will eliminate the problem all together and not require a guideline alteration. The only system that is an oddity is the Sega Model 3. It's not tied to MAME, has nothing to do with it, but it's still Arcade technically. With Scrape As anyways, it doesn't necessarily matter what our default platforms are, someone can break out different sets all they want.

LaunchBox does use relative paths if it's all on the same drive. So my roms and emulators even have relative paths because they're all on the same S drive. Initially I would make a copy of your entire LB install, might as well if you have the space, but as LaunchBox gets updated just backup the core files. If you change up a platform or something major, you can either do a full back up, or a core backup then replace the system's media with the updated version, if that makes sense. If you just copied over the core LB stuff, and you were suddenly missing just media, the Metadata and Media Downloader will fix that. You just click on a game, Ctrl + A to highlight them all, then Tools -> Download Metadata and Media. This will re-download everything. Of course it's not the fastest method, but if you wanted your backup to take up as little space as possible, so you only backed up the core, then this is a possible solution. I think backing all of LB up, and updating the LB files every so often, and replacing the media when major changes happen might be the smartest method. If you do use BackBlaze too, I would exclude your local backup from backing up again to your cloud backup, as uploading that much data could take a while.

For the N64 I find that I have to use an N64 pad, so I have a Retro Link USB one myself.

If it's the API error then it's on the EM side of things.

Ah yea, I didn't even think to go down that route either, file system and if it's MBR or GPT.

I think the No-Intro sets are better than the software lists, but it's just a difference. for CD-i I got the CHD's to work over bin and cue, so it's situational. TOSEC has too much other stuff bundled, but at least it has proper names. Some software lists do to, like CD-i, it had the full names. As long as it has the full names you are in business, but if it has MAME styled short hand, you'll need to convert it or LaunchBox will, and it only converts mame currently.

So I removed that last bit, I would appreciate it not being linked anymore. Past that, I am sure there is software that can do the mirrored thing, but the one I found is from 2003 and doesn't mirror video.

Yes, the iSCSI controller, not a controller as in a gaming controller but controller in the sense of the thing that controls x hardware.

How expensive is the proper controller for it? There's a network bay I've been keeping my eye on, and it's $100+ for just the bay.

Some services can be disabled to help if someone wants to really try and figure it out. I also recall most of our issues with other software being AV and Firewall related, but I don't remember this one exactly either. With a fresh install, disabling some of the more annoying services (or un-needed services like the Printer Spooler for example), keeping it to the default Windows Defender and Windows Firewall, running IOBit's Driver Booster, the Standard K-Lite Codec Pack install, making sure all the pre-req gaming related software is downloaded (which can be grabbed from the Gaming Module of Driver Booster), and having Windows fully updated is the best starting point suggestion I can give to anyone. Most of all making sure every single one of your drivers are updated, and trust me, there are a ton you would never realize need updating.

You can just use a regular rom set with MESS, or in the Atari 2600's case with RetroArch. I have made a few tutorials where MESS was the only option, or the better option, and I used games with regular names.