Stormsinger wrote on Dec 17, 2013, 14:50:
So let me see if I have this straight now. You're saying that as of a month and a half before the deadline -they- had set, they hadn't even decided what engine they were going to use?
Okay there seems to be quite a bit of confusion in this thread... ENGINE is not the same as NETCODE, which is what they are referring to in this article.
Game Engine from Wikipedia:
"A game engine is a system designed for the creation and development of video games. The leading game engines provide a software framework that developers use to create games for video game consoles, mobile devices and personal computers. The core functionality typically provided by a game engine includes a rendering engine (“renderer”) for 2D or 3D graphics, a physics engine or collision detection (and collision response), sound, scripting, animation, artificial intelligence, networking, streaming, memory management, threading, localization support, and a scene graph. The process of game development is often economized, in large part, by reusing/adapting the same game engine to create different games, or to make it easier to "port" games to multiple platforms."
The NETWORKING or we shall say NETCODE is what is being rewritten to better support ship to ship combat. Crytek ENGINE NETWORKING was designed with FPS combat in mind and was already planned to be scraped and rewritten a while ago because it wasn't up to snuff. However they wanted to release the dogfighting module in December so they could use that to bring in more developmental money and were going to be stuck releasing it with the existing NETWORKING that didn't work so well for their space game. Since they recently received a large amount of funds they don't need to rush out the module now to gain new funding. So since they now have the money they want to delay the module so they can release it with the proper NETWORKING they originally didn't have the necessary money to do. Is that clear enough now?
Long story short; they were going to release the module to get more money but they got more money elsewhere and now can release the proper module they originally wanted to put out, hence the delay...