Depth is reversed when first loading page

[lakmeer]

I have a simple threejs scene with a single cube and some moving lights. However, this issue is also apparent when viewing the tutorial scene.

When I first load the page, the depth effect is reversed. That is, near objects seem far, and far objects seem near, as if I was looking at a stereograpic image with the eyes swapped over. Further, if I lean left, I see the part of the quilt showing right-hand side of my cube, and vice-versa.

Strangely, if I use the Holoplay fullscreen button, or F11 to fullscreen the browser itself, or change the window size in any way, it corrects itself. Even if I return the window size to what it was before, it remains correct. However, if I refresh the page, it becomes wrong again. It is very confusing :sweat_smile:

System:

• 8.9" dev kit
• Windows 7
• Chrome 80
• Web drivers v1.2.0
• holoplay.js v0.2.3 (according to comments in source)

[lakmeer]

I've got a workaround for myself that might be useful; I added the following function to Holoplay.js:

    function fixShaderValues (backoff) {
      if (typeof backoff === 'undefined') backoff = 1;

      // Exponential backoff
      if (!jsonObj) {
        console.log("HoloPlay::fixShaderValues - calibration not ready, retrying in " + backoff + "ms.");
        setTimeout(function () { fixShaderValues(backoff * 10) }, backoff);
      } else {
        setShaderValues(
          jsonObj.DPI.value, 
          jsonObj.pitch.value, 
          jsonObj.slope.value, 
          jsonObj.screenH.value, 
          jsonObj.screenW.value, 
          jsonObj.center.value, 
          jsonObj.flipImageX.value, 
          jsonObj.flipImageY.value, 
          jsonObj.invView.value);
        console.log("HoloPlay::fixShaderValues - calibration reapplied");
      }
    }

I made this function available on the HoloPlay prototype, so I can call it from my threejs setup code. This works well, so perhaps this code will be helpful in making a more robust solution to the problem :)

[alxdncn]

Hi, thanks for delving into this! This will be fixed in an upcoming release, v1.0.0. It will be live later this month.