So something else has changed, going to try console.log for every line and taking a screenshot of the values to see what changed
by user 103054507105067008
So something else has changed, going to try console.log for every line and taking a screenshot of the values to see what changed
by user 103054507105067008
Found another error actually: this is obviously wrong and should be 0
then screenpoint works without any other changes
I’ll also add a debug flag ?debugscreenpointtoray
to easily visualize the rays produced in the future
thanks for reporting - when fixing the domx and domy it works both on android, mozilla XR and desktop again
I will see if I can make that change locally here to test also, gives me peace of mind for updating the engine in my AR template project now!
by user 103054507105067008
Thanks
by user 103054507105067008
Yea sure the code is in engine_setup line ~137
So I just change both those lines to return 0 for this._domX and this._domY?
by user 103054507105067008
change to this
Confirmed that fixes it, thankyou! Just going to update to 2.52.0-pre and also try the built in method for screenPointToRay
to check if that works so I can ditch my local version
by user 103054507105067008
That does! Wooooo
by user 103054507105067008
The change is not published tho - next release
So 53 will have it
Just going to check if anything else breaks in 52, I’m sure not though
by user 103054507105067008
All good with 2.52 using that fix from above, excited to use 2.53 when it drops!
by user 103054507105067008