engine VS Godot

There are many engines that you can use in browser. 1. (GDevelop)[https://gdevelop.io/] 2. (Construct 3)[https://www.construct.net] 3. (Godot Engine)[https://editor.godotengine.org] 4. (Play Canvas)[https://playcanvas.com] 5. (Hex Engine)[https://hex-engine.dev]

Web-focused 3D engines (three.js, babylon.js, PlayCanvas, ...) are pretty capable. Maybe not AAA-level like Unreal Engine, but certainly capable of the stuff you're describing here. If you're comfortable working within these frameworks, and writing shaders, there's a ton you can do.

I wasn't familiar with PlayCanvas, looks very cool.

Another thing I recommend is to learn how to make games with ThreeJS (3D) or PixiJs (2D) and build web-based games using javascript. If you want a full-fledged web game engine, then you can take a look at Playcanvas. Playcanvas is similar to unity but for web-based games. If you want to learn all about Three Js then this course will help you a lot.

Engines: PlayCanvas, Three.js, BabylonJS

Godot game engine - MIT license. Go wild.

Some of issues in current csg implementation is already fixed here just wait for it to be merged into the main branch but some edge cases are not yet solved.

I have a beefy machine and noticed the same thing. Porting my projects to 4 resulted in all-round poorer performance in builds as well. I posted my tests here

One of, if not the main, issue threads about it with 200~ replies: https://github.com/godotengine/godot/issues/20566

The other primary tool to think about today is Godot (https://godotengine.org/). I feel like Godot is to the main game engines (Unreal and Unity) very similar to Blender's relationship to the major 3D modeling tools (Maya, Max, etc.) Godot is improving at a dramatic rate, and it's a wonderful tool for creating 3D games from assets you create in Blender. It's lightweight but incredibly powerful, is reasonably easy to learn, and exports to a lot of great formats including web.

If you feel there is something missing in the documentation, you can open an issue on the docs repo, or if it's about the class reference, the main repo. Even if your issue doesn't match the template exactly, it's ok as long as it describes the problem properly.

I recommend a hierarchy of terrains and avoid "dirt-on-grass"/"grass-on-dirt" scenarios to prevent the algorithm from choosing a transition tile from the wrong tile set. The issue is better described here: https://github.com/godotengine/godot/issues/70218

It's only a matter of time before we can find this on SideQuest -- Bastiaan's work on a VR editor

Clone Godot repository then switch to your current using version if needed.