Version: Flighting SU13 - 188.8.131.52
Context: Issue only in VR, found in A2A PA24, Flysimware 414, possibly other addon aircraft too.
We’re currently investigating an issue with SU13 beta that made the tablet screen unclickable in VR. I replaced our HTML gauge with MouseWasmModule.wasm copied straight from SDK samples, and both show the same problem. The gauge does not receive any mouse related events. You can see in a screenshot below that the the white circle driven by
MouseInformation_mouse_callback is not updated. The mouse_callback is not called, neither with mouse movement nor with mouse clicks. Interestingly, the red circle, which is driven by
sGaugeDrawData passed in PANEL_SERVICE_PRE_DRAW callback, is correctly shown over the cursor. This data is updated every frame as expected.
Also the cursor does not display on the gauge plane, but “falls behind” and is aligned to the horizontal dashboard surface behind the gauge.
The same gauge works fine when assigned to a different gauge texture in the cockpit. Only the tablet texture is affected. Which suggests it’s some issue related to the object or the materials, but so far we were unable to find the exact cause. Even creating a new mesh without animations does not help, or copying the material settings from a working gauge element.
SU13 release notes mention changes to handling click interactions in VR. The same model works fine in SU12 so it looks like it’s a regression with SU13.