Open issacclee opened 3 years ago
Yes, I'm sure we could support that extension. Would you be able to provide a sample file that we could test?
@phtaylor
Hi, please find the attached zip file as suggested. It is encoded with both EXT_meshopt_compression and KHR_mesh_quantization extensions. Let me know if you need more files with such extensions for testing purpose.
Thanks. We should get time to look at this in eht next couple of days.
On Mon, May 17, 2021 at 7:15 AM jx.li @.***> wrote:
kezbnt31_aym.zip https://github.com/ZeaInc/gltf-loader/files/6493363/kezbnt31_aym.zip
@phtaylor https://github.com/phtaylor
Hi, please find the attached zip file as suggested. It is encoded with both EXT_meshopt_compression and KHR_mesh_quantization extensions. Let me know if you need more files with such extensions for testing purpose.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ZeaInc/gltf-loader/issues/1#issuecomment-842239267, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGNDOMFU34TLVCDZHRNKWDTOD3F3ANCNFSM44753ZYA .
-- [image: Zea Homepage] http://zea.live/ Fast, Easy and Open Philip TAYLOR CEO, Zea Inc.
Schedule a meeting https://meetings.hubspot.com/philip-taylor1 Montréal, Québec M: +1.514.582.4325
Hi @issacclee , how was this glb file produced? can you tell me what tools were used?
original CAD file is STEP format, it was translated into gltf format and post processed with gltfpack with quantization and meshopt flags enabled in gltfpack cli
the STEP to gltf translation was done by CadExchanger. We run a forked version of gltfpack with most changes focused on the way to use toktx CLI to compress texture, and preserve certain extra information which would otherwise be stripped by the original version of gltfpack. I would assume those changes have no effect on the way gltfpack construct mesh data based on meshopt & quantization extension specs.
Ok, so the post processing was an optional step you applied after CAD Exchanger.
Does the original file exported from CAD Ex load ok?
I'm just learning about the meshopt tools. So far I think I have that part working, but the quantization is now proving to be more challenging.
On Thu., May 20, 2021, 3:10 a.m. jx.li, @.***> wrote:
the STEP to gltf translation was done by CadExchanger.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ZeaInc/gltf-loader/issues/1#issuecomment-844776205, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGNDOPY7DZMCGUORH5POIDTOSYWTANCNFSM44753ZYA .
Could I also take a look at the original gltf? I'd like to compare.
On Thu., May 20, 2021, 5:59 a.m. Philip Taylor, @.***> wrote:
Ok, so the post processing was an optional step you applied after CAD Exchanger.
Does the original file exported from CAD Ex load ok?
I'm just learning about the meshopt tools. So far I think I have that part working, but the quantization is now proving to be more challenging.
On Thu., May 20, 2021, 3:10 a.m. jx.li, @.***> wrote:
the STEP to gltf translation was done by CadExchanger.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ZeaInc/gltf-loader/issues/1#issuecomment-844776205, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGNDOPY7DZMCGUORH5POIDTOSYWTANCNFSM44753ZYA .
Hi, Plz find the attached zip file as the original gltf prior to the gltfpack operation
Hi Guys, Do you have any plan to support loading gltf assets with EXT_meshopt_compression and KHR_mesh_quantization extensions?