WOW That's genius! Now it makes sense how you did achieve it. What i tried were the greedy meshing system instead, but it still had some problems at long view distances. Ill can only imagine how much performance boost i will get with using both of the systems!
What are you plans for the feature? Do you plan to stop at one point? Or do you have bigger ambitions?
i plan to recreate Minecraft Java 1 to 1 in C++ (AKA, what Bedrock Edition SHOULD have been), and follow a similar historical progression but instead starting from late infdev and reaching an infdev 2010-06-30 (the last one) equivalent, and then going from Alpha 1.0 to Alpha 1.2.6 and then going from a Beta 1.0 equivalent to a Beta 1.8.1 and all the way until release 1.8 (that is where i will stop)...
all while implementing QoL features like LODs and many optimizations (like very VERY heavy multithreading, and even a future Vulkan transition too for extra optimization), also preserving all the different terrain generations and letting people choose instead of just limiting to the latest one, and who knows maybe i could have either a branch of the game for cubic chunks too.
edit: so yeah this is my long term plan, but this MC clone is just one project of many others of mine that i am making simultaneously, so yeah, no rush, slow but sure progress, which is also why the code is open source too
i wouldn't say it is a better voxel engine, this is my first ever voxel engine too and my god i underestimated how much difficult making a voxel engine would be, it is because of this that i learned multithreading and i also realized that for voxel engines it is much MUCH better to use a ChunkProvider approach to manage chunks instead of whatever the hell i had before
Yeah its really complex. I my self now, I had been rewriting my code over and over just to make it perform better. It feels like I am making spaghetti right now. Maybe should focus more one adding new features, instead of just using my whole free time to make a code that runs 5-8 fps faster.... :skull:
