Jupiter LTB Support #22
Merged
Conversation
This file contains 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
|
Currently imports rigid and skeletal (non matrix palettized) meshes. No bones, no animations, nothing flashy. |
|
The shading is a bit odd as seen here: My guess it's to do with an optimized index list. Those verts aren't connected to each other, probably don't need to be for the engine's purposes. Merging by distance will fix it up. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Resolves #20
This PR implements both import of PC LTB v23 meshes, animations, but also provides a more direct way to convert PC LTB files to LTA. (Similar to my old PS2 LTB to LTA converter.)
It also fixes some issues with LTA export for jupiter.