Open
Conversation
|
What if you use the same material on two sides of a cube? Would it only create one object (one side) (finally got around to looking at this) |
Author
|
I didn't consider that. I'll patch this up when I get the chance. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upon loading a .OBJ file into away 3D, it will only use the last mentioned texture in an object, defined by "o" and "usemtl"
this happens because each object can only have 1 texture, but the OBJ file attempted to load multiple textures onto 1 obj. I fixed this by instead of creating a new object on every use of the O keyword, it ignores the O keyword and will then create a new object under usemtl, then applies the texture.