Version 2.0748 includes the following improvements:

- Added ability to import a custom carrier mesh for single player (see customizing kit).
- Added option to map an input for mouse button 2 on VR controllers (see vrsetup-bak.txt).
- Flight control button mappings in VR are now bypassed entirely when point mode is active.
- Only operational VR controller in point mode will show laser pointer to prevent confusion.
- Control conflict alerts (yellow) added for duplicate axis channel mapping with matching button mappings.
- Control input system updated in an effort for improved device enumeration.
- Automatic waypoint plotting system updated for Thuban to Capella route.
- External library dependencies merged into game's object code file.
- IDS 'Off' mode toggle now supports Alt-Spacebar to re-enable.
- Minor improvements and fixes.


Notes:

Control Input System Changes - The input system has been updated to improve device identification, reduce certain non-gaming related devices (mouse, keyboard, etc) from occasionally being queued, and expand conflict detection to include alerts for simultaneous mapping across axis channels and buttons. If an axis channel is mapped to a control that is also linked to an axis input for a button function, the conflict will now be indicated with yellow in the key/button mapping menu. The input device testing utility has also been updated to incorporate the improvements associated with device listing/identification, available for download here: https://www.starwraith.com/evochronlegacy/JoystickTest-Advanced.zip


Changes to Libraries - In an effort to meet the requirements/limitations of some antivirus programs, several of the game's dependencies have been merged internally. While this will be fine on Windows platforms, this may have an impact for anyone trying to run the game on an incompatible/unsupported Linux environment with an older Proton version (such required dependencies are one of several reasons native builds aren't feasible). While later versions of Proton may work fine with this arrangement on compatible systems, significantly older versions may not. So updating the Proton version in Steam's compatibility settings may be needed for the game to attempt to launch. Otherwise, an error message like 'Failed to load plugin 'AGKVR' required by this app' may appear when the operating environment is not able to properly provide a dependent resource the game requires. Other 'Experimental' versions might display a message about a path not being found, simply pressing enter or clicking on 'OK' should allow things to launch and run. Even though Linux/Proton is not supported, I ran tests with currently listed versions 7.0-6, 8.0-5, and 9.0-4 through Steam to verify those versions would continue to work with the game like before.