love VS Godot

Start by making some games imo, unless you already have a good project in mind. https://tic80.com or https://love2d.org

If all goes well with PICO-8, you can "upgrade" to love2d, which like PICO-8 uses Lua programming language, but allows for higher resolutions, and generally more polished outcome.

I have a similar profile, and I have tried many different engines/frameworks/libraries. Some thoughts: - ebiten, written in Go, is a very light game dev lib. I like Go, so writing "my own engine" with it was pretty fun (I have some libs for ebiten here). Mostly 2d. - Love2d is sort of the same thing, but written in C++, and scriptable in Lua. I absolutely love this level of abstraction, and this is probably the one I have been the most productive with (example here). Mostly 2d, but people have done 3d with it too. - Godot has a bright future, at least from my point of view. The 2D workflow is very very fast, much faster than Unity in my experience (you don't spend time waiting for stuff to recompile every time you edit a script, for starters), and they just released v4, which comes with insane improvements in 3D rendering. I have never delved into 3D, but from what I can see, it's on par with what Unity can produce these days. Plus, the founders have created a separate commercial entity to provide support for consoles (called W4games), because the open source licensing attached to Godot is not compatible with the NDAs involved in publishing for consoles - raylib and monogame might be interesting for you if you want to go old-school. They're both inspired by the same framework (XNA) and they work similarly. Also very close to the way Love2d does things, and a comparable level of abstraction. - Unity is slow. I honestly dislike it a lot, just for this reason. There's also a lot of "we've refactored this, and there's no docs yet, but you can also use this other system, and also the legacy one, and that one, or build your own based on these primitives" and it's hard when you're a beginner. If you know what you're doing I guess it's fine, or if you don't care, but as a software engineer, you will probably be like me and try to find the "best" solution to your problem, which is tiring and hard to do with Unity.

Also, a recommendation that is a little more Niche. Lua, and love. love2d.org is a really easy to make games with a relatively simple programming language. Could be fun.

Are you saying she wants the D? Because that's a total brainfuck. I'd much rather believe they merely fell in Löve.

Being a hard worker and having persistence are more important than being intelligent; a lazy genius never accomplishes anything. Try learning programming as its own skill separate from gamedev first. If you're finding C# too difficult, than try a simpler language like Lua. Lua specifically can be used with Love2D to make games.

i read you want to make games. go for 2d games, love https://love2d.org/ or pygame https://www.pygame.org/news or some kind of js engine for webgame https://github.com/collections/javascript-game-engines

You mean the game development library LÖVE?

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.