Quicklook ar placement

[pixlhero]

Fixes #3989

Also had to fix the boom_2_.glb model because the model was offset quite a lot, which messed with the rotation required for quicklook AR.

I tried a few different approaches to reset the rotation of the model (like keeping a copy of the matrix). Only rotating it back worked for me though.

[elalish]

Thank you! Probably a good idea to test with several different off-origin models to ensure the transformations are consistent between WebXR and QuickLook.

[elalish]

Let's not update the GLB; it's a good test precisely because many models are not aligned to the origin. I believe you'll need to also apply the scene.target translation to make it work.

[elalish]

It sounds like USDZ may have particular assumptions about where the origin should be relative to the placement point, so you may also need to make use of $scene.boundingBox to find the translation you need.

[vincentfretin]

Instead of (-90 * Math.PI) / 180 we can use -Math.PI / 2 here.

Also we have the same auto rotation issue with alignment "any" (https://developer.apple.com/documentation/realitykit/uniform-token-preliminary-planeanchoring-alignment), so maybe doing usdzOptions.ar.planeAnchoring.alignment !== 'horizontal' would be better.

[elalish]

Would you like to take over this PR or make your own version?

[vincentfretin]

I didn't understand what you were suggesting in the comments above with the translation and bounding box, and also every time I tried to do threejs operation like that translation followed by rotation I always do things wrong and lose my hairs, so I probably can't do any change related to that.
But not sure if we should go this way if removing the lines https://github.com/mrdoob/three.js/blob/aaafb4ffe8830932e31aa44003376457265d126a/examples/jsm/exporters/USDZExporter.js#L209-L210 also fixes the issue.

[vincentfretin]

related comment #3989 (comment)

[elalish]

@pixlhero Ping - are you planning to come back to this?

[pixlhero]

@pixlhero Ping - are you planning to come back to this?

Not in the near future unfortunately. We worked around this issue by just not placing it on the wall in our project. So until I have some spare time between projects I won't be able to work on this.

[h36ahmed]

@pixlhero - has this been fixed or still being worked on?

[ekokotov]

any news how to enable vertical placement on IOS Quicklook?

[elalish]

If anyone would like to take over this PR, it would be great to merge it. I may get to it eventually, but not sure when.

[pixlhero]

Sorry about turning silent on this PR. I think I might be able to come back to this during next month. Probably not in the next two weeks though, but I put it in my calendar.

[elalish]

Thanks!

[pixlhero]

Working on this now 🚀

[elalish]

Thanks! Let me know if you have any questions.

[vincentfretin]

I tested the changes here with model-viewer 3.4.0, it works fine for my models.
But it seems we have an issue when auto-rotate attribute is used on model-viewer tag, the usdz generated has a different y rotation each time we generate the usdz, and after the 90° rotation here it gives really weird results. The bounding box seems wrong and will result of bad snapping on the wall, the shadow is ok but the model is not correctly on the wall.