Godot - Terrain Prototype Test 

His GPU is straight up bottlenecked by his CPU. It may be 4c8t, but he would probably see some big increases in framerates if he upgraded to something a bit newer. Advances in CPU architecture have made CPUs a lot more efficient over the years.

You say it's impressive, and at the same time you're promoting the Unreal Engine? Nanite is bad technology, and that's why Unreal Engine 5 has so many problems and is a nightmare in terms of performance. Every game that relies on Unreal Engine 5 and NANITE has massive problems. And you see artifacts popping up everywhere.

@@MatthiasLindemann-hp2zr Nanite is bad tech? Find me another LOD system that allows you to have billions of polygons in a scene while keeping a smooth framerate, I'll wait. Godot probably doesn't even have a proper LOD system yet lol.

@@ghosteyes2708 Nanite causes massive problems, all UE5 games released so far with Nanite have poor performance and FPS drops. In addition, strange artifacts pop up everywhere in the Nanite models, even the shadows flicker with Nanite and load too late. Nanite is very M.2 SSD dependent, and A) not everyone has one, and B) every system is different, and has different drivers, Epic Games didn't take that into account during development.

Thanks! It currently runs in full quality mode. By turning down some SSAO, SSIL and SDFGI it runs better on my old machines. (its currently on ultra) At the moment its also just sibgle threaded due to some bugs and the viewdistances are also quite expensive. But I havn't implemented a limiter based on quality yet. I first wanted to test the max possible.

You should do a test monitoring the CPU and GPU usage, it seems like the CPU you used in the video is very very old for this RTX, and might bottleneck it.

At least in the comment he wrote "When I'm done cleaning up this demo, I'm going to release the project."... hopefully he will release it....

Godot 4 does a really good job actually. It's mainly careful tweaking and a few new shaders for the terrain.

You can get the root viewport and change settings there, similarily to other viewports. In there you will find the settings which correspond to the main window. (as far as I know the project settings are just loaded and applied in there) You can also get the variables by doing get_property_list() / get_method_list() or in the documentation of the Viewport node. # Mip Bias get_tree().root.texture_mipmap_bias = value # Lod Threshold get_tree().root.mesh_lod_threshold = value # Set MSAA get_tree().root.set_msaa_3d(value)

It's rendered in 1080p and the default texture resolution is 4k. I used basic PBR textures for this. (Albedo, Normal, Roughness, Blend for the rocks terrain blend, Alpha + Translucency for the vegetation) I tackled down most of the issues already and built in a custom distance LOD system. (the mesh lods are not good enough for this or at least they don't crunch them down far enough in the distance, so I baked my own imposters) The scene is now running at stable 60FPS with the same settings, even with additional MSAA. (average vertices are now at ~3-4mil primitives) I also reworked the runtime scattering with the garbage collector being triggered at slightly random times to avoid overlap. The demo is currently still running on just one core / thread. If multi-threading is more stable in upcoming builds, this will give an additional boost in performance.

@@Polygarden Sounds really great. Thank You.

Godot 4.02