meshoptimizer

This is where I grew up. Back then, getting home meant crossing a reservoir in a wooden boat. The bamboo grove and the old house were on the other side of the water. I grew up and got used to a world of tall buildings. The things I once saw every day slowly became things I had to remember. I gave GPT-6 Astra a few photographs, and it turned them into this 3D scene. There it was again, on my screen. Of all the things I've made with AI, this might be the one I love most. One day, the real place may no longer be there. And I can no longer go back. At least here, I can look at it once more. For this, I'm grateful to AI. This is my first Three.js project, and God knows how bad the initial performance was—even my M4 Mac mini couldn't handle it. I've done a lot of optimization since. Huge thanks to meshoptimizer (https://github.com/zeux/meshopti

Worth mentioning that MeshOptimizer (https://github.com/zeux/meshoptimizer) has become one of a handful 'hidden champion' pillar libraries that probably carries half of the gaming industry. Basically the curl of asset pipelines ;) https://github.com/zeux/meshoptimizer/discussions/986

Our budget couldn't afford Epic Games style nanite, but there are three js implementions.. so it's not impossible to recreate. - https://github.com/AIFanatic/three-nanite - https://news.ycombinator.com/item?id=42974461 three-nanite is based on https://github.com/zeux/meshoptimizer cutting each mesh into maybe 124 triangles per chunk.

In godot engine we decide to do a continuous level of detail based a pixel error metric. (simplified explanation pixel-error -> based on fov -> based on floating point error of the meshopt_simplifyWithAttributes function) The 12 ish lods are automatically generated by https://github.com/zeux/meshoptimizer. https://docs.godotengine.org/en/stable/tutorials/3d/mesh_lod... We allow a hierarchical level of detail if people want to set it up.

> Making a nanite mesh is complicated, with a lot of internal offsets for linking, and so far only Unreal Engine's editor does it. meshoptimizer [1] is an OSS implementation of meshlet generation, which is what most people think of when they think of "Nanite's algorithm". Bevy, mentioned in a sibling reply, uses meshoptimizer as the generation tool. (Strictly speaking, "Nanite" is a brand name that encompasses a large collection of techniques, including meshlets, software rasterization, streaming geometry, etc. For clarity, when discussing these concepts outside of the context of the Unreal Engine specifically, I prefer to refer to individual techniques instead of the "Nanite" brand. They're really separate, even though they complement one another. For example, software rasterization can be profitably used without meshlets if your triangl

Wow, Martini looks really interesting! I did some research about mesh simplification and had some success using https://github.com/zeux/meshoptimizer. Meshoptimizer is in c++ so I had to use the Rust wrapper https://github.com/gwihlidal/meshopt-rs and compile it to wasm. I actually opensourced this code at https://github.com/blaze33/dem2mesh, just have to use dem2mesh.png2mesh which given a png data, computes the heightmap, builds a mesh, simplifies it and return the data to javascript. (can be tricky though to deal with wasm)

heres a random search result that is code that cites that paper for its own strip generation https://github.com/zeux/meshoptimizer/blob/master/src/stripi... source: went to https://sci-hub.tw/10.1109/VISUAL.1996.568125 then searched one of the author names + github paper title and authors are Optimizing Triangle Strips for Fast Rendering Francine Evans Steven Skiena Amitabh Varshney

From the post: >One number that we haven’t moved substantially yet is the time it takes to run this code in debug using MSVC. While it’s natural to expect unoptimized builds to be slower than optimized, they have to be fast enough. Sometimes you want to debug your problem on a non-trivial input dataset. Sometimes you want to run the debug build with full checks through your tests to make sure they don’t trigger any bugs that could disappear in release. Sometimes you are trying to debug a different part of the program, but you still need to run the rest of it. The library, by the author, is https://github.com/zeux/meshoptimizer. I presume it will be used in graphics pipelines. Debug builds working at a speed that allow graphics to be tolerable by humans sounds like a good goal to have.