UnityMeshSimplifier VS unity-raw-input

You can also reduce the number of triangles on the fly if you want to create your own clipping conditions. For example you can use this component for runtime mesh processing.

https://github.com/Whinarn/UnityMeshSimplifier :

> 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.

Mesh.Optimize: https://docs.unity3d.com/ScriptReference/Mesh.Optimize.html

Unity-Technologies/AutoLOD

Using LOD system, generating LODs for each chunk once its mesh is generated (using https://github.com/Whinarn/UnityMeshSimplifier to generate lower detail meshes). Also, have additional "LODs layer" where I take lowest meshes of all chunks, merge them together and create LODs for resulting mesh. This helps as then I can dissable all chunks game objects and simply enable planet object. (1000 chunks would result in 4000 total game objects as unity uses separate game object for each lod which can all be disabled/destroyed and replaced with 4 gameobjects). This is used if camera is very far away. In screenshot all chunks are in lowest LOD but camera is not far enough away to trigger dissabling of chunks and enabling of planet mesh.

This is more of what I want, but it took so long. It also won't work with my current cave digging system but that's an easy fix for later. I decided against writing my own mesh simplification method since this bad boy already exists.

Either throwing together a very basic unity 2d program and using something like the raw input package here to detect both keypresses and keyreleases and update the png.

There is a package that does what I need but it works only for keyboards (https://github.com/Elringus/UnityRawInput) judging by author's responses to issues it can be modified to also support the mouse. But so far I wasn't able to figure out how. :c