Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generated USDZ files don't work anymore on VisionOS 1.2 beta #4742

Open
3 of 14 tasks
hybridherbst opened this issue Apr 12, 2024 · 5 comments
Open
3 of 14 tasks

Generated USDZ files don't work anymore on VisionOS 1.2 beta #4742

hybridherbst opened this issue Apr 12, 2024 · 5 comments
Labels
flag: not model-viewer Problems that are related to our project but are ultimately some other project's issue

Comments

@hybridherbst
Copy link
Contributor

Description

External issue with VisionOS 1.2 beta, I think worth tracking here as well.
This has been broken before, see #4354, now it's just broken in a different way.

Webkit bug: https://bugs.webkit.org/show_bug.cgi?id=272575
cc @elalish @grorg

Live Demo

Browser Affected

  • Chrome, version: xx.x.xxxx.xx
  • Edge
  • Firefox
  • IE
  • Safari

OS

  • Android
  • iOS
  • Linux
  • MacOS
  • Windows
  • VisionOS

AR

  • WebXR
  • SceneViewer
  • QuickLook
@elalish elalish added the flag: not model-viewer Problems that are related to our project but are ultimately some other project's issue label Apr 12, 2024
@elalish
Copy link
Collaborator

elalish commented Apr 15, 2024

FYI @AdaRoseCannon

@milesgreen
Copy link
Contributor

@hybridherbst - Out of curiosity... have you tried with an untextured model? Either a GLB that has no textures. Or using a ThreeJS primitive with no texture? Wondering what your experience is on VisionOS.

@hybridherbst
Copy link
Contributor Author

hybridherbst commented Apr 18, 2024

Interesting. It might be that the behavior has changed to take the duration of generating the blob into account - so files without textures would be faster? Not sure. Or „rendering to the canvas“ is an interaction cycle boundary now - that would make the click invalid/behave different depending on what has happened between „user clicks button“ and „link is opened by code“.

@milesgreen
Copy link
Contributor

milesgreen commented Apr 18, 2024

Not sure. But per my findings for iOS here #4746 (comment) I have textured models that were smaller in blob size and quicker to generate but failed to open in ARQL on iPhone, compared to some untextured models that were bigger in blob size and took longer to generate but did open in ARQL.

@milesgreen
Copy link
Contributor

milesgreen commented Apr 30, 2024

@hybridherbst - the related issue on iOS has just been fixed with iOS 17.5 beta 4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flag: not model-viewer Problems that are related to our project but are ultimately some other project's issue
Projects
None yet
Development

No branches or pull requests

3 participants