Nobody can tell you in advance how far your interest in game dev will take you. Only one way to find out: start small (some tutorials, build some crappy first) and see if your interest sticks around as you up the challange.

Maybe game dev in Godot will end up being a significant chapter in your life, maybe it will just be a small sidequest. But once you've given it an honest try, no matter the outcome, you at least will know if it's something for you or not. That in itself is already worth something.

And who knows: maybe Godot is just your entry gateway to something else you discover along the way, which you wouldn't have discovered if you hadn't taken on the challange in the first place.

If you know C++ already, Unreal is a much more natural starting point than either Unity or Godot.

Unreal is what gets used in many AAA shops - it's not a monopoly by any means but it is the most common off-the-shelf engine in the industry. Unity's main edge is that it's easy to learn but if you are comfortable in C++ then there's no real benefit to Unity.

Godot uses GDScript, which is a custom scripting language that's meant to be easy to learn. It's FOSS so you don't need to worry about being screwed over - but it's a lot less mature than something like Unreal which can ship on everything you can think of.

But my advice is to make small things. Don't hyperfocus on a dream game. Just make things that will take a weekend (maybe a week at most). Then move on to something else.

When I was getting into game dev, I made a couple simple projects then jumped into my dream game. I spent so long making that one game that I never finished.

When I got hired in the industry, they cared more about what I released than what my education or job experience was. Because that one big game was never finished, I wound up with my smaller "just getting started" games on my resume; stuff I had made but wasn't proud of. But those games were at least finished and available to the public... and they were what got me hired, not my magnum opus overscoped unfinished indie game I never completed.

If you want to use C/C++ you may be more interested in O3DE, although it's a AAA specialized game engine that's not very user friendly. If you're new to game dev in general, then Godot is definitely the easiest to get started with, but you should use GDScript and not C/C++.

EDIT: or just make your own little game engine with OpenGL or Vulkan, That's probably the most effective way to learn nearly everything..

There is C# support in Godot. I'm not sure how many tutorials have been made with it in particular, but I think there's plenty. Plus their docs go over the API differences so shouldn't be hard to use in any case