[bluescrn]

People underestimate the cost of switching game engines.

While a lot of concepts are transferrable between engines, if you've got a team of experienced C#/Unity developers who haven't touched UE, switching to C++/UE is likely to cost a lot of time/money. A new engine can still be a steep learning curve for experienced game developers. You might be able to pick up the basics over a weekend, but reaching expert levels of knowledge takes years.

That cost increases further if it means restarting a project from scratch rather than building on top of an existing codebase (which will likely include not just the game itself, but also an assortment of tools built within Unity for building content and improving workflows).

Unity's killer feature for many is still its C# support. If you're a small team or solo developer who doesn't need AAA levels of performance, it can be a big time-saver over working with C++.

[Vespasian]

That's one of the reasons why Godot started brushing up their C# support recently.

For that that small/solo team it's also easier to switch engine and since they can't get custom license deals like the big boys having the same language may encourage some to invest the time and resources.