This essentially just bakes in all the dependencies and other third
party tools that we need, preventing them from being downloaded on every
new CI run.
TravisCI does not have non-enterprise support for custom images without
a lot of hassle.
* fixed input sending bug not properly releasing keys
* updated to ovr 1.12.5
* added disable oculus api button experimental
* small refactor and fix float and bool bugs
* added nokeyup events to modifier keys when read in, and adjusted token send to have proper logic
* fixed literal held issue
* added backslash
* fixed sender token parser
* updated version string to dev whoops
* added backslash to documentation for keyboard input
* Implement (most of) pop-up notification when autoturn is enabled
* Add neato fading: doesn't appear to impact performance
* formatting
* added macro and UI for notification of auto-turn
* changed notification default to true for auto-turn
* added common issue for trackers
* added warning for custom keys
* minor documentation markdown format fixes
* fix qml syntax error in atgb
* gasd
Co-authored-by: ykeara <ykeara1@gmail.com>
* temporarily disabled adjust chaperone
* added experimental check to prevent rotation drift
* adjusted ss to 2 digits precision
* updated rotation model to be based on relative position and not drift
* fixed force precision error with supersampling
* added Error for turning too fast
* removed error impossible to execute
* fixed and cleaned up some potential failure points
* added inversion check
* re-worded warning
* added adjustchaperone2 defaulted to off to replace adjust chaperone
* moved adjust chaperone to settings removed from offsets tab
* moved adjust chaperone to settings removed from offsets tab
* enabled clipping for settings page no longer scrolls outside of its area
* updated strings for release
Previous way of controlling when controllers were run was split among
the different controllers, meaning that third parties would require
knowledge of internal state of controllers in order to be on the same
update schedule as them.
This refactor moves the logic into a seperate class.
Additionally, it also stops the use of the `adjustUpdateRate` function
on all tab controllers, since it broke the prime-number-ability of
less collisions.
* fixed input sending bug not properly releasing keys
* updated to ovr 1.12.5
* added disable oculus api button experimental
* small refactor and fix float and bool bugs
The old OpenVR overlays did not function for unknown reasons, and it was
not possible to get them to work.
With this a white overlay with ALARM ACTIVATED will be shown for 3 seconds.
It's not pretty, but it effectively communicates that an alarm has been
activated.
This fixes
https://github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings/issues/417
* added two new keyboard press actions
* added todos to overlay controller for new actions
* added settings for keyboard press and default to f10
* added logic, fixed default value
* added action alias
* fixed center marker rotation count
* updated version strings
* fixed Trigger Condition
* removed literal limitation (character input)
* updated version string
* fixed white space issues
* add native chaperone option
* refactored overlaywrapper error handling
* added reset all settings
* added reset all settings option
* clarified driver bounds language
* fixed naming schema of turn settings
* fixed qml issue
* marked errors in settings
* fixed rotation of center marker and cleaned up
* ci test
* removed debugging code
* fixed comment
* fixed rotation.... made messy
* fixed crash when centermarker new was on at launch
* added settings to scroll view
* fixed some initialization issues w/ center marker and some race conditions
* updated Documentation to be more correct/concise about openGL rendering Information issue 457
* changed default behaviour of chaperone bounds to be un-checked to be consistant w/ other settings (default is unchecked)
* cleaned up code around centermarker overlay
* removed unused variables, changed scope of some existing
* code naming cleanup
* more rename
* updated Version strings for 5.1.1 release
* updated string to be more concise
Saving a profile with only visibility changed, the saved struct looks
like
bools\1\bools=false
bools\2\bools=true
bools\3\bools=false
bools\4\bools=false
The load function expects 2 bool values before loading
`includesVisibility`, leading it to getting a false value (actually
includesFadeDistance).
Making the struct save the `chaperoneGeometryQuadsValid` that it expects
to be saved there fixes the issue.
This bug highlights issues with the current object settings system, in
that debugging is unnecessarily tedious and difficult.
Previously logic was duplicated for Linux/Windows.
Additionally, Linux was
```cpp
if ( isModifier( token ) )
{
sendKeyPress( token, KeyStatus::Down, display );
if ( noKeyUp )
{
heldInputs.push_back( token );
}
continue;
}
```
while Windows was
```cpp
if ( isModifier( token ) )
{
inputs.push_back( createInputStruct(
convertToVirtualKeycode( token ), KeyStatus::Down ) );
if ( !noKeyUp )
{
heldInputs.push_back( token );
}
continue;
}
```
(notice difference in noKeyUp if statement which was a bug on Linux.
Windows was the correct version and it has been kept.
* Bump version string to 5.0.1
* ACTUALLY bump version string
* really really fixed version strings
* changed some defaults, and adjusted speed slider slightly, made text a little more intuitive
* see previous
* fixed issue with disabled seated recenter button
Co-authored-by: ykeara <ykeara1@gmail.com>
* Resolve a logic issue for Redirected Walking
* Resolve issue with arc magnitudes being less than expected
* warnings
Co-authored-by: ykeara <ykeara1@gmail.com>
* fixed qml error for input
* fixed settings save bug, fixed rotation direct input, disabled chaperone force floor bounds via profile, made some dialog boxed round @ 2 digits
It is unknown if gcc uses the O3 optimization levels passed to the
compilation of individual cpp files, or if it needs O3 passed to the
linker as well.
The hash of the final binaries are different, thus O3 is passed to the
linker.
Travis clang does not have the LLVMgold plugin installed.
Disabling LTO is easier than installing the plugin since the CI doesn't
create any artifacts anyway.
Qmake attempts to invoke the linker with the default `g++` binary even
when we changed the binary. This will compile error when using LTO.
For clang:
```
/usr/bin/ld.gold: error: /usr/lib/llvm-3.8/bin/../lib/LLVMgold.so: could
not load plugin library: /usr/lib/llvm-3.8/bin/../lib/LLVMgold.so:
cannot open shared object file: No such file or directory
```
For GCC:
```
lto1: fatal error: bytecode stream generated with LTO version 6.0
instead of the expected 4.1
```
Vasily Utkin
ykeara
Chelsea Jaggiandykeara
Ben Scholzen (DASPRiD)