* 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
* updated documentation/screenshots, let seated-recenter show in all modes, fixed default value of brigthness
* fixed formatting
* changed PTT to System
* added comma to documentation
Initial implementation of Auto-Turn
Auto-turn leverages Space Turn automatically whenever you reach a configured distance from your chaperone boundary. Turn direction is in order of precedence:
1. Away from a corner where you're already touching one wall. This is to avoid being turned to face a wall, which we pretty much never want. If 'use corner angle' is enabled, it'll turn the angle of the corner, otherwise it'll turn the angle of your headset to the wall you encountered.
2. In whichever direction will start you unwinding your cord. If your rotations is greater than 'cord detangling rotations' and your angle to the wall is less than 'min detangling angle' it'll turn you such that the thing you're walking towards is directly along a wall, in the direction which will begin unwinding your cord.
3. In the closest angle to the wall. This too will put whatever you're walking towards directly along a wall, so you can walk the maximum distance to it.
- If Smooth turn is checked, it'll turn at a constant (configurable) rate until the world is aligned with the new angle, otherwise it'll snap to the new direction instantly.
- Activation distance is the distance from your chaperone at which auto-turn starts, and deactivation distance is the minimum distance (+ the activation distance) at which it'll be able to be activated again, to avoid turning twice at once.
Redirected walking tries to gently guide you away from your playspace boundaries by tweaking the world's angle at smaller increments than your brain is capable of noticing. While most playspaces won't be big enough to allow this to give you a true 'infinite walk' experience, it can give the perception of your playspace being ever so slightly bigger by making you walk in a slight arc in real life while walking forward in VR.
- Redirected walking is independent from Auto-turn and can be activated on its own. At both the 'slight' and 'imperceptable' radii, the turning speed is incredibly minimal. When walking along one wall of your chaperone to another, you should notice the far corner of your playspace (relative to the world) drifting ever so slightly away from you. In normal circumstances at the lowest settings this shouldn't be noticable.
Co-authored-by: feilen <feilen1000@gmail.com>
* Initial implementation of Infinite Walk
* Code cleanup and abstraction, use nearest corner instead of nearest wall to determine turn direction
* Run clang-format
* Turn relative to the last wall if we run into adjacent walls, otherwise turn at easiest angle
* Limit maximum turns (just refuse to turn for now), only turn on shared corners if going the same direction
* Improve same-corner
* get rid of LastDirectionLeft
* WIP: cord untangling hint
* Try to automatically untangle cord, don't rotate if we encounter a wall behind us
* Incorrect offset for walls
* optimize if hmd inactive
* Cleanup/clarify angles
* (probably?) solve rare segfault
* Adjust the defaults and fix a bug with blocking reverse turns
* Implement smooth turn, fix a bug with shared-corners that would cause it to turn the wrong way
* actually really fix shared corner bug
vect[i + 1 % vect.size()] was somehow evaluating to vect[i + (1 %
vect.size())]
* Move configurables for autoturn to .h to make clearer what's configurable
* WIP: true redirected walking
* First pass optimization/cleanup
* Second pass cleanup/optimize
* Missing clang-format
* Somewhat ugly: Optionally turn the exact angle of the corner when using shared corner turns
* added rotation tab controller in progress
* cleaned up chaperone controller/ finished settings/rotationtab
* did first 4 settings qml, and main qml setup
* initial working build, not all settings UI done
* merging master into redirected walking. (#387)
* Update OVR to 1.10.30 (#379)
* updated to ovr 1.10.30
* fixed updated showoverlaykeyboard call
* fixed keyboard location
* Updated Manifest (#380)
* updated to ovr 1.10.30
* fixed updated showoverlaykeyboard call
* fixed keyboard location
* removed un-necessary matrix, updated app key and manifest
* fixed formatting
* Fix push to mute icon not being used when PTM enabled
* added touch default bindings (#385)
travis CI down/broken?
Co-authored-by: Vasily <vautkin@teknik.io>
* added action, and additional settings
* fixed various bugs added turn speed and mode
* fixed conversion error for turn speed
* added redirected walking options
* formatting
* formatting fixing
* removed old comments
* changed logs to debug and some wording changes
* changed UI layout
* added space turn to rotation page
* added icon, fixed autoturn to autoTurn, fixed conversion to be in qml vs set
* Update src/res/qml/RootPage.qml
yep XD
Co-Authored-By: Kung-vr <38249782+Kung-vr@users.noreply.github.com>
* reverted build changes
* removed un-needed app image build commands
* Cleanup some functions, avoid an extra chaperone check.
* Make redirected walking and autoturn independently enable-able
Co-authored-by: Feilen <feilen1000@gmail.com>
Co-authored-by: Vasily <vautkin@teknik.io>
Co-authored-by: Kung-vr <38249782+Kung-vr@users.noreply.github.com>
Source outputs must all be moved to new default source.
Reference topic
https://askubuntu.com/a/72076
* Adds microphone controls on Linux via PulseAudio (PA) for several
points in
https://github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings/issues/43.
It can not be overstated how unsuited the public AudioManager API is for
using the PA API.
It can also not be overstated how undocumented and horrible the PA API
is. The PA way of doing audio is very unlike the Windows way of doing
audio, which the AudioManager is heavily influenced by.
Since I don't have a Linux machine I have not been able to personally
test this. https://github.com/feilen/ has graciously helped with
testing.
PulseAudio is very undocumented and not very widely used for what we
need outside of official utilities. As such there's most likely a better
way of doing things than I've done.
Additional information can be found at
https://github.com/username223/pulseaudio-device-changing.
The "complex" PA API is asynchronous. Since our current AudioManager is
running synchronously and would not work asynchronously (functions are
expected to return valid data on function return) it is necessary to
massage the PA API until it runs synchronously.
This is done with a general workflow of
1. Register a callback function (`pa_context_get_source_info_list()`,
for example).
2. Run the PA loop through `customPulseLoop()`. This will trigger
any registered callbacks. Sometimes a `void*` is passed through the
callback that can be used for custom data. `successCallback()` uses
this to set the success variable.
3. Run the callback function and do required work.
4. Return to original function, do work or return values.
It is not possible to run a `customPulseLoop()` inside of an already
running loop (inside a callback), as this will lead to a PA assert
error on runtime.
* fixed audio override key unset issues
* Add apt-transport-https to CircleCI config
CircleCI fails with
E: The method driver /usr/lib/apt/methods/https could not be found.
when attempting to get the LLVM key.
This is suspected to happen because of an update to the image.
Co-authored-by: Vasily <vautkin@teknik.io>
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.
Chelsea Jaggiandykeara
Ben Scholzen (DASPRiD)
Vasily
