UnityMeshSimplifier VS godot-proposals

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.

Godot was fine, for the most part, it's a good engine for small games. The main issue was around working together and resolving conflicts with git (Godot isn't really working and constantly kept changing IDs in resource files), and it kept losing data in scenes when the code changed so we had to rebuild things several times. On previous test games we also ran into huge performance issues in the editor when we wanted to do too much work in scenes, so we had to switch to doing most of the work in code.

The worst part was when I had to rip out a bunch of testing code that used @tool for release as it seemed to cause issues when doing a release build. The engine is generally not great when you want to follow clean software engineering (e.g. dependency injection is not possible, I opened a proposal to that end here[1]).

[1]: https://github.com/godotengine/godot-proposals/issues/8850

If we had a Mask2D, this would be super easy and straight forward.

So if that's what OP meant, clip_children property won't work. Instead OP needs to use a CanvasGroup parent and the Line2D (with CanvasItem Material in Subtract mode) and TextureRect as siblings, or any of the other methods explained here until we have a Mask2D node.

There is an open proposal to have a compile option for a LibGodot, as a Library https://github.com/godotengine/godot-proposals/issues/6267

Yes, there could be the option to open at least 2 tabs at the same time, when working with scripts. This has probably already been suggested in: https://github.com/godotengine/godot-proposals

I cannot tell exactly where the jitter is from the video, but if it is what I'm thinking of, it is a known issue, see here. There is a proposal to fix this, with tons of discussion here. Try some of the workarounds mentioned in these two links. Game looks great by the way!

It's in the release notes. Here is a link to the pull request, based on this proposal.

Currently not possible: https://github.com/godotengine/godot-proposals/issues/7213