DirectX is C++ (technically a set of COM interfaces) and most game engines are also C++.

Unlike, say, Linux programming where C is the standard, almost all games have been written exclusively in C++ for a long time now, probably three decades.

▲

cedilla 3 hours ago | parent | next [-]

There are a few exceptions though, like most mobile games, visual novels (many of which use Python of all languages, due to an excellent framework called ren'py), and of course games written using Unity or XNA, which use .NET languages.

Also, three decades is going a bit too far back, I think. In the mid nineties, C was still king, with assembly still hanging on. C++ was just one of several promising candidates, with some brave souls even trying Java.

	▲	pjmlp 3 hours ago \| parent \| next [-]
		In J2ME feature phones Java was all there was, and even today many indies do use it on casual titles on Android. Which is why after so much resistance not wanting to use the NDK for Vulkan, and keeping using OpenGL ES from those devs, Google is bringing WebGPU to Java and Kotlin devs on Android. Announced at last Vulkanised, there is already an alpha version available, and they should talk more about it on upcoming Vulkanised.
	▲	jiggawatts 2 hours ago \| parent \| prev [-]
		> Also, three decades is going a bit too far back My memory was wrong: I was thinking of the Quake 1 engine, but I just looked it up and it’s C with some assembly code, no C++. The reason I remember it being C++ was because Visual C++ was the compiler tooling required on Windows.

▲

direwolf20 3 hours ago | parent | prev [-]

COM was designed to be compatible with C. Linux games are also often written in C++. The ones written in C are just old.

	▲	jiggawatts 2 hours ago \| parent [-]
		Sure, but in practice COM is almost never used from C programs unless there is some integration into a very legacy codebase. Games are newly developed, they’re not enterprise database platforms.