I just updated to PTC v56, and as per the instructions in the recent PTC
v56 Un-Megathread request by the Community Manager, I am posting this to
its own thread with the PTC Tags. I can report that there has been no
perceivable change in the ongoing ...
Thanks also for this update @Ryanality . I think testing the issue in
early builds is an excellent step to take, and I'd like to specifically
mention the previous workaround/test that could be performed in v54,
where the issue was not present on the ...
We have been able to reduce the Pixel Artifact issue in our own
immersive video app to around 95% elimination on the Quest 2. This is
not a fix however, but rather an application specific workaround to
circumvent it.As many have clearly determined, t...
I would just like to add in to the current conversation, in order to
refresh key information for others that has come before, that just after
the initial period when this issue was introduced in v53 there was a
strange workaround in v54... which I be...
Thank you Ryan, I strongly recommend to you that the Engineering team
look at video decoding applications that uses h.264/h.265 , as the pixel
artifact issue appears much more acute in these types of performance
demands. These include Virtual Desktop...
@cgwu Just a suggestion, but if you can still access the device settings
on the phone app, then you could join the PTC channel in Advanced
Settings. The when the next PTC update occurs (likely now PTC v59) it
will install new firmware sooner. If that...
