Latest News
spacer View All spacer
 
November 7, 2009
 
Iwata: 35% Japanese Connectivity Ratio For Wii, 20% For DS
 
iPhone Dev Storm8 Sued Over User Data Harvesting Allegations [5]
 
Game Boy, The Ball Admitted To National Toy Hall Of Fame
spacer
Latest Features
spacer View All spacer
 
November 7, 2009
 
arrow On Bringing Modern Warfare 2 To Life [3]
 
arrow Games Demystified: Dissidia Final Fantasy [1]
 
arrow Building Social Success: Zynga's Perspective [3]
spacer
Latest Jobs
spacer View All     Post a Job     RSS spacer
 
November 7, 2009
 
FarSight Studios
Software Engineer
 
Sucker Punch Productions
3D Environment Artist
 
Sucker Punch Productions
Network Programmer
 
Sucker Punch Productions
Character Artist
 
Sucker Punch Productions
Texture Artist
 
Monolith Productions
Sr. Software Engineer, Engine - Monolith Productions - #113767
 
Sony Online Entertainment
Brand Manager
 
Crystal Dynamics
Sr. Level Designer
spacer
Blogs

  Why Is My Middleware in Perpetual Beta?
by Dan Goodman on 07/09/09 04:39:00 pm   Expert Blogs   Featured Blogs
1 comments
Share RSS
 
 
  Posted 07/09/09 04:39:00 pm
 

When I was in college I was a double major -- computer science and English.  I know, I know, strange combination.  Anyway, of the few things that people have said over the years that have really stuck with me, one such pearl of wisdom came from an English professor.  He said that a piece of writing can be written and rewritten and edited over and over again forever, but at some point you just have to stop and go with what you have. 

Eventually, a piece of writing stops getting better regardless of your effort.  It's what Economists call the law of diminishing returns.  As additional production effort is applied to a system the output gained from each unit of effort dininishes.  It is sometimes more beneficial to stop the current effort and apply what has been learned to something completely new.  It's a lesson the game industry should learn.

Middleware companies sell complete packages for AI, physics, UI, animation, you-name-it, but what constitutes a "complete package" anymore?  What a lot of middleware companies deliver seems no where near complete, even for the subset of game development technology of which they are supposed to be the leading industry experts.  They release new versions monthly that game studios have to integrate to get lastest features and bug fixes.  Are we game developers, or simply beta testers for middleware companies? 

Many of these companies have great customer service.  They offer support tickets so developers can submit bugs and feature requests, but at this point, they've gone from middleware provider to service provider. 

They customize a solution intended for the masses to the needs of individual companies, when what they should really be doing is applying the effort spent on maintenance of the current version on developing the next version.  After all, once a few games have shipped on the current product, its viability has been proven.  STOP DEVELOPMENT!  Give us what you have right now and put your development effort into making the next version that much better.

Sure, those companies that shipped games probably needed workarounds.  And the other companies out there with games in development have workarounds too.  Some of the currently supported features have unexpected results, or just don't give you what you want. But do you really want to wait around for the "fix" anyway?  Waiting around holds up your production.  You have to remember that you are not their only customer.  It may be months.  It may never come.  It could be the fix that breaks everything else in your game.

You can't rely on it.

So what can game developers do?  Well, the next time you're shopping for a middleware solution for your project, and the salesperson tells you about the cool new features coming in the next or upcoming release, don't plan on getting them in your lifetime.  If you can live without a feature, design your game without it.  If it isn't there now, and you really need it, shop for another solution.  I don't want to be a beta tester any more.  Neither should you.

 
 
Comments

Robert Allen
9 Jul 2009 at 10:46 pm PST
profile image
I saw this in action at a large company in the industry that has vowels in it's name.... The bottom line here is that the game industry lacks the experience and training in producing middleware that one needs to produce good middleware. Producing a library with a C++ interface for your middleware? Don't forget about name mangling. Releasing a library for your new sound/graphics/physics engine? Is it versioned? Is the version hard coded in the code itself so you can use an extraction tool if need be to be SURE what version is compiled into a binary? Finally, are your libs built on dedicated build machines with very tightly controlled access and software upgrade polices, or are they built on Joe-random-programmers desktop?


none
 
Comment:
 


Submit Comment