Santherus

Just as a confirmation/summary; the actual issue of the incorrect reporting of the BIOS isn't resolved: There's the below option (noted by the devs) as a sort-of-workaround. Not one for me, but YMMV. "Update is already out. You can just check the box to not show the BIOS error in LaunchBox if you don't want LB to warn you about stuff like that. No functionality has changed in this version once you check that box and ignore the feature."

Good stuff. Just shout if you need anything else👍

Details page: Have also checked absolute length of path to the pcsx2 bios folder - it's not excessive at 81 characters in length.

Curious. No change on reinstall (13.14) - I should note that the other retroarch core pages DO correctly list the files/dependencies as you stated (e.g. as below). It's just the PS2 page that seems to be reporting strangely. (example of a 'good' page below)

I've recently been setting up PS2 emulation in launchbox, using retroarch as emulator. There's a bit of an oddity that I wasn't sure whether was a Launchbox or a Retroarch issue; when I attempt to launch roms, I'm told that a dependency isn't satisfied. When I check the dependency (screenshot) It shows that the bios can't be found... except that I DO have the correct bios in the correct location, and that 'Play anyway' will correctly launch the ROMs. I'm posting so that the Launchbox team can have a look - it's reporting the bios folder name as bios' instead of bios (see pic) in the first half of the text - the \system\pcsx2\bios location specified contains my bios files, but I think the verification might be using an incorrect name (with a ' appended) when trying to verify. Note that 'Open Location' opens my pcsx2 folder, not my pcsx2/bios folder. So I'm assuming that there's some sort of path issue confusion due to the ' (maybe)?

Yep - I'm doing that; I made sure that I read through the whole (8 pages!) thread before posting; turns out that was incorrect - saw advice telling me to ensure that there WAS a trailing slash in the URL: turns out that this was incorrect - REMOVING the trailing slash allowed import to work successfully.😵 Simple as that. Thanks for the help, both of you 👍

Thanks for coming back to me 👍 Ah - So (assuming that your personal URL is also https or that they're interchangeable), I have some sort of other problem; Am a bit stumped; launchbox should be using the correct URL (as below) that I've keyed in: http://steamcommunity.com/id/santherus/ Have set steam profile to public. I also have the correct API key in there - I even revoked the existing key, and created a new one to no avail - still not able to access my account. Not quite sure where to go from here - In case it matters, I'm using the new release of launchbox to connect for the first time; had no problems with origin/gog/epic connection prior to this. Any ideas that might help?

Just attempting to connect, and have found that I'm unable to connect my steam account; I note that in launchbox, the URL prefix is: http://steamcommunity.com/id Whereas my actual steam custom URL is prefixed with: https://steamcommunity.com/id/ i.e. We're in https-land! I'm assuming that this is the root of the problem - launchbox will never find my details as it's trying under http:// instead of https:// Am I missing something, or is this a genuine issue?