brianleeprice -> (10/14/2001 10:34:00 PM)
|
quote:
Originally posted by john g:
I am one of those who got the beta to test since I was one who got hit with the yugo early on. Remember this is not a finished patch, this was a unstable test version to be used for sharing the save games with Matrix in tracking down why it happened. In case you haven't noticed there have been a relative lack of posts by Matrix employees the last week or so. They are most likely finalizing the v7 release, not passing out more beta versions. Do you want to start with a beta just to have to start over again when the real release gets out?
My beta release is 7.0b6, I have seen mention of 7.b11, I have no idea what version the final release will be derived from. My reports to the other members of the beta team have slacked off, but I still test things off and on, just to see what is different from previous versions (I started playing back with v1.0).
Realize that part of the delay with v7 is getting it to work with the third mc, since there were issues with landing craft. When all three mc are working fine then I think you will see v7.
I know to get the enjoyment out of mcna I'll have to restart when v7 gets released. Do you want to have to do the same?
Another consideration is that if you have v7beta installed you are pretty much cut out of the pbem or online battle community, with 6.1 you can at least fight others while you wait to do the campaign. thanks, John.
I've been making my living as a programmer since the late '80s when I switched careers so yeah I well understand the nature of beta versions.
As far as the beta version goes I would prefer the b11 but the b6 version would be one whole heck of a lot better than what I have now. I wouldn't be starting MC DF over when release 7 comes out unless there turned out to be other cat 1 or showstopper type bugs in the beta affecting MC DF.
Since I have plenty of HD space, it should be quite easy to install and run multiple versions of SP:WAW so I'm completely unconcerned at the prospect of having a v6.1, a 7.11b, and a 7.x release versions all installed on my machine, using each for a different purpose. In any event I'd need to do so for any ongoing pbem games when 7 came out unless it had 100% backwards compatibility - even then it's unlikely you'd want to switch horses in mid-game. I've been through similar situations with other multiplayer strategy/wargames over the years and have used the multiple installation version solution many many times.
I'd really prefer access to 7.11b, albiet with appropriate warnings such as you've given, and the opportunity to make my own informed choice on the upgrade path to follow. As it stands now I have an unplayable game that I've purchased and no certain knowledge of how long a wait will be required for an 'officially approved' fix.
Hopefully as Matrix matures as a company they won't make this type of PR fubar any longer. If you ship a product with serious bugs, give the customer the option to make an informed decision about using beta patches as a temporary fix until the final fix is available and make those beta patches publically available as promptly as possible since by shipping a product with bugs the customer is turned into an involuntary beta tester anyhow.
That said, as a longtime member of a very successful online strategic gaming community, I'll say this - regardless of the actions of Matrix as a company - what makes or breaks a good game is its online community. It can either make things easy and enjoyable for newcomers, be quick to help fellow gamers with problems, or become stagnant and unresponsive.
Games always have bugs, developers are always under pressure, and companies are always understaffed - if the game's online community picks up the slack, providing guidance and assistance to newcomers and fellow gamers, a game will be far more successful and the issuing company will be far more likely to pay attention to the needs and desires of the community due to its ever increasing buying power. Simple economics.
[ October 14, 2001: Message edited by: Brian Price ]
|
|
|
|