Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add binding modifiers to OpenXR action map #10080

Open
BastiaanOlij opened this issue Jun 30, 2024 · 0 comments
Open

Add binding modifiers to OpenXR action map #10080

BastiaanOlij opened this issue Jun 30, 2024 · 0 comments
Assignees
Labels
Milestone

Comments

@BastiaanOlij
Copy link

Describe the project you are working on

Core support for OpenXR in Godot.

Describe the problem or limitation you are having in your project

The current action map implementation in Godot has a number of missing features that are now available through the OpenXR API. This proposal focuses on adding support for binding modifiers.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

OpenXRs action map attempts to disjoint the actions a user performs within an XR game from the actual inputs performed on the controllers. This in theory allows OpenXR games to be used on platforms for which it has not been designed by creating the appropriate bindings or introduce peripherals the original game was never envisioned to work with.

The missing component here was the inability to make adjustments on these inputs, be it platform specific thresholds, offsets, etc. Especially making sure poses (spatial locations on controllers) line up has been a big missing feature.

OpenXR added the XR_KHR_binding_modification extension for this. This extension is but a foundation on top of which different modifiers can be defined.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

This needs further investigation on how we can best integrate this into Godot. At this point this proposal is just a starting point for the work that needs to be done.

If this enhancement will not be used often, can it be worked around with a few lines of script?

This requires a core implementation.

Is there a reason why this should be core and not an add-on in the asset library?

This requires a core implementation.

@BastiaanOlij BastiaanOlij added this to the 4.x milestone Jun 30, 2024
@BastiaanOlij BastiaanOlij self-assigned this Jun 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant