1. XSOverlay
  2. News
  3. Build 384 Changelog

Build 384 Changelog

[h3]CHANGES[/h3]
  • Changed: Clamped "Window Curve Bias" to a minimum of 0.1

  • Added: Small animation to desktop window to ensure that users put on the headset to see the overlay.

  • Added: New Settings Tab "Experimental." This tab will contain experimental settings, and a description of what each one does. The settings in this tab will eventually graduate out of the experimental tab and moved to an appropriate section when deemed to be stable and non breaking.

  • Added: Force Higher Quality Overlay Rendering option to the "Experimental" tab in Settings.

  • Added: Input Blocking option to the "Experimental" tab in Settings.

  • Added: New contextual tutorial. This will only play once, and is aimed to help new and old users alike, as it will intuitively guide you through how to use the basic functions of the overlay.

  • Added: "Allow Movement" toggle to the "Wrist" tab in the Settings menu. This allows you to turn off the ability to grab and move the wrist.

  • Added: Plugin front-end. This is not currently accessible to the end user, and will be expanded in the future.


[h3]BUGFIXES[/h3]
  • Fixed: Keyboard Left Ctrl / Right Control are now separated properly and recognized as different inputs.

  • Fixed: Keyboard Left Shift / Right Shift are now separated properly and recognized as different inputs.

  • Fixed: Keyboard Left Alt / Right Alt are now separated properly and recognized as different inputs. (Notes: Windows currently treats AltGR on keyboard layouts such as the UK layout, or Polish layout as 'Ctrl + Alt' - As such, when pressing the right alt key and using one of these layouts, you will see the Ctrl key light up. You can ignore this, it is functioning as Windows intends for it to function. I will look into solutions to stop the UI from exposing this side of Windows in the future.)

  • Fixed: UI elements on the Window Options panel should no longer have edges that look weird due to transparency.

  • Fixed: Resolved a very specific scenario that caused settings to be loaded incorrectly. (This is possibly a fix for Keyboard Layouts loading incorrectly or not at, in the same scenario.)
Show Changes