Version: Any 2020 / 2024 version (aircraft interior gltf is built using 2020 exporter).
**
Bug description:** As our dev team is primarily NON-VR users (only one of us has VR goggles and they sit mostly unused) it took awhile for us to notice this issue and we did only after a couple customers reported it, but… for them, it renders the sim unplayable really.
In essence, what we’ve noticed is that in VR mode, the controller clickspots (especially on the overhead panel) in the aircraft stop a few centimeters in front of the actual buttons / knobs they’re supposed to click, so the user can’t actually hit them unless moving the virtual “hand” very very close to the panel itself - the beam pointer stops a few centimeters before the actual click spot in most cases.
I am not quite sure how to showcase this with a screenshot, but hopefully the Asobo dev team might have an idea how to guide us for a more complete report or a repro case.
Hello @simfan
I’m tagging the topic as obsolete as we didn’t hear from you since our last PM.
Feel free to ping me via PM with a working repro package to test.
Thanks for the feedback !
Collision meshes are used in VR to detect mouse interactions where it’s needed. I think that is why you were seeing this behavior.
From the documentation it must be exported with the interior playable LOD (usually LOD0)
I think the da62 sdk .max or .blender will give you a good example of how it should be.
