If you run this game on a dual CPU machine you will find the developers left
in a beginners bug of not checking which CPU the QueryPerformanceCounter
call (or whatever it is) was called on. The results is flashing and jumping
occurs - keyboard inputs are echoed erratically etc.
The solution is to use task manager and set CPU affinity to only one CPU -
then the game runs fine.
Another example of not thoroughly testing software. The stuff that passes
for QA in this make a buck economy amazes me. Do they even pay the
developers or just feed them?
Mike
It is already common knowledge that a very small amount of the population
has dual CPU's, and even less then that play computer games. To say they
don't need to throughly test their games on multiple cpu machines is an
understatement. Look at the speed of the game with just one proc. With a 1
ghz PIII, 512 RAM, and a GeF 2 Go, I can run in 1280x1024, 16 bit, with all
the options at medium or full. This is AMAZING. I'm more then happy with the
game, I'm willing to live with a few bugs at the moment, and it is better
then the other crap being released.
-Stuart Becktell
"Mike" <[email hidden]> wrote in message
news:[email hidden]...
> If you run this game on a dual CPU machine you will find the developersleft
> in a beginners bug of not checking which CPU the QueryPerformanceCounter
> call (or whatever it is) was called on. The results is flashing andjumping
Quoted text (12 lines)
> occurs - keyboard inputs are echoed erratically etc. > > The solution is to use task manager and set CPU affinity to only one CPU - > then the game runs fine. > > Another example of not thoroughly testing software. The stuff that passes > for QA in this make a buck economy amazes me. Do they even pay the > developers or just feed them? > > Mike > >Mike wrote:
In today's economy, good developers are too expensive. They send almost
everything off shore to "developers" with next to no experience.
Quoted text (12 lines)
> If you run this game on a dual CPU machine you will find the developers left > in a beginners bug of not checking which CPU the QueryPerformanceCounter > call (or whatever it is) was called on. The results is flashing and jumping > occurs - keyboard inputs are echoed erratically etc. > > The solution is to use task manager and set CPU affinity to only one CPU - > then the game runs fine. > > Another example of not thoroughly testing software. The stuff that passes > for QA in this make a buck economy amazes me. Do they even pay the > developers or just feed them? >
"Bryon Lape" <[email hidden]> wrote in message
news:[email hidden]...
> Mike wrote:
> In today's economy, good developers are too expensive. They send almost
> everything off shore to "developers" with next to no experience.
Yes, ISI who did F1 2002 have no experience before they started to make
games.
They just worked with flight simulators and car-simulators.. and that gives
you no
experience ;) :)
