> Marc has a good point here. I am presently working as a Quality Software
> Engineer. The project I am working on I cna say we have bugs like every
> other project has. You have to weight the bug priorty (does it crash the
> game or is it a minor nuisance) against the cost of not shipping. For
> example: If the bugs are a minor nuisance and the user can get around
> them real easy than the product should be shipped. Fix it during the
> maintenence cycle and release a upgrade or patch. Now if there are 100
> minor nuisance bugs and it hurts the users confidence in the software
> than yes hold up the shipping for that product until the number of
> nuisance bugs are reduced.
> I am a N2 user and looking at the product as a Software Quality Engineer
> I can say I believe papyrus did make the right decision. This is only My
> Humble Opinion.
Yeah but from a multiplayer view of N2 there are a 100 little bugs. So then N2
fails under your criteria.
Latest bugs found over x-mas:
Both Michigan and Pocono are unplayable in a LAN enviroment AFAIK. For some
reason the game will crash about 10 seconds into the race. Practive works fine
but the race is not. I still have yet to try every course multiplayer so I'm
not sure if there will be others or not. If somebody has these working please
correct me so I can look at my systems more carefully.
One's that works:
Charolette
Rock
Bristol
Talladega
Martinsville
Q.B.M.