Marcus
Marcus
> OK what I think I'll do is implement #498, #499 and #502 for the next release (bugfix release 3.4.4), keeping this as an optional for the moment (but will...
Hi @nickw1 , thanks for the reply. If it helps at all, [MindAR](https://github.com/hiukim/mind-ar-js) uses aframe as well and it doesn't have this issue.
In the `ar-threex-location-only` file and `aframe-ar` (why both files?), there's this line `navigator.mediaDevices&&navigator.mediaDevices.getUserMedia){const t={video:{width:1280,height:720,facingMode:"environment"}}` that seems to be the issue. It sets the width and height to a specific value......
@nickw1 If I use `videoTexture: false` the problem goes away. But then the cube stretches, so another bug comes up ;_; damn it. Should I create another issue for this...
> with the agreement of @kalwalt, as the world-origin-as-original-GPS-position will be a breaking change It doesn't have to be breaking if it's optional! It can default to false to keep...
> And if the initial position as world origin is the preferred behaviour anyway, maybe it's best to make that the default by switching to that with a 3.5 release....
I simply got the files _ar-threex-location-only_ and _aframe-ar_ from the branch and added to the same folder as the index.html. Like this ``` AR.js A-Frame Location-based const entity = document.querySelector("[gps-new-entity-place]");...
If it helps anything, you can take a look at [this issue](https://github.com/jeeliz/jeelizFaceFilter/issues/292) from another repo. I tried the fix provided there but it didn't work here. Maybe the [JeelizResizer](https://github.com/jeeliz/jeelizFaceFilter/blob/2de003ace85cb2f691a4a2f6694fe67524eafbac/helpers/JeelizResizer.js) and/or...