Also posted as a discussion for open conversation: #2085
xeokit-convert/xeokit-sdk handle IFC, glTF, CityJSON and others, but there's no path from SketchUp .skp into XKT — today that means an extra lossy hop through IFC/glTF first.
OpenSKP is an MIT-licensed, from-scratch .skp reader — pure TypeScript (openskp on npm), works in Node and the browser, no native binary. Parses geometry, materials, layers, and instancing directly, bakes a triangulated scene.
Would a direct .skp → XKT conversion path be useful here? Happy to build it out if there's interest.
Also posted as a discussion for open conversation: #2085
xeokit-convert/xeokit-sdk handle IFC, glTF, CityJSON and others, but there's no path from SketchUp
.skpinto XKT — today that means an extra lossy hop through IFC/glTF first.OpenSKP is an MIT-licensed, from-scratch
.skpreader — pure TypeScript (openskpon npm), works in Node and the browser, no native binary. Parses geometry, materials, layers, and instancing directly, bakes a triangulated scene.Would a direct
.skp→ XKT conversion path be useful here? Happy to build it out if there's interest.