Instruments of Destruction

Shadow-dropped at Twitch Galaxies, we’ve announced that our physics-based vehicle destruction game Instruments of Destruction is now available on PS5 and Xbox Series X|S, to join our Steam version! Get behind the controls of over 130 wild and wondrous machines, causing total mayhem and levelling islands in mind-bogglingly glorious chaotic action. To celebrate, we’ve released an explosive new trailer. Check it out: Take on over 50 campaign missions and get to grips with your instruments, then revisit these maps in Challenge Mode with new vehicles and harder objectives. Or go your own way, trying out the Build & Destroy campaign with 25 new missions before editing and building your own vehicles for endless destructive fun in the Sandbox. However you prefer to enjoy Instruments of Destruction, we invite you to join us in the official Discord server where you can meet other players, ask questions and share your creations.

Some more minor fixes coming over from the console version porting process: Added "EARTHQUAKE!" to the screen when there's an earthquake Fixed a few more 60hz physics issues Fixed a bug where some logic was processing while the game was paused (making vehicles go wonky after you paused) Fixed some minor localization issues (mission labels being the most obvious one) Made water depth no longer update during Kraken fail sequence (speeds it up, saves a lot of memory) Fixed Dragonfly Alpha shooting itself with some hidden lasers Fixed a 2nd vehicle loading and making things weird if you went to build mode on 3-2/etc After you reset progress, it should now be reset when you restart the game Forced a couple non-mission islands far off the map if you use the unlock-all-missions cheat Fixed Total Destruction achievement so it doesn't trigger by skipping a mission Improved outline object cleanup so reloading a level doesn't increase memory usage by nearly as much as it used to Made vehicle parts get added to the Recent list in more cases If you skip a mission, the game now remembers that so some islands don't be re-locked when you restart the game

A long list of stuff, though much of it gamepad-related in preparation for console release, improved playability of some of the more annoying missions, and made 60hz physics more fair: Fixed Remap Controls shows controller buttons, and they are a bit blurry (only fix if it's easy) Fixed "DO NOT DESTROY" objective text is not translated (m9-4) Fixed text in multiple areas of Build & Destroy are not translated to its supported languages. Fixed gamepad icons during the build section text width Fixed B key glyph rather than the B button controller glyph showing on custom vehicles Made Flip/Swap Vehicle prompts flash when you push the corresponding input Fixed pause menu default gamepad selection being incorrect Updated options menu to show LB/RB and LT/RT for swapping menus and scrolling respectively Fixed issue with B&D Reset All Instructions not working for gamepad Added potential null-crash fix for EntityOutline crash (m4-4 killing outlined car corpses) Made plants kill themselves a lot faster in player collisions, and they also have 50% less mass. Fixed “Show Controls” option still showing text for the controls Fixed Build Mode Settings buttons being all mess

It's been a few months since version 1.12 and subsequent patches were released. Today, version 1.13 fixes the biggest issues caused by that update along with a few other minor tweaks/fixes. Let's get to the changelist first, then I'll go over the exit-freeze issue and the journey to fix it, and finish up with some other news.1.13 CHANGELISTRebranched code from 1.11d to prevent exit-freezeReintegrated all 1.12 changes into new branchAdded new cheat to unlock all missionsFixed dropship sequence going too fast and causing issues when framerate was lowChanged a couple gamepad shortcuts a bitGrayed out vehicle slots that have nothing when in Load Custom Vehicle menuRemoved some excessive debug.log statementsPrevent GPU from trying to release resources twice on shutdownTHE EXIT-FREEZE MYSTERYAs you can see from the the first item, the solution to the exit freeze was relatively simple in the end, though it took a very long time to figure out. And to be honest, I'm not actually sure what code caused the exit freeze, I just know roughly where the freeze came from.The exit-freeze was first reported in May after 1.12 (or one if it's follow-up patches) released, and I