chaperoneGeometryQuads was converted from an implicit pointer array to a
std::vector because the only thing the pointer array did was hide the
fact that it was an array.
Release log:
https://github.com/ValveSoftware/openvr/releases/tag/v1.9.16
```
Removed sync function. Saving of settings is controlled automatically by
the system now. All existing calls to Sync can be deleted. Calls to sync
using old APIs do nothing.
```
* fixed Chaperone toggle, toggle state on launch
* made update rates based on variable frame rate assuming 90 default
* added overlay color back in
* fixed opacity value not synching
* updated to ovr 1.8.19
* fixed license issue
* rolled back ovr update
* fixed overlay toggle state, formatting, and clamped max opacity to .85%
* removed velocity fade dependent fade.
* changed floating point comparisons
* explicit conversion changes
* removed head speed calculation from overlaycontroller as no longer used
This reverts commit e712f4aa1f.
The issue turned out to be isolated to Linux, since it wasn't possible
to reproduce the issue completely on Windows.
An MVP for the bug can be found here
https://github.com/username223/SteamVR-Manjaro-Sync-Crash
The issue is very likely to be on SteamVR's end, since the issue doesn't
appear on the same CPU running Windows.
The fix for the issue in
https://github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings/issues/252
is to by default turn off the offending feature. This doesn't fix
anything, but it will prevent people from having OVRAS kill their
performance just by running the application.
Having the application call Sync() every frame led to slowdowns on some
4 core CPUs and instant crashes on some older CPUs.
This makes the chaperone velocity modifier only update on every 101st
frame. This might not be the ideal framerate, but having it update every
frame makes the app crash on start for some users.
On Manjaro with a i7-6700K (4 cores) this led to instant crashes of
SteamVR+Steam+OVRAS, with a SEGFAULT in SteamVR.
Issue here:
https://github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings/issues/252
* added arbitrary orientation change
* removed commented code
* updated to OVR 1.4.18
* changed two instances using new to init via array
* moved prox sensor action to haptic instead of Misc
* fixed json file, added prox sensor back for mic mute/un-mute
* added proximity sensor to audio and haptic chaperone warnings
* fixed fall-through behavior
* removed bad prox code
* Test removal of HideWorkingSetPreview for issue #133
* Update WorkingSetPreview on apply reset data for issue #133
* fixed bug to apply floor fix offsets properly
* updated version to 3.0.1
* format
* Prevent space offsets effect on fix floor measurement
* Reorder chaperone commit timing on reset
This is an attempt to smooth apparent ~0.1sec lag on first movement after using a reset.
* Fix space fix tab (todo: reimplement undo button)
* Improve reset function and velocity timing
* fixed PTT checkbox error
* Rewrite of chaperone adjust. Make drift impossible
* Formatting
* fixed mic mute on exit
* format
* Clean up interactions with new chaperone adjust
* Remove commented code
* Implement height toggle action and ui
Them being in the overlay controller required them to be static, which
forces the compiler to give them a memory location at compile time. They
also don't really fit into the overlaycontroller.
Replace magic numbers with constants and centralize settings update counters. Rename actions manifest localization from "en" to "en_US" (Thanks Ykeara)
Parameters with the same name as class members are ripe for introducing
bugs. The fact that the "this->" syntax is optional creates confusion
for maintaining programmers who can only guess at the intention.
Vasily
ykeara
Kung-vr
Kung-vr
Robin Appelman
matzman