- Upgrade firmware version 1.255 upgrade#
- Upgrade firmware version 1.255 series#
- Upgrade firmware version 1.255 download#
- Upgrade firmware version 1.255 windows#
Removes dependency on Visual C++ 2010, Visual C++ 2012, Visual C++ 2013 and Visual C++ 2015 Improved voice control threading to handle spurious false voice commands resulting from noisy environments. Improved reliability of file copy to game plugin folders for American Truck Sim, Euro Truck Sim, Kart Racing Pro, rFactor 1.255, rFactor 2, X-Plane 10 and X-Plane 11.
Upgrade firmware version 1.255 download#
Updated installer (setup.exe) that accommodates some changes on the Microsoft download website. This optional feature will close WMR when a VR game that was launched from Sim Commander is closed. It also unnecessarily burns CPU when not in use.
In some cases, WMR won't reset desktop resolution correctly when a VR game is closed.
Upgrade firmware version 1.255 windows#
New ability to kill Windows Mixed Reality when game closes.
This optional feature resolves the issue (by setting the default sound card back to what it was when Sim Commander started) when a game is closed. In many cases, Steam or WMR will change the default sound card to the VR headset when you launch a game but won't change it back when you close the game. New ability to reset default sound card when VR game closes. Improved handling of orphaned Steam library folders. No longer writes iRacing VR ini settings after game closes and 'Stay Connected' option is enabled. No longer edits iRacing ini VR settings when VR headset is set to 'None' in Sim Commander settings GUI Belkin International, Inc. Upgrading the router’s firmware using the TFTP utility.
Upgrade firmware version 1.255 upgrade#
Minor improvements to game record validation and support for iRacing Alpha version Upgrade Firmware Version 1.255 0 Comments Linksys Official Support. Resolves issue with some non-default SimVibe effects causing the profile to restart. IRacing Via Launcher plugin now honors VR mode override settings in CommanderSettings.xml file. Prevents game overlay from loading when user clicks 'Launch in VR' button since it can only overlay on monitors. This will ensure that the new VR launch option gets enabled for users that need it. One-time introduction of new VR functionality on main screen since many users don't read release notes.
RFactor 2 now launches into mirrored VR mode when user clicks 'Launch in VR' SimVibe now attempts to recover from some games and VR utilities erroneously wiping the SimVibe sound card buffersįix It! button is now visible even if profile image size is set to the smallest setting
Upgrade firmware version 1.255 series#
Improved effect slider labels for G-Belt, GS-4, GS-5 and Stage Series Motion (more to come) Minor bug fixes with reset Commander to defaults functionĬorrected path issue with rFactor 1 Steam versionĬorrected false detection of MSFS 2020 on some systems New ability to control speech volume ( more here) New ability to auto-switch VR audio device ( more here) Single-click VR experiences for games that support it ( more here) Also have tried the latest beta BIOS as a last ditch attempt.New game record validation/warning system ( more here) Have now tried to downgrade BIOS to 0801 but no joy at all, the damage has been done. I'm also not happy about having to teardown my system to remove the Motherboard. I could arrange a courier or postal return but this will take several days. This is a pain as I live in a Regional area and the store I purchased the Motherboard is a fair distance away so if I wish to return the Motherboard I will need to take a whole day off to do so. I'm going to arrange an RMA return to ASUS via my supplier. My System still works fine once booted but No AURA Lighting Effects and takes 30 minutes to boot. Note: This is not any official procedure and is done at your own risk You can also try updating to this firmware: !Atmpv-6qHr_6o5VHvIdLs5KJpiPC8Q Can someone with this error run this tool (cmd or power shell as administrator), save their firmware and send it to me for debug?
0 kommentar(er)
