Wolvic VR browser uses KTX textures to create an OpenXR cubemap layer.
They have been working fine until v68 but the v69 PTC upgrade broke them
and they are not displayed anymore. We have tested several combinations
of cubemap layers and texture form...
The specs clearly state that:If the returned isActive is true, the
runtime must return all joint locations with
bothXR_SPACE_LOCATION_POSITION_VALID_BIT and
XR_SPACE_LOCATION_ORIENTATION_VALID_BIT set. Although, inthis case, some
joint space location...
This release brought an important regression that severely affect
Wolvic. As it can be seen [in this
comment](https://github.com/Igalia/wolvic/issues/1631#issuecomment-2491121254),
our main thread gets stuck on a `dequeueBuffer` call as soon as the
b...
Same issue
https://communityforums.atmeta.com/t5/Get-Help/PTC-V69-broke-OpenXR-support-for-GL-COMPRESSED-SRGB8-ETC2-KTX/m-p/1237621?search-action-id=61220200085&search-result-uid=1237621
BTW after the upgrade to v66 most of the flickering is gone. At least
the whole display does no longer switch off and on for seconds. But I
said "most of" because there is still some flickering in the browser
window when a video is shown. Much less d...
In the Wolvic browser we detect that gesture when we stop getting valid
values for aim. For devices not using the FB aim extension we do use the
data from the hand joints to detect that. We haven't found a better way
to do that.
We have been observing similar issues in the Wolvic browser when playing
video not only mp4 but also VP9 for example. The whole screen flickers
or gets pitch black. As soon as the user moves away from the web page
with the video the problems vanish. ...
