Skip to content
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

Basic Exporting #13

Open
heavyimage opened this issue Apr 23, 2018 · 0 comments
Open

Basic Exporting #13

heavyimage opened this issue Apr 23, 2018 · 0 comments
Labels
Architecture JS boilerplate? Design? Any sort of high level thing.
Projects
Milestone

Comments

@heavyimage
Copy link
Collaborator

In order to be able to do final geometry tweaks / lighting / rendering / animation, we'll need to be able to export from the application into some sort of 3d interchange format.

For Milestone 1.0, we'll need a basic format that can be loaded by other 3d applications. The choices are:

  • Use OBJ (Looks like there's a way to embed different meshes in one obj described here.
  • Custom format based, say, on json. (Con: need to write a reader for this in maya / blender etc)
  • Use fbx / abc which maya can read but for which I doubt there's an easy way to author from javascript
  • Write out a custom .ma which maya can read + embed controls (gets us pretty deeply in bed with maya specifically though).

I think we should go the .obj route as a starting point if we can get that mesh separation to work!

@heavyimage heavyimage added the Architecture JS boilerplate? Design? Any sort of high level thing. label Apr 23, 2018
@heavyimage heavyimage added this to the 1.0 milestone Apr 23, 2018
@heavyimage heavyimage added this to To Do in Gooper Apr 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Architecture JS boilerplate? Design? Any sort of high level thing.
Projects
Gooper
  
To Do
Development

No branches or pull requests

1 participant