Large Model Failures / Max size limit? #4925
Unanswered
andres-echo
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Wow, I'm impressed the browser will render a 2GB file for you! Might be a GPU RAM limit, but more likely a browser JS limit. I'm sure there is one, though I don't know what it is - looks like you found it. Are you using KTX2 textures yet? That can help keep the memory footprint down. Beyond that, you may want to look at what e.g. Cesium does for breaking large scenes into LoD tiles and loading and unloading them dynamically as you move around. That's a bit beyond what MV is designed for. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to use model viewer to render large GLBs (1GB ~ 4GB) within a browser javascript application. GLBs smaller than 2GB load fine but anything larger does not. I can confirm the device has more than enough memory (desktop PC) and the network tab shows the file being streamed and downloaded successfully (I am on ethernet so even a 4GB file streams in about a minute). There are no errors in the console, the progress bar for the viewer loads and fills but once done, the model does not. Is there a known limit to the size of GLBs that can be rendered within a browser? (Latest Chrome, W11).
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions