-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
PBR, Streaming and LOD #596
Comments
Thanks for the kind words.
We are interested in this! See Slide 14 here and perhaps talk to @mlimper about collaboration. As for the LOD and streaming, I don't have any glTF-specific advice, but glTF should be flexibility enough to offer you plenty of options. For example, for HLOD for geospatial datasets, we are building 3D Tiles, where each tile in the spatial data structure is basically a glTF asset. For interleaving, it would be a welcomed contribution to COLLADA2GLTF or perhaps gltf-pipeline. |
Thx for your answer. I will fork COLLADA2GLTF soon to add interleaving and sorting options. |
Sounds great, looking forward to your contribution! |
See #643 for PBR. |
FYI: This protocol is know available at: https://github.com/fl4re/rest3d-new Any feedback is welcome :) |
Could you please add link to github in the presentation, also cross reference presentation in github. Thanks -- Rémi
|
For LOD, see #1045 For streaming, see https://github.com/thibauts/pop-buffer and 3D Tiles (separate but built on glTF). For more streaming discussion, let's start a new issue. |
FYI: This protocol is know available at: https://github.com/fl4re/rest3d-new Any feedback is welcome :) Load streaming only glTF 1.0. Do you have a example load streaming glTF 2.0 ? |
Hi everybody,
Firstly, I want to thank all the WebGL/glTF community for his work (libraries, documentations, tutorials…).
I’m actually working on a viewer using ThreeJS, and all my scenes will be glTF files. I’m trying to allow asset streaming, support Physically Based Rendering and LOD. I would like to ask you some questions and know your opinions. If my work can be benefit to the community instead of resolve only my own problems, it will be more enjoyable and motivating.
About PBR:
Since ThreeJS have a “MeshStandardMaterial” (thx for this add! ), it’s seems interesting to have a glTF extension (or increase the KHR_materials_common) to describe StandardMaterial proprieties instead of sending all the shader and translate it into ThreeJS. Something is on this way ?
About LOD:
I have not seen anything that talks about it. What do you suggest to not disturb the current loaders ?
About the stream:

Let me start by explain what i’m trying to do: There is a diagram showing what i’m actually doing ( I hope this is enough explicit to understand the behavior).
I’m using node.js with websocket-stream module.
The main idea is to send the most essential informations in first. By essential informations i mean which object is the most representative in our asset and which data are most representatives in this object. That why meshes are sort and “position” attribute is sent in first.
The goal for the user is he understand as quickly as possible what this asset represent, even if the global process to transfert all the file is a little bit slower than “classic” approach.
Some problems are coming:
Thank for you attention. And feel free to say what you are thinking, especially if I said bullshit :)
ping: @RemiArnaud
The text was updated successfully, but these errors were encountered: