Squad Update: V2.10
Today’s update brings in an urgent server crash fix we have been notified about since the release of V2.9, as well as a couple of fixes for some long-standing client crashes.
See below for complete explanations of these issues, and thanks again to those who submitted server crash logs to help us address these as soon as possible.
Be sure to let us know if you continue to experience any of these issues through our dedicated channels and try clearing your in-game cache if you continue to experience residual issues.
- Fixed the Server Crash related to UB32 Rocket Pod & SPG9 Recoilless Rifle’s backblast.
- Fixed a problematic and difficult to reproduce client crash that is related to the Particle System and switching maps. The Particle System was reusing a Particle Emitter Instance from a pool, which is tied to the FX System in the current map world, which was persisting to the new map world after a map change, and then re-using one of these instances from the pool, but the FX System it was created with was no longer valid. There has been an attempt to fix the same (or similar) issue with particle rendering, which essentially iterates all particle systems at the end of the match and force deactivates them. This fix has been extended to also reset the particles, and therefore clear the instance pool which should hopefully fix this assertion failure. As we still do not have proper reproduction steps for this, this is not straightforward to test or be certain the issue is resolved completely. If this issue persists, full crash dump logs are appreciated to investigate the issue further.
- Fixed a Client Crash when switching maps, related to the vehicle tire configs. After investigation, the client crash was determined to be caused by a race condition in the Tire Config. Tire Configs are modified on initialization and destruction, however async loading initialization can happen on a separate thread and these functions are not thread-safe. Added locks around access to the Tire Configs array, to ensure it is thread-safe. This should address the fundamental issue causing the crash. Some reports of this crash mention that it was happening specifically while Alt-Tabbed, but this is not conclusive.
Clear Cache to resolve residual issues
If you are experiencing issues, be sure to go to Settings -> “CLEAR CACHE” after updating.