Oculus Go pixel size is too large in VR mode

[tlaukkan]

A-Frame has larger pixels in VR mode than that of native resolution i.e. is the pixels are at least 3-4 times too big.

• A-Frame Version: aframe@cb4de2e19 (Latest master at time of reporting)
• Platform / Device: Oculus Go
• Reproducible Code Snippet or URL: Any scene viewed with Oculus Go

A-Frame master based scenes and examples at A-Frame site run with too large pixel size in all Oculus Go browsers:

• https://aframe.io/aframe/examples/boilerplate/hello-world/

Three.js examples run with correct resolution with Oculus Browser (did not test other browsers.):

• https://threejs.org/examples/#webvr_ballshooter

This could possibly be some problem with setting the canvas width/height when initializing VR mode.
Setting to scene renderer maxCanvasWidth and maxCanvasHeight to -1 does not have effect. Setting antialiasing to true alleviates the problem somewhat but the jagged edges and large pixels are still clearly visible.

I could tweak the display settings in firefox reality to get the content look quite ok when looked in normal browser mode but when entering VR mode the situation remains the same i.e. too large pixel size.

It looks like this was earlier reported but closed after reporter was happy after setting antialiasing=true which does address the root cause of pixel size:

#3571

[dmarcos]

I have no Oculus Go to test at the moment. Is there a way to retrieve the canvas size when in VR mode?

[tlaukkan]

I am not sure. I could checkout master, add some debug log output and use firefox reality remote debugging which I hope gives access to console log.

[tlaukkan]

Evaluated in Oculus Go / Oculus Browse console using chrome remote debugging as requested by @dmarcos
AFRAME.scenes[0].renderer.getSize();

{width: 2048, height: 1024}

Native resolution of Oculus Go is: 2560 x 1440

This image illustrates how the pixels look in VR mode all though its screen captured in normal browser mode (the pixel size is similar):

[tlaukkan]

Commenting out of this code did not have effect on the pixel size:
https://github.com/aframevr/aframe/blob/master/src/core/scene/a-scene.js#L514-L541

[IvoJager]

@tlaukkan
Hi,

Have you tried adding to your a-scene;

renderer="antialias:true"

Adding the above on my Oculus Go helped.

It appears that antialias="true" has been removed and no longer works.

[dmarcos]

Thanks for investigating @IvoJager

[dmarcos]

@tlaukkan Can you confirm if antialias is working for you?

[tlaukkan]

I have that on but it only alleviates the problem as it hides some of the pixelation. However the pixel size is still too large.

[arpu]

looks like aframe should use the meta data like the model-viewer do it ?
but no idea why three samples works and aframe not :/

https://github.com/GoogleWebComponents/model-viewer/blob/master/src/utils.js#L114

setting it here https://github.com/aframevr/aframe/blob/master/src/core/scene/a-scene.js#L581

[IvoJager]

I can confirm that, on Oculus Go, turning anti-aliasing off results in much chunkier rendering of the outline of geometry than might reasonably be expected. Yet textures remain smooth. Anti-aliasing turned seems to fix geometry outline issue completely though (as far as I can discern).

I'm not sure if related, but text - regardless of anti-aliasing on/off - turns into a shimmering mess quite quickly at a distance (the same scene and text looks buttery smooth on a WMR headset).

Similarly a forced non-power-of-two texture exhibits the same sort of shimmering that I cannot replicate on other devices/headsets.

I'm not sure if it's the capabilities of the hardware either; I have a Mi5 here with the same SoC and it renders everything just brilliantly w/AFrame.

[tlaukkan]

Anti-aliasing smooths the color difference between adjacent pixels but does not affect he pixel size itself.

[IvoJager]

It's not supposed to, no :) However I think what you and I are seeing in our Oculus Go units, is that without anti-aliasing pixel size seems to be much bigger than AA can account for. Correct me if I'm wrong?

[dmarcos]

Mmhh. Thanks for the patience. Resolution looks good to me (antialias aside) on hello-world and Anime UI on the Oculus Browser. Do you have a link where I can reproduce the problem?