k_rollo

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.

Thank you for actively supporting 13.19 concerns. Food for thought, it might be a good idea to retain support for the current LTS release of .NET to maintain plug-in compatibility for a time and to give 3rd-party devs a chance to catch up? Since LB introduced a plug-in system, there will be 3rd-party dependents now. Breaking changes are common for a major SDK update. Cheers!

Hi @AstroBob I have unfortunately deleted the contents of the Updates/ directory a while back to save some space. Is there a support email I can contact to request for the 13.18 installer from the LB Team?

Hi @AstroBob It looks like Supermodel 3 is also affected by this issue. Basically, any emulator that relies on the console window. Since I can't be individually checking all my standalone emulators configured in LB, is there a way to rollback to 13.18 for the time being?

Cc: @C-Beats Hi @AstroBob Thank you for your attention. I can confirm the issue exists on LaunchBox 13.19 (free version), where launching Dolphin causes it to flicker: LB319_Dolphin_Flicker_Issue.mp4 Upon invoking the Task Manager (Ctrl + Shift + Delete), the flickering stopped, but Dolphin (latest nightly) did not completely launch to exclusive fullscreen. This is my Edit Emulator window (no AHK scripts): Dolphin was able to lauch normally to fullscreen after turning off the Atempt to hide the console window option as suggested. (Note: I use the emulator config for fullscreen rather than passing cmdline args). Hope a hotfix can be deployed as it is a stopper defect if the user did not know the specific workaround. Thanks!