Probably joined a older server and someone in there had a vob mod. I've noticed that apparently some vobs still work telling from the messed on skins i see in z30.
Dave, he have a legal s2 account ( Shadowww ), but his s2 acount in the forum was banned permanently, still he can post pics or whatever with s2 content
Initially, in the SetUp (shift-P), I selected 25% of fuel and 30% for the next pit stop.
Race started and I was forced to make a pit-stop at lap1.. so I changed Pit instructions (F12) to no additional fuel (0%) before entering pit-lane.
I saw no message of refueling (may be it appeared) but the car got 30% of additional fuel. I did 38 laps at so4r with FBM without pitting, so the fuel was added for sure.
I don't know if this is specific to Z30 and Z31, but I'm almost sure that some one else would had noticed it if present in Z28.
I don't remember my remaining unlocks, thats why I don't try to repeat it with Z28.
If any additional info is needed, don't hesitate to contact me.
raftor
I don't think it is a networking problem, because the car's physics runs locally, it shouldn't be affected by dropped packets or anything like that. And they weren't near enough to another car to suggest that another car's lag was a likely cause.
I guess, and I hope, that this was just a problem with the Z30 collision system, something like the Fern Bay gantries (which, unlike these, were easily reproducable).
I haven't heard of any false collisions with objects or falling through the road in Z31. I found a genuine cause for the Fern Bay type of false collisions in Z30, detected and eliminated them in a way that seems clean and good, so I hope these are gone now.
When you select an open rallycross config (e.g. FE6X) and a car with rallycross tyres, a message comes up that you are using rallycross tyres on road track. I think those blue messages should not be displayed after selecting an open config.
And 2nd, you can select an open config in hotlap mode. Even if you cannot do anything on them, it's logical to not enable them in hotlap mode.
I was was just guessing on it being network based by the problem appearing during multiplayer only. I have another possible theory though, and that is related to memory. Is the track completely loaded into memory or streamed? I ask because one of the reports seemed coincidental with other pc activity. My observations (which I dismissed because I was already aware of it) is that some skipping can occur when the machine is under pressure, though nothing as severe as the reports. This seems to happen around the track texture joins, and I'm unsure if this coincides with a track surface join. It may just be a result of what I was doing at the time, but could paging also be a possible culprit? I'm talking a local MP session here and prior to Z30. My remedy is to make sure to close any unneeded background process, which is often stated by most programs, and common sense anyway. More conjecture I know, and this doesn't require a response as I understand you are already busy.
I've played around with the open layouts quite a lot locally. The gantry problem is definitely fixed in both SP and MP for me, and the only possible related issue is the floating/beaching in the gravel trap opposite the new loop at Fern Bay as reported by others.
