-
-
Notifications
You must be signed in to change notification settings - Fork 982
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
Should MeshMagick be integrated into the OGRE repo? #3092
Comments
it was started outside of Ogre, thats why it never was part of the Ogre tools. However, since I switched Ogre to the monotree approach, it could be merged. That being said, there doesn't seem to be a great deal of interest or usage of the tool, and it would need to be updated to align with Ogre's current build, test, and documentation frameworks. |
I think it would be useful to have amongst the other tools that come with OGRE, perhaps people are not aware of the tool because of that. Anyway I wanted to know if you were open to integrating it.... |
the problem with integrating meshmagick is that it is also a library as shown by the doxygen file in the repo. So we would need to split it into a component and a tool which complicates things. Also one should clean up the code before merging:
for now I have added it to the tools page on the website: |
Is tootle obsolete? If there are ogre-next ifdefs then perhaps it is an argument against integrating it into this repo... |
yes, see OGRECave/meshmagick#7
it is actually a separate branch. forgot the details. looking at the commits, it seems that tootle is the most used feature. For that we could just improve -optvtxcache in MeshUpgrader by using meshoptimizer directly. |
OK, tootle is discontinued by AMD but is it not useful anymore?
Is it a proper replacement for tootle? I'm asking from ignorance. Thanks |
I have no idea how what the ranking of current -optvtxcache vs tootle vs meshoptimizer is. Someone would need to benchmark I guess.. |
I was wondering why MeshMagick sits apart from the rest of the OGRE tools.
The text was updated successfully, but these errors were encountered: