11 replies to this topic

[DAYLEET]

Title says all. MWO CryTech, AUTE UnrealEngine 4.

[Ryvucz]

Copy paste resources into the game worlds I guess.

[Scratx]

Those are not the kind of resources they'll be sharing. The only resources they'll be sharing is data center, office space (and all associated with it), tech backbone behind MWO's operations and some management, QA and other personnel.

Which is a LOT, when you start to think about it.

[DAYLEET]

Scratx, on 09 September 2014 - 03:55 PM, said:

Those are not the kind of resources they'll be sharing. The only resources they'll be sharing is data center, office space (and all associated with it), tech backbone behind MWO's operations and some management, QA and other personnel.

Which is a LOT, when you start to think about it.

Uh, Russ made it clear personnel would ONLY be shared if one game had accomplished it's current goal and would help the other team achieve theirs instead of moving on on their own side. So now everyone has to work on 2 different engine, sounds counter productive.

[Scratx]

DAYLEET, on 09 September 2014 - 04:07 PM, said:

Uh, Russ made it clear personnel would ONLY be shared if one game had accomplished it's current goal and would help the other team achieve theirs instead of moving on on their own side. So now everyone has to work on 2 different engine, sounds counter productive.

You misunderstood me. Any personnel whose tasks don't have to be game-specific (like support personnel, accountants, human resources, etc) are shared by both games. Likewise, rent, utilities, etc, are also shared by the two games, not just one. Scaling up to running two projects means you can have a dedicated team on each project and share the fixed costs of running the business among both projects.

[Darth Futuza]

I also don't get why they are throwing away all their experience working with CryEngine to now run into nightmares with a new engine they know nothing about.

Seems wasteful.

[9erRed]

Greetings all,

For PGI starting a game using CryEngine was a first. And they had never worked or used that engine before.
- Not so with unreal.


Directly from the site itself.

- The open-ended architecture of Unreal Engine 4 gives us the freedom to make our game exactly how we want.
UE4 is built for multiplayer – this combined with our in-house backend starts us out of the gates running.
Fast prototyping is critical to solid delivery.
- UE4’s blueprints system allows us to get to work quick. Designers can experiment with gameplay features and get fast feedback, ensuring movement, combat, and all aspects of play feel balanced.
UE4’s advanced, node-based material system gives us the power to create intricate, high resolution materials with dynamic effects. With cutting edge particle technology right out of the box, visual effects are taken to the next level of realism; players will really get the sense that they are in a huge, zero gravity environment.
To top it all off, customizable post-processing effects dynamically set the mood wherever players explore.
The gold standard in game engines, UE4 allows us to make a big, multiplayer universe with incredibly rich and highly detailed environments.

Even from the start of MWO, the CryEngine turned out to not be the Engine they though it was, and didn't have the functionality they needed. Wasn't server authoritive based, and needed large amounts of modification just to get the game in a playable state.
- This is not the case with the Unreal 4 engine platform.

9erRed

[Darth Futuza]

That's all just "Yay look at us" fluff and is just marketing hype. CryEngine can handle MMO's just fine, see Star Citizen and ArcheAge for examples of successful application. The fault was never the engine, but the lack of experience the developers had with it. Now that they've had experience they are going to run into the same problems they had with CryEngine because they aren't familiar with the new engine.


Additionally when asked if they could go back and switch to another engine for MWO, Russ said no, CryEngine had been great.

Edited by Darth Futuza, 09 September 2014 - 09:37 PM.

[McHoshi]

Darth Futuza, on 09 September 2014 - 06:49 PM, said:

I also don't get why they are throwing away all their experience working with CryEngine to now run into nightmares with a new engine they know nothing about.

Seems wasteful.

UE4 is much more easier to manage than cryengine is

[Darth Futuza]

McHoshi, on 10 September 2014 - 01:25 PM, said:

UE4 is much more easier to manage than cryengine is

Depends on what you're doing, but regardless it is still new technology they have to learn when they should already be familiar with the other.

[Lily from animove]

There are a lot ressources to share that are not engine related, like art designers, QA stuff for findign bugs. the whole overhead stuff of marketing and support guys etc ....

[CMetz]

Crytek's recent woes might have something to do with it, but this is sheer speculation on my part. Seems to me that UE4 would be the more stable business choice. In addition, if I am correct, I believe CryEngine is MUCH more resource intensive.