-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
b3dm with external textures reference error #3892
Comments
@konashredbiker thanks for the report! Do you have a sample 3D Tiles tileset that we can test with? Just a tileset with one simple .b3dm file would be great. |
Yes, here I generated a simple one. |
Thanks @konashredbiker! I added this as a near-term item to the 3D Tiles roadmap, #3241. |
@sumitshyamsukha Let's work on this after #4344. In For testing that it works download the sample tileset provided above, host it somewhere (we usually use the
Then in the |
@lilleyse I was trying to host the sample tileset provided, but after running the
I imagine it's most likely something to do with an Express route -- any suggestions on how to fix? |
You don't need to access 8003 directly, you just need to get the url of the tileset hosted there. Run Sandcastle normally from localhost:8080 and in the 3D Tiles demo change the url of one of the tilesets to |
Fixed in #4376 thanks to @sumitshyamsukha! Thanks for the report, @konashredbiker! |
In the 3D Tiles branch, when loading a b3dm file that references external textures like this:
"images":{"tex_5709034.jpg":{"uri":"textures/tex_5709034.jpg"}
The request for texture images then looks like this:
http://localhost:8080/Specs/Data/Cesium3DTiles/Batched/BatchedWithBatchTable/b3dms/R/SW.b3dm/textures/tex_5709034.jpg?v=0.0
which results in
Failed to load resource: the server responded with a status of 404 (Not Found)
The path in not relative to the folder containing the .b3dm file, but to the file itself.
When removing the b3dm header and loading it as an .glb, the textures work fine. Simply adding "../" in front of the path results in not seeing the model at all.
Tested in Chrome and Firefox
The text was updated successfully, but these errors were encountered: