O
old.Ego
Guest
Snow Leopard (Developer) - 04:55pm Apr 3, 2001 PST
Associate Producer
Myself and Hexabolic spent a good part of today reading nearly every post from people having problems in the game on this and other forums.
Our intent was to look for trends that would allow us to identify those issues that need to be looked at first. Notice how I said looked at, not fixed. There are just too many variables to automaticly call an issue a bug. Once our QA guys take a look, run some tests and say "Yep, it's a bug", we can then identify the problem and fix it. What I mean by that is, there are about 75,000 different machine combinations of hardward/drivers/OS, such that many problems may in fact be a result of some combination we were unable to anticipate or test for. There may be combinations that cause problems not unique to Tribes 2. For example there are several problems caused by Win2000 that have effected other games, not just ours, that we can't do anything about. Ultimately, Microsoft is the only person who can fix those problems.
Here are what we found to be some common issues:
1) Dual CPUs and SB Live causing problems
2) A memory footprint issue
3) UE is still showing up on some systems
4) We are looking at a possible issue with Athlon/AMD systems.
5) Patch freezing at the Audio.vl2 file
6) Popping/Hissing-Miles Sound Drivers
Hexabolic and I did not have the time to address each person who wanted a responce from the DEV team, sorry. We are reading what you are saying and reacting to your concerns however.
So many people seem so focused on the negative and overlooking the positive. Almost 40,000 new accounts, last time I checked almost 700 servers up and running, reports from some guys in Australia who had 88 people in a server playing...the list goes on.
Rest assured we are aware of these issues and taking action where we can.
Last sentence makes me laugh! I have "issues" with points 1 and 6. I wont bother holding my breath for a solution
Associate Producer
Myself and Hexabolic spent a good part of today reading nearly every post from people having problems in the game on this and other forums.
Our intent was to look for trends that would allow us to identify those issues that need to be looked at first. Notice how I said looked at, not fixed. There are just too many variables to automaticly call an issue a bug. Once our QA guys take a look, run some tests and say "Yep, it's a bug", we can then identify the problem and fix it. What I mean by that is, there are about 75,000 different machine combinations of hardward/drivers/OS, such that many problems may in fact be a result of some combination we were unable to anticipate or test for. There may be combinations that cause problems not unique to Tribes 2. For example there are several problems caused by Win2000 that have effected other games, not just ours, that we can't do anything about. Ultimately, Microsoft is the only person who can fix those problems.
Here are what we found to be some common issues:
1) Dual CPUs and SB Live causing problems
2) A memory footprint issue
3) UE is still showing up on some systems
4) We are looking at a possible issue with Athlon/AMD systems.
5) Patch freezing at the Audio.vl2 file
6) Popping/Hissing-Miles Sound Drivers
Hexabolic and I did not have the time to address each person who wanted a responce from the DEV team, sorry. We are reading what you are saying and reacting to your concerns however.
So many people seem so focused on the negative and overlooking the positive. Almost 40,000 new accounts, last time I checked almost 700 servers up and running, reports from some guys in Australia who had 88 people in a server playing...the list goes on.
Rest assured we are aware of these issues and taking action where we can.
Last sentence makes me laugh! I have "issues" with points 1 and 6. I wont bother holding my breath for a solution