Put instant meshes batch process into a static library #122
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
I wanted to use the instant meshes functionality of the batch process in a different project and therefore excluded the business logic of instant meshes into an InstantMeshesLib project.
That library includes everything needed to start the batch_process from outside.
Also the smoothing step got separated from the extraction step that you can also use smoothing without the full instant meshes workflow. Therefore a new compilation unit smoothing.obj was added.
To use the smoothing I also added the possibility in meshIO to load and write a pure OBJ quad mesh with and without normals information.
Updated gitignore to work with ReSharper and Visual Studio