Hey @flatKAT!
We’re aware of issues using the Valve Index Grip Axis input as an input for an Action Mapping. If you assign Valve Index Grip Axis input to an Axis Mapping, it works as intended. The reason why that’s not default in the VR Template is due to how we’d prefer to have the same Action Mapping be responsible for the same logic path, as that’s how input w. OpenXR is intended.
I’m working w. the team to figure out if the issue is w. the runtime, the generated action manifest, or our Input Mappings. For now you can modify your grip logic to be triggered off of an Axis Mapping instead of Action, and it’ll work as you’d expect. Hope that helps!