You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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:
I think we should go the .obj route as a starting point if we can get that mesh separation to work!
The text was updated successfully, but these errors were encountered: