cryengine

This is what draws my attention more: > //FIXME: There's a threading issue in CryPhysics with ARM's weak memory ordering. https://github.com/CRYTEK/CRYENGINE/blob/6c4f4df4a7a092300d6... Translation: "We have race conditions in our C++, but x86 is lenient enough and current MSVC not aggressive enough to make it crash and burn constantly on our main platform." Coincidentally, I finished Crysis 1 today. That involved the first four crashes I had with the game, three of which were in the final battle.

There's some RAII: https://github.com/CRYTEK/CRYENGINE/blob/release/Code/CryEng...

I don't think it's the best code I've ever seen, but a lot of these are surface-level complaints. > * goto inside 3 nested for-loops. C has no pattern for breaking out of multiple for loops at the same time. Other languages like Java and JavaScript introduced "break label;" to handle this edge case. goto is perfectly acceptable to break out of multiple loops. > * new/delete, with no RAII They use RAII, but it's not applicable here. In this case, the developers only want to allocate a temporary array when it needs to be resized. Since we don't want a large stack allocation (stack sizes are super small on consoles), using a delete/free to resize an array seems fine to me. Game developers have a long-seated distrust of std::vector, and for good reasons. RAII is used for the WriteCondLock which you criticize in the next bullet point, so it's

This is on the front page again. Please take some time to read this wonderful function: https://github.com/CRYTEK/CRYENGINE/blob/release/Code/CryEng... EDIT: That whole function is a minefield. Just taking a quick look: * 814 lines of code * goto inside 3 nested for-loops * macros * commented out code * new/delete, with no RAII * thread specific variables and locks (?)

Many of the filed issues are "X not work" and not very interesting, but this one...this one is a real gem. https://github.com/CRYTEK/CRYENGINE/issues/763

> I did not say that everyone was using ICC, rather that desktop and game developers did not share the same opinion regarding ICC and Visual C++ Yes, sure. MSVC is garbage clearly isn't right. I presume (in the absence of any real data of course) that ICC doesn't result in significant performance advantages over MSVC, for games, or it would have been worth these developer's time to support it. > if you are reducing the world to just what Unreal, Source and CryEngine officially support It's a reduction sure enough, but I think that's a reasonable set of engines to consider. > I wonder how many AAA games have been released on Windows using GCC or clang with those engines I imagine it's none. According to the (quite possibly stale) official wiki, Source does not support Clang, and only supports GCC for building Linux dedicated servers. [0] I

The article references the tick function from CryEngine briefly (https://github.com/CRYTEK/CRYENGINE/blob/release/Code/CryEng...). How do people manage to figure out or learn how to read and work on something like this? It looks mindbogglingly complex.

According to Crytek, it should be. Their engine license[0] is, if I am reading it correctly, similar in this respect. > By doing so, you, the Licensee, agree to all terms and conditions of this Agreement or in the accompanying documentation. You should read this Agreement carefully before the Start Date. If you do not agree with the terms and conditions set forth in this Agreement you are not authorized to use the CRYENGINE. > You agree to check www.cryengine.com periodically for new information and terms that govern your use of CRYENGINE. Crytek may modify this Agreement at any time. Crytek will inform you about revisions to this Agreement by email and/or by a notice on our home page and/or during log in. Revisions to terms affecting existing CRYENGINE shall be effective thirty (30) days after posting at www.cryengine.com If you do not a

It is not, just take a look at the third party directory of chromium, where it tracks all its third party dependencies https://github.com/chromium/chromium/tree/master/third_party the main point of their build system gn (similar to bazel) is to have explicit and distribution independent control of all dependencies (typically tied to specific versions). LLVM basically has no system dependencies as well, instead it implements a lot of platform abstractions within the repository (https://github.com/llvm-mirror/llvm/tree/master/lib/Support), the remaining dependencies are mostly build dependencies such as python 2.7 and cmake. Same story for Cryengine (https://github.com/CRYTEK/CRYENGINE/tree/release/Code/Libs) and Unreal Engine (https://github.com/EpicGames/UnrealEngine/tree/release/Engin...). Linux distributions simply duplicate a lot of w