If you use GW2 TacO ReActif installed with the executable, you will not have to do anything to keep your validated settings and markers. Here is how to do depending on the type of update. Performance/stability: TacO now waits for the mumble link to update more aggressively.ĭuring an update, you can perfectly keep your validated settings and/or markers.Performance: Trails and markers are now grouped for each map ID, which means far fewer checks per frame.Performance: Category visibility settings are now cached more aggressively.Performance: Teamspeak integration is now only checked if the TS3 window is open.Performance: Small fonts now also have outline versions and the outline does not need to be rendered separately using a 3x3 display.Performance: Track textures are now cached more aggressively.Performance: replacing strings with string ids in tag category system.Added warning popups when TacO misses important data files (mainly occurring when overlay is run directly from the archive without unpacking).Added additional checks to avoid a crash related to switching menus in rare cases.Fixed handling of the Characters API endpoint - this should no longer crash if the API returns unexpected results.Running at uncapped framerates, with some popular large marker packs loaded, TacO's uncapped framerate was increased from 120 fps to ~2000 fps, for a ~16x performance boost. There have also been dramatic performance improvements. To disable crash reporting, you just need to set the "SendCrashDump" value in TacOConfig.xml to 0. No credential or GW2 account information is sent ( since the overlay doesn't have access to it anyway). The information sent is the TacO process dump file and the session TacO log file. This system sends incident reports to the cloud for easy triage and analysis. In order to better be able to track unreported and rare accidents, a BugSplat accident tracking system has been integrated. TacO's development is ramping up, this time with a bunch of stability and performance improvements.
0 kommentar(er)
