24 replies to this topic

[Burktross]

MWO shouldve been put on the doom or build engine :^)

[Rhaythe]

How to decide upon an engine for a game:

1) Do we have a budget?

• NO: Unity
  
• YES: Go to question 2

2) Do we have more than 1 programmer on staff?

• NO: Unity
  
• YES: Go to question 3

3) Do we have a clear, documented, and meticulously-reviewed vision of what we want our project to look like?

• NO: Unity
  
• YES: Go to question 4

4) Do we *really* have a budget, or is this a Kickstarter?

• NO, NO REAL BUDGET: Unity
  
• KICKSTARTER: Unreal Engine
  
• A REAL BUDGET: Go to question 5

5) Have our shareholders and/or marketing team already committed us to a particular engine?

• YES: Whatever they decided; too late to make a good decision now
  
• NO: Go to question 6

6) Do we like paying license fees per parcel royalties, or in one lump sum?

• PER PARCEL: Unreal Engine
  
• LUMP SUM: CryEngine

[Troutmonkey]

Yeonne Greene, on 21 June 2015 - 07:10 AM, said:

And, as far as I am aware, the networking solution used by PGI is not inherited from the engine, anyway. It's a custom job. The optimization problems are also on the developer end. For all we know, PGI locked tessellation on and so we've got water running under entire levels with polygons being rendered that we never see. That was a problem in Crysis 2.

I've fallen through a couple of maps. There's no water, at least on HPG

[Y E O N N E]

Troutmonkey, on 21 June 2015 - 05:10 PM, said:

I've fallen through a couple of maps. There's no water, at least on HPG

Well, the water would only be on River City, Forest Colony, Crimson Straight, and Caustic Valley if it's there at all. I'm not saying it is, though, just using the example of the Crysis 2 trip-up as an example of how developer shenanigans can cause screwy performance. Crysis 2 and 3, however, actually ran quite well on lower end hardware for the amount of detail they offered at the lower settings.