f3d: glTF extension CESIUM_RTC is not supported which causes texture to not be loaded
Describe the bug When loaded in f3d v2.5.0, a file using CESIUM_RTC extension is not loaded correctly
To Reproduce Steps to reproduce the behavior:
- Open the file: odm_textured_model_geo.zip
- Observe it does not render fully
- Output in console:
- Expected output (from https://gltf-viewer.donmccurdy.com/)
Warning: In vtkGLTFDocumentLoaderInternals.cxx, line 1362
vtkF3DGLTFDocumentLoader (0x5638f3bc06a0): glTF extension CESIUM_RTC is used in this model, but not supported by this loader. The extension will be ignored.
Original issue below:
Describe the bug When loaded in f3d v2.5.0 with DRACO support, a DRACO-encoded GLB does not render.
To Reproduce Steps to reproduce the behavior:
- Open the file: odm_textured_model_geo.zip
- Observe it does not render
- Test the same file here: https://gltf-viewer.donmccurdy.com/
- Verify report:
Validation report
Format: glTF 2.0
Generator: draco_decoder
Stats:
9 draw calls
0 animations
9 materials
142397 vertices
223185 triangles
Extensions:
CESIUM_RTC
KHR_draco_mesh_compression
KHR_materials_unlit
NOTE: Extensions above are present in the model, but may or may not be recognized by this viewer. Any "UNSUPPORTED_EXTENSION" warnings below refer only to extensions that could not be scanned by the validation suite, and may still have rendered correctly. See: [three-gltf-viewer#122](https://github.com/donmccurdy/three-gltf-viewer/issues/122).
Report generated by[KhronosGroup/glTF-Validator](https://github.com/KhronosGroup/glTF-Validator/) 2.0.0-dev.3.9.
Info Message Pointer
UNSUPPORTED_EXTENSION Cannot validate an extension as it is not supported by the validator: 'CESIUM_RTC'. /extensionsUsed/0
UNSUPPORTED_EXTENSION Cannot validate an extension as it is not supported by the validator: 'KHR_draco_mesh_compression'. /extensionsUsed/1
UNUSED_OBJECT This object may be unused. /bufferViews/0
UNUSED_OBJECT This object may be unused. /bufferViews/1
UNUSED_OBJECT This object may be unused. /bufferViews/2
UNUSED_OBJECT This object may be unused. /bufferViews/3
UNUSED_OBJECT This object may be unused. /bufferViews/4
UNUSED_OBJECT This object may be unused. /bufferViews/5
UNUSED_OBJECT This object may be unused. /bufferViews/6
UNUSED_OBJECT This object may be unused. /bufferViews/7
UNUSED_OBJECT This object may be unused. /bufferViews/8
Expected behavior The DRACO-encoded GLB renders properly.
System Information:
- OS: Alpine Linux Edge x86_64
- GPU and GPU driver: Intel N3450, Intel i915/MESA
F3D Information
Paste the content of f3d --version:
f3d --version
F3D 2.5.0
F3D - A fast and minimalist 3D viewer
Version: 2.5.0.
Build date: 2024-11-13 06:52:25.
Build system: Linux 64-bits.
Compiler: GNU 14.2.0.
External rendering module: OFF.
Raytracing module: OFF.
VTK version: 9.3.1.
Copyright (C) 2019-2021 Kitware SAS.
Copyright (C) 2021-2024 Michael Migliore, Mathieu Westphal.
License BSD-3-Clause.
By Michael Migliore, Mathieu Westphal and Joachim Pouderoux.
Additional context The same file renders in Blender, MeshLab, CloudCompare, and WebODM’s PoTree viewer.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 1
- Comments: 17 (12 by maintainers)
I’ve update the issue and added it in the list: https://github.com/f3d-app/f3d/issues/608
Indeed! Ill update the issue accordingly
Thanks for all your debugs @jo-chemla @Saijin-Naib !
Thanks, just did it here: https://github.com/f3d-app/f3d/issues/1707
Lets create a dedicated issue, Ill then add it to https://github.com/f3d-app/f3d/issues/608.
Found the issue:
In order to get access to glTF + draco you need a more recent VTK (9.3.20240214) . I wish there was a way to inform user of the issue though.
This issue should stay open anyway because the texture is not loading in the file you shared.
Just tried the above command, which says for me that the draco plugin is already loaded (I installed f3d 2.5.0 via
winget install f3d).What’s weird is that the following sample assets with draco compression and png textures do load: Duck, Avocado, BoomBox, and Lantern. Could this be caused by the CESIUM_RTC glTF extension in the case of the OP mesh file?
F3D is not built with draco support afaict, what is the output of
f3d --scan-plugins?