k_rollo

Ah, I get it now. Your Emulators folder is inside the LaunchBox folder. I've configured my standalone emulators separately a while back before I started using LB that's why mine's outside. The ..\ means "go up one level" in file and folder paths. Apart from that, I don't see anything glaringly different from here. Hope someone has other ideas.

No, I meant this: Not sure if LB knows it's a relative path without the ..\ before the name of the first directory. Yours doesn't have it in both locations. This is my actual global setup and it works perfectly. Nothing else. Can you try just manually browsing to the Supermodel.exe and ROM locations again? Let LB set the paths, don't type them in or anything.

It did help. It eliminated the cmdline options as suspect and confirmed the latest Supermodel build works as it should on its own. 😄 When you don't know what's right, you eliminate everything that's wrong. That's the key to deductive logic a.k.a. troubleshooting. Now you can confidently focus on LaunchBox. The latest Supermodel-487d642 works flawlessly on my LaunchBox-13.22 build by the way. Get the global emulator settings to work first before trying any custom launch params. The application path in your first screenshot seems off to me at least. Relative paths on mine have ..\

Try to launch the emulator via cmdline without LaunchBox first. Always a good diagnostic step to troubleshooting.

I was submitting a fanmade 3D box art and noticed there wasn't an image type for it: Could be useful to have one. Thanks!

I know. I deleted the contents of the Updates/ directory to save space and had to contact LB Support to send me an installer. I was able to find it from another website called UpToDown before the support team responded, so I was at least able to verify the SHA1/MD5 with the one they sent.

Compared to the other updates, 13.19 saw a major SDK change from .NET 6 to .NET 9. This type of jump is bound to have breaking changes and could have used a longer testing cycle during development. I think this is also the first time such a major change was implemented, so there are definitely lessons to be learned here. The most practical solution as of the moment is a rollback to 13.18 and stay there for a bit, until the defects raised from 13.19 has been ironed out. As someone already said, staying on an older version is not _always_ bad, specially when compatibility/stability is the priority. It is the same practice I do with major OS upgrades. I did not upgrade to Win11 until it was 11mos later. Early adopters tend to get bitten first with cutting-edge changes.

Sounds great! Keep that around just in case.

Hi all, good news! LB Support (Breandan) came back to me and sent me a G-Drive link for 13.18. Turnaround time is around 48-72 hours which is reasonable. @Gaming4MyKids I checked the hash from UpToDown and they all match the original file from Support if you (or others) still need it quickly. Meaning, the file has not been tampered with. That's all folks!

Ah, good catch. Thanks! My poor eyes only see .19 actually haha. But yes, it is 13.18 -> 13.19 update. That is indeed a mighty jump. I don't mind staying on 13.18 for the time being to prioritise compatibility/stability.

Sometimes, a rollback is warranted and seeing the myriad of reported issues with 13.19 as of late, it is reasonable to stay on a previous known stable version. LB website does not provide an official way to acquire older installers unfortunately, but not hard to find. I'll probably wait until 13.19 weathers the storm. It's bound to have breaking changes with plug-ins here and there due to a major move from .NET 8 to .NET 9. I personally go for compatibility/stability over speed. Glad you found a solution for you.

Hi @AstroBob Is it not possible to maintain backwards compatibility with .NET 8? It is LTS after all and .NET 9 is STS. Cheers!

I haven't received a response from the support email, but I found 13.18 here if anyone else needs it - <removed> Scanned with Microsoft Defender. Looks clean.

Thanks, I have sent the email.