|
|
|
|
|
by pandaman
3343 days ago
|
|
Ok, you completely lost me on the point you are trying to make wrt "C compiled with C++" however I wholeheartedly agree with your penultimate paragraph. Sony and Nintendo do not use these engines, MS might be making the new Gears with UE though, rest of their first party don't. Amazon and Google have one successful game between themselves (and that's a mobile game). All these engines bring to the industry are indies and mobile games. UE actually lost quite a lot of AAA they had in UE3 times. Epic's and Crytec's own games don't do quite well (Crytec is not even making payroll). So yeah, looks like C++ games do not have much to worry about. |
|
Use the platform C++ compiler, but write code only the language subset common to C, that could even be compiled by a plain C90 compiler.
The only exception being, wrapping C++ SDK APIs into C like wrappers.
A pattern I have seen too often.
Dismissing indies is the wrong attitude, they were the first ones to adopt C and Pascal, C++, Objective-C and nowadays C#, Swift, Java.
Sony does use C# a lot on their internal tools.
Nintendo uses Unity for prototyping.
Microsoft and Google are using Unity and Unreal a lot for their VR work.
All of them invited MonoGame developers and supported them porting MonoGame into their platforms (PS4, Switch, UWP Xbox).
C++ might not go away, people still write games in C and Assembly, but it will become that very thin bottom layer at the engine architecture diagram.
Just give it time, eventually even all major C compilers became written in C++.