Skip to main content

I am reading one great book, Game Coding CompleteGame Coding Complete (http://www.amazon.com/Game-Coding-Complete-Third-McShaffry/dp/1584506806/ref=sr_1_1?ie=UTF8&qid=1295978774&sr=8-1), and that book strongly recommends using MVC (Model-View-Controller) approach, with three key layers:

  1. Game Application Layer
  2. Game Logic
  3. Game View

To me, this approach looks like an overkill for a mobile computer game.

What is your opinion, please? Is it worth of implementing this architecture, even if it adds extra communication needed between modules? Can this design consume so much CPU power, that at the end, the result would be significantly slower, than if it were'ntweren't implemented?

I am reading one great book, Game Coding Complete (http://www.amazon.com/Game-Coding-Complete-Third-McShaffry/dp/1584506806/ref=sr_1_1?ie=UTF8&qid=1295978774&sr=8-1), and that book strongly recommends using MVC (Model-View-Controller) approach, with three key layers:

  1. Game Application Layer
  2. Game Logic
  3. Game View

To me, this approach looks like an overkill for a mobile computer game.

What is your opinion, please? Is it worth of implementing this architecture, even if it adds extra communication needed between modules? Can this design consume so much CPU power, that at the end, the result would be significantly slower, than if it were'nt implemented?

I am reading one great book, Game Coding Complete, and that book strongly recommends using MVC (Model-View-Controller) approach, with three key layers:

  1. Game Application Layer
  2. Game Logic
  3. Game View

To me, this approach looks like an overkill for a mobile computer game.

What is your opinion, please? Is it worth of implementing this architecture, even if it adds extra communication needed between modules? Can this design consume so much CPU power, that at the end, the result would be significantly slower, than if it weren't implemented?

Post Closed as "Opinion-based" by House
edited tags
Link
Jesse Dorsey
  • 2.9k
  • 4
  • 34
  • 59
Source Link
Bunkai.Satori
  • 2.8k
  • 9
  • 37
  • 47

MVC (Model-View-Controller) Game Engine Architecture - Yes or No?

I am reading one great book, Game Coding Complete (http://www.amazon.com/Game-Coding-Complete-Third-McShaffry/dp/1584506806/ref=sr_1_1?ie=UTF8&qid=1295978774&sr=8-1), and that book strongly recommends using MVC (Model-View-Controller) approach, with three key layers:

  1. Game Application Layer
  2. Game Logic
  3. Game View

To me, this approach looks like an overkill for a mobile computer game.

What is your opinion, please? Is it worth of implementing this architecture, even if it adds extra communication needed between modules? Can this design consume so much CPU power, that at the end, the result would be significantly slower, than if it were'nt implemented?