-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
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
Incremental loading and non-blocking parsing and rendering #4397
Comments
I've experienced similar problems when loading large models. I would guess that the most important optimization would be to reduce the amount of preprocessing done internally in three.js, see #4386 |
In http://Clara.io we use binary objects (like glTF and Sketchfab.com do) to reduce the need to do JSON parsing of large objects. JSON-based 3D meshes is good for debugging and prototypes, but it isn't a production solution. Funny thing, Sketchfab and glTF are nearly the same format arrived at independently I believe. |
Is there a way to use a BufferGeometry with the JSON format or binary format until #4386 will be implemented? |
Yes. You can use BufferGeometryLoader and BufferGeometryExporter. |
@mrdoob Does the export include materials and textures? |
There is a MaterialExporter. You can use ObjectExporter with your mesh. Makes sure the geometry is using All these exporters is what the editor uses. So you should be able to figure out how to use it by looking at the code.
Nope... Maybe you can write a node.js script for that? |
we had good results with the ctm loader back last year, how it uses a worker for non- / less blocking loading too. have been testing with gltf now, looks good so far. |
Some updates since this bug was last opened:
Closing this issue, as there is more recent discussion in #11746. |
Hi,
I have large models > 20MB which blocks the browser when parsing and rendering them for several minutes.
In my case the 3D viewer is only part of the app and models are loaded in the middle of a session so showing a progressbar is not enough.
What part is the most expensive?
Are there plans to improve the browser responsiveness when loading large models?
Or maybe I'm missing existing features?
Some thoughts:
I'm not sure if IE11 support this feature but FF and Chrome do. (pdf.js uses this technique).
Progressive loading of PDFs
mozilla/pdf.js#2719
Worker with transferable objects
mozilla/pdf.js#3904
http://updates.html5rocks.com/2011/12/Transferable-Objects-Lightning-Fast
The text was updated successfully, but these errors were encountered: