|
Post by oldnslow on Nov 8, 2009 20:18:59 GMT 2
for the most part, i seemed to be in the wrong place at the wrong time. i missed a bunch of accidents but the last multiple one caused the car to be unable to turn right and barely go straight. with half a lap to return to the pits, i put the very dead lobster to bed.
|
|
Crash
Administrator
Posts: 328
|
Post by Crash on Nov 10, 2009 4:00:41 GMT 2
R.I.P Red Lobster.. Took a helluva beating!
|
|
Crash
Administrator
Posts: 328
|
Post by Crash on Nov 10, 2009 4:02:35 GMT 2
Wonderful race write up Karl! But then I can`t ever recall a poor one from you. Always top notch! Cheers...
|
|
|
Post by BurnOut on Nov 10, 2009 10:04:26 GMT 2
Yes, very nice write up! You did seem to miss my suspension hit in lap 24 tho...I didnt slow down in 2nd stint for no reason Was considering pitting as I had like 30% of wheel damage, but car seemed to be drivable just enough to get it to the end
|
|
|
Post by Administrator on Nov 10, 2009 11:15:30 GMT 2
Yup - missed that. In the race and on the replay ;D Had I known in the race; I'd have tried to close in even faster ... and probably ended up in some wall
|
|
|
Post by Administrator on Nov 12, 2009 1:22:27 GMT 2
ok, guess I figured the cause for some of those lag-caused incidents, the one at 21:01 especially On tracks with tight hairpin turns, where there's opposing lanes only few meters away from each other, NHeat sometimes seems to have trouble judging what lane a car actually is running - in case the client PC is either high pinging or low bandwidth. That can make such cars cause jumping in these areas. That problem is showing really badly if the server is run in thin mode, but seems to show occasionally even in fat mode I only knew Donington to be a track with that problem, but by checking replay it became obvious that Longbeach has same problem in at least 2 areas
|
|