The Cheatsrichter

Gw2 Launchbuddy Version 4.0.7

Added 2023-07-25 17:41:57 +0000 UTC

Finally, a build that I'm happy with! Thank you all for your patience. This maintenance build focuses on user-reported issues and bugs. Overall, Windows 11 needed some tweaks, and I am still closely observing it (I had to order a new small PC, as a virtual machine does not suffer from the issues reported by users). The CPU footprint of the client tracker has been reduced. And last but not least, the "Recreate Loginfile" feature has been updated to work with the newest Chromium-based GW2 update.

If you are still experiencing issues with LB, please report them right away! If the issue is related to client tracking bugs (launch percentage not updating), please right-click the "x" button and send in a debug info report.

Thanks again to all my supporters for making this project possible. Further patches are coming soon as I want to push LB for the next x-pack release even further.

Changelog:

Improved computer vision on high-resolution gaming setups.
Optimized CPU usage of computer vision game clients trackers.
Added child process cleanup for GW2 game clients. Closing a game client via LB now also makes sure that all child processes of that client are closed.
Adapted "Recreate Loginfile" to now be compatible with the new Chromium framework.
Added Win 11 fix for a mutex closing problem.
Added Win 11 UI scaling issue workaround.
Increased automated email typing speed delay from 50ms to 80ms to reduce incorrect email inputs.
Changed Version.dll module trigger (game client tracker status 0%) from a blocker trigger to an optional trigger.
Fixed a bug that tried to restore backup login files on LB close even when none are present.
Removed -dx9 and -dx11 options as they are no longer supported by ArenaNet.
Removed -usecoherentui option as it is no longer supported by ArenaNet.

Additions:

- A win 11 bug in loginfile creation has been reported and is fixed. This fix will be included in the next upcoming version 4.0.8. Thanks to Todd Sieber for the remote debug session to solve this issue