-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Ability to export an scene #1
Comments
I've added the possibility to export to glb in release 0.0.6. Check out the demos, and replace |
Hello again! I have progressed just a bit. I realized I had the exporters were disabled. After enabling them, I tried with GLTF/GLB and this is what I got:
It works with files with embedded textures and materials. I tried exporting an FBX with external textures and I think it needs some more work. |
Oh! wow! Awesome timing! I will check it out definitely. Thank you very much. |
Hello, I have just tested using This is what I am executing:
Any pointers to why this might be happening are appreciate it. Thank you very much in advance! |
I don't know if it's still relevant, but you should use |
@kovacsv - from your drag and drop demo - i am able to get this to work: but this does not work: maybe i need to treat the result differently since it is not text? |
The |
@kovacsv - would you be willing to show an example of taking the glb2 output and turning that into a blob? i want put it into model-viewer. |
For example you can just use the file system api in node.js to write it to a file: let resultFile = result.GetFile (0);
fs.writeFileSync ("model.glb", resultFile.GetContent ()); |
Hello, it would be good if the library can export an scene, either created or imported from a file, to another format. For example import an
fbx
file and export it toglb
.The documentation states this can be done as follows:
I have tried it
However it is not writing the file to the filesystem.
I call this function from the
ImportFileListByMainFile
for the sake of testing.Hopefully this can be done.
Thank you very much!
The text was updated successfully, but these errors were encountered: