1376721 - Space Harrier WebVR Three.js demo works in Firefox 54 Release channel (without VR display), but not Beta or Nightly 54

Status: RESOLVED INCOMPLETE

(Core :: WebVR, defect, P4)

Description

[Chris Peterson [:cpeterson]]

STR:
1. Load https://dlittle42.github.io/machinecode/examples/spaceharrier_vr/index7.html

RESULT:
The game demo loads in Chrome and Firefox 54 Release channel (without VR hardware), but just shows a magenta page with a black rectangle in Firefox Beta and Nightly builds, including Beta and Nightly 54! Thus I was not able to find a regression point using mozregression.

I see the following JavaScript error in the devtools console because navigator.getVRDisplays() doesn't report any VR displays:

TypeError: hmd is null. webvr-manager.js:353:30

Comment 1

[:kip (Kearwood Gilbert)]

I have reproduced this in the current Nightly.  Disabling WebVR with dom.vr.enabled allows it to run normally on Nightly.  We are hitting a code path on the site unique to having the WebVR API available, but no HMDs attached.

Perhaps the issue could be solved by updating webvr-manager.js and/or the threejs vreffect.js on the site?

Comment 2

[Chris Peterson [:cpeterson]]

I filed a bug on the game's GitHub repo: https://github.com/dlittle42/machinecode/issues/1

Comment 3

[thomasmo]

The link above (https://dlittle42.github.io/machinecode/examples/spaceharrier_vr/index7.html) shows the same magenta page and the same script errors across FF64, CH71, and Edge32:

Uncaught ReferenceError: PNLTRI is not defined
at index7.html:199
at index7.html:220
index7.html:285 Uncaught TypeError: THREE.ConvexObjectBreaker is not a constructor
at index7.html:285

I tried with and without a headset in FF and Edge.

:cpeterson, can you confirm if this bug should be still active? And, if so, where/how i can repro?

Thanks!

Comment 4

[Chris Peterson [:cpeterson]]

(In reply to thomasmo from comment #3)

The link above (https://dlittle42.github.io/machinecode/examples/spaceharrier_vr/index7.html) shows the same magenta page and the same script errors across FF64, CH71, and Edge32:

I see the same behavior and errors in all browser I tested, so I'll close this bug.

Comment 5

[thomasmo]

Thanks for confirming!