Comments on: Common Component Syndrome http://makemacgames.com/2005/08/30/common-component-syndrome/ The Adventure Fri, 21 Nov 2008 08:46:23 +0000 http://wordpress.org/?v=2.6.3 By: Jon Trainer http://makemacgames.com/2005/08/30/common-component-syndrome/#comment-77 Jon Trainer Wed, 07 Sep 2005 12:53:17 +0000 http://makemacgames.com/?p=62#comment-77 Hi Keli! Thanks for reading and leaving your thoughts. I'm glad to see someone from Unity (OTEE) chime in. You are absolutely right. It is unfair to compare Unity and Torque to a database grid. But, it was only to make a point. I have a whole bunch to say on this topic and my reply is turning out to be too long for a comment, so I'm turning it into a post that should be added to the site later today. Hi Keli! Thanks for reading and leaving your thoughts. I’m glad to see someone from Unity (OTEE) chime in.

You are absolutely right. It is unfair to compare Unity and Torque to a database grid. But, it was only to make a point.

I have a whole bunch to say on this topic and my reply is turning out to be too long for a comment, so I’m turning it into a post that should be added to the site later today.

]]> By: Keli Hlodversson http://makemacgames.com/2005/08/30/common-component-syndrome/#comment-76 Keli Hlodversson Wed, 07 Sep 2005 07:38:46 +0000 http://makemacgames.com/?p=62#comment-76 Using Unity as a game engine does not lock you into any certain kind of game. (Well except it has to be some kind of 3D game :P) It just removes the tedium of writing your own game engine and provides a glue for your own game code and assets. It makes common taks easy, hard tasks possible and near-impossible tasks within reach. Please take a look at OTEE's widget challenge contestants. There are 13 very different games. (Even a 2D board-game one.) (http://www.otee.dk/widget-challenge.html ) The analogy to the database grid view is in my opinion unfair (even to Torque.) Game engines are complex extensible products with focus on releiving game developers from common tasks. You wouldn't want to write your own compiler or 3D modeller, would you? Most software devolpers suffer from a 'Not invented here' syndrome once in a while. A good manager will save a lot of development time and money recognising and avoiding that syndrome. ( http://en.wikipedia.org/wiki/Not_Invented_Here ) -- Keli PS. Yes, I work for OTEE. Using Unity as a game engine does not lock you into any certain kind of game. (Well except it has to be some kind of 3D game :P) It just removes the tedium of writing your own game engine and provides a glue for your own game code and assets. It makes common taks easy, hard tasks possible and near-impossible tasks within reach.

Please take a look at OTEE’s widget challenge contestants. There are 13 very different games. (Even a 2D board-game one.)
(http://www.otee.dk/widget-challenge.html )

The analogy to the database grid view is in my opinion unfair (even to Torque.) Game engines are complex extensible products with focus on releiving game developers from common tasks. You wouldn’t want to write your own compiler or 3D modeller, would you?

Most software devolpers suffer from a ‘Not invented here’ syndrome once in a while. A good manager will save a lot of development time and money recognising and avoiding that syndrome.
( http://en.wikipedia.org/wiki/Not_Invented_Here )

–
Keli
PS. Yes, I work for OTEE.

]]> By: Jon Trainer http://makemacgames.com/2005/08/30/common-component-syndrome/#comment-70 Jon Trainer Wed, 31 Aug 2005 21:16:57 +0000 http://makemacgames.com/?p=62#comment-70 <blockquote>Agree 100%</blockquote> Thanks.

Agree 100%

Thanks.

]]> By: Make Mac Games » Blog Archive » The Escapist on The Games Industry http://makemacgames.com/2005/08/30/common-component-syndrome/#comment-69 Make Mac Games » Blog Archive » The Escapist on The Games Industry Wed, 31 Aug 2005 21:14:40 +0000 http://makemacgames.com/?p=62#comment-69 [...] Make Mac Games The Adventure « Common Component Syndrome [...] [...] Make Mac Games The Adventure « Common Component Syndrome [...]

]]> By: radioact1ve http://makemacgames.com/2005/08/30/common-component-syndrome/#comment-68 radioact1ve Wed, 31 Aug 2005 04:14:59 +0000 http://makemacgames.com/?p=62#comment-68 Agree 100% I had always thought of coming up with my own engines. Your last sentence says it all. "Doesn’t it make sense to make the technology fit the game, not the game fit the technology?" I see those "all purpose" engines are, all though great for the various reasons you listed above, just missing something. Something that only an engine made for the game would have. I just finished playing Darkwatch from High Moon. Great game and all, but when I saw in the beginning credits that they were using RenderWare I was a little disappointed. Graphics great and all, but of course reminded me of those games that use RW. Great game over all though. Agree 100%

I had always thought of coming up with my own engines. Your last sentence says it all.

“Doesn’t it make sense to make the technology fit the game, not the game fit the technology?”

I see those “all purpose” engines are, all though great for the various reasons you listed above, just missing something. Something that only an engine made for the game would have.

I just finished playing Darkwatch from High Moon. Great game and all, but when I saw in the beginning credits that they were using RenderWare I was a little disappointed. Graphics great and all, but of course reminded me of those games that use RW. Great game over all though.

]]>