There are reasons why AAA studios stick to C++: they don't know any better, they're in constant crunch-mode and don't have time to look for better alternatives, they use an existing engine with years of development history and don't want to invest in a new one, they target platforms where only C/C++ compilers are available, etc.
You'd be surprised of the horrors you can find in a game's C++ code base (there are gems too, but you kind of expect those.)
While it's true that some languages make some horrors easier to bring into the world (if you take away people's access to the memory, for example, you remove an entire class of memory-related nightmares), in my experience, the key requirement for creating these horrors isn't the language; it's the programmer and the constraints they're working under (such things as inexperience, painful levels of urgency, inappropriate processes, team churn, and so on and so on). People can and will make horrors in any language, and if D becomes the new C++, in twenty years people will be saying the same things about D.
When I think about all the different variable initialization rules in C++ I know I'll get it wrong in crunch time and most likely get it wrong when all my work conditions are perfect because there's like 7 different rules. And that's for one feature only.
D doesn't make it impossible to write horrors, it just doesn't ask for it the way C++ does.
Relatively small backend apps written in C++ may be a better target for D and Rust.
The difference is that they only do it when the OS vendors, or game console vendors, force them to adopt new languages in their SDKs.
First there was only Assembly, C and Pascal dialects were dog slow, and the OS vendors forced them to go C.
Then there was only C, C++ was dog slow, and the OS vendors forced them to go C++.
Then there was only C++, language X was dog slow, and the OS vendors force them to go language X.
The question is what language X stands for.
https://www.st.cs.uni-saarland.de/edu/seminare/2005/advanced...
And the new generation usually comes with a fresh set of ideas about things, and some of the newbloods will be "stupid" enough to start and rewrite some of the C++ tools, at the expense of their employers that will see delayed projects and tons of bugs because of this, and probably fire the trouble-makers, but the retooling will happen anyway, so it's probably better for people to embrace it and start allocating budget slices for it.
Edit: yeay the downvote bandwagon, you should go to a AAA studio and ask about C++.