Mesh simplification for Unity. The project is deeply based on the Fast Quadric Mesh Simplification algorithm, but rewritten entirely in C# and released under the MIT license.
Because of the fact that this project is entirely in C# it should work on all platforms that Unity officially supports, as well as both in the editor and at runtime in builds.
Hello there! Are you interested in mesh simplification and would like to take this package further?
I'm currently looking for someone to take over this repository since I feel like I'm not the right person to do it, nor do I have enough time to spend on it. Or if you'd just like to be a maintainer. Preferably someone with a better knowledge and interest in mesh simplification.
If you think that's you or your organization, please open up an issue to start a discussion.
Because this project is now using Unity packages, you should use a Unity version from 2018.1 and beyond. Although some scripts have been tested and confirmed working as far back as Unity 5.6, it will no longer be officially supported. Unity introduced the package manager in Unity 2017.2, but at a very early state.
The code will only (at the time of writing) compile with the .NET Standard 2.0 or .NET 4.X scripting runtime versions. The legacy scripting runtime is no longer supported. Read more about this here.
You will find different methods of installing this library into your Unity project here.
If you are not a programmer look into the LOD Generator Helper component.
For programmers you will find documentation for the Mesh Simplifier API and the LOD Generator API useful.
In order to solve artifacts in the mesh simplification process where holes or other serious issues could arise, a new feature called smart linking has been introduced. This feature is enabled by default but can be disabled through the EnableSmartLink field on the SimplificationOptions struct appled to the MeshSimplifier class through the SimplificationOptions property. Disabling this could give you a minor performance gain in cases where you do not need this.
The VertexLinkDistance field on the SimplificationOptions struct could be also be used to change the maximum distance between two vertices for the linking. The default value is double.Epsilon. This value maximum distance is intended to be very small, but you might need to increase it for large scale meshes.
If you have installed this library through the Git URL in the Unity package manager, then you will likely see this problem.
The solution is quite simple however. Open up your Unity Editor, go to Edit > Preferences and then under External Tools you will have multiple options under Generate .csproj files for:. Now simply make sure that Git packages and whatever other kind of package is selected here. You should now see the XML documentation for the API show up in your code editor after having also clicked Regenerate project files.
The original algorithm that was ported from C++ did not support situations where multiple vertices shared the same position, instead of being treated as one vertex they were treated individually. This would then end up creating visible holes in the mesh where the vertices were not connected through triangles.
There are several ways to solve this problem. The smart linking feature (mentioned above) is enabled by default and should take care of most of these problems for you. But there are also options to preserve borders, seams and UV foldovers. The properties PreserveBorders, PreserveSeams and PreserveFoldovers will preserve some vertices from being decimated, strongly limiting the decimation algorithm, but should prevent holes in most situations.
The recommendation is to use the smart linking feature that is enabled by default, but the options for preservation exists in those cases where you may want it.
The most probable cause for this is that you have objects that are parented under bones that will move with the animations. Currently there is no code to deal with this, and the best way to do this is to use nested LOD Groups. Any such object that you know is parented under a bone should have its own LOD Group.
This can be a problem because of an assembly definition provided with this repository, if you are using Unity 2017.3 or above. Make sure that you have the latest version of Visual Studio Tools for Unity. If you are using Visual Studio 2017, make sure that Visual Studio is up to date and that you have installed the Game development with Unity component. For other versions of Visual Studio you would have to download a separate installer. Please go to the Microsoft Documentation for more information.
Please read CONTRIBUTING regarding how to contribute.
