
This post has been edited 1 times, last edit by "decay90" (06.07.2009, 18:58)
Quoted
I mean if i was a developer, I wouldnt release a game with bugs like AA3 has
) because that's what the contractor wants.
Quoted
If I was a builder, and I was given a house to build, I'm fairly sure I could say to the contractor, we need x amount of time and x amount of builders. The contractor would then negotiate how they could achieve this with less time and less builders to save money. But eventually, both parties would come to an agreement and the house would stand (but maybe having cheaper roofing) because that's what the contractor wants.

Quoted
and I still got my original questions, they didn't plan to release a bug infested game did they
maybe devs stuffed it up when they found out their jobs were going lol![]()
Quoted
maybe they can get better ones
Quoted
AA2 still has bugs and ive seen patches make things worse and have another patch days later
Then I really suggest you find a job in construction, cause you clearly don't understand the major difference, which makes it impossible to compare building a house and making a game. Building a house is a static process, which follow a clear and defined blueprint. Whereas coding a game is a dynamic process which changes all the time - you can't make a deadline for a game; what you can do, is make hallmarks along a line where you hope to reach a certain point in the coding, and then you decide when the next hallmark should be.I've read all that, but I don't understand how they could stuff it up so much.
If I was a builder, and I was given a house to build, I'm fairly sure I could say to the contractor, we need x amount of time and x amount of builders. The contractor would then negotiate how they could achieve this with less time and less builders to save money. But eventually, both parties would come to an agreement and the house would stand (but maybe having cheaper roofing) because that's what the contractor wants.
In aa's case it seems that the game doesnt "stand" and I am fairly sure that's not what the US ARMY wants. Why didn't they put in the intial build, less features and less bugs!? Kinda doesn't make sense to me...
either 1. The dev's are shit and didn't do their job.
or 2. The US ARMY wanted a commercial quality game at half price.
O and I still got my original questions, they didn't plan to release a bug infested game did they :S I was hoping patches would be more content... not bug fixes...
Pye, just want to thank you for the hard work you put in. The fact that you are giving out information is very welcome too. I'm just a little worried about the future of this game after reading your posts. There must be some high up army idiot who realises that all the hard work and money put into the project are wasted if it isnt done the RIGHT way all to the end?
Hope you guys land on your feet after losing your job.
honestly yea you guys are right no game comes with out a few bugs thats expected but when its that bad theres no way in hell it should of gotten released i understand its nothing the devs could of done but damn, i mean around 10,000 (not sure of the exact number) players came on the first few days to see what AA3 was about and now 2/3 of them not even bothering with it anymore... If that was me i'd copy the code for the game then put a virus in the network taking out all the computers, If they want the game back demand more time to do it right lol
Quoted
When you kill 6 people in Unreal Tournament it's "Monster Kill", In Quake3 it's "Excellent", in America's army it's "Kicked by Admin"
My friend, u clearly have no idea what construction is... If u think it's static process, u r quite wrong. Did u ever think how does weather affect building, or how many differend contractors u have to syncronize on a project in the same time, how if one of them is late u get a domino effect?Then I really suggest you find a job in construction, cause you clearly don't understand the major difference, which makes it impossible to compare building a house and making a game. Building a house is a static process, which follow a clear and defined blueprint. Whereas coding a game is a dynamic process which changes all the time - you can't make a deadline for a game; what you can do, is make hallmarks along a line where you hope to reach a certain point in the coding, and then you decide when the next hallmark should be.
© 2010 Battletracker.com
..:: Disclaimer - Forumrules - Contact ::..
