Skip to content

vive trigger/axes processing prevents continuous values #22

@grrrwaaa

Description

@grrrwaaa

The way the trigger and axis handling is done in the openvr binding captures an instantaneous value, rather than the current actual value of the trigger/axis; setTriggerValue() is only called if the trigger touch state changes. This doesn't match how the oculus binding is done, where setTriggerValue() is called every time.

More importantly it doesn't allow a continuous sampling of the trigger or axis state, which is weird.

(Also, the difference between touch and press events is not captured by the Cinder-VR binding at the moment.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions