Racer list after start is preety messed up.
[IMG=http://img440.imageshack.us/img440/3118/lfs1.th.jpg]
Screenshot taken on first lap, after start on (FM) Fox Junkies. As you can see on the map M.Bont is first, D.Williams second (and under them in correct order), but on list they are in the middle.
Situation didnt change even when they start second lap. List was correct after all drivers passed thru start/finish line.

Next race, and everything is OK:
http://img200.imageshack.us/img200/7506/lfs3.jpg

[img=http://img440.imageshack.us/img440/1483/lfs2.th.jpg]
Second image is old "bug" with directon arrow while look left/right

Quote from Simpson :

Racer list after start is preety messed up.

Were you already connected to the server at the start of race, or did you join after the start? I did change something in this area while doing the autocross fixes, so it looks like I've broken something. If you could post a MPR that shows this problem that would be very helpful.

Quote from Scawen :

Were you already connected to the server at the start of race, or did you join after the start? I did change something in this area while doing the autocross fixes, so it looks like I've broken something. If you could post a MPR that shows this problem that would be very helpful.

I were not connected. Joined just after start, 2-3 seconds.

Edit: tried to reproduce it later on South City, but couldnt

Hm talking about start list positions.. we had a weird bug at the start of the race a few months ago... i was using 0.5z but it probably was dedi error because every body had same bug with the position list i have no idea what version of dedi was running.. there is a screenshot http://xs941.xs.to/xs941/09285/lfs_00000170664.jpg i can upload mpr if u like... not sure if it is connected in any way to Simpson bug but if it is, that might help you...

replay (10MB file) http://rapidshare.com/files/254295390/fzr_at_we1r.rar.html

Managed to reproduce it. Only one driver, but i hope it helps.

Quote from Aid :

Hm talking about start list positions.. we had a weird bug at the start of the race a few months ago... i was using 0.5z but it probably was dedi error because every body had same bug with the position list i have no idea what version of dedi was running.. there is a screenshot http://xs941.xs.to/xs941/09285/lfs_00000170664.jpg i can upload mpr if u like... not sure if it is connected in any way to Simpson bug but if it is, that might help you...

replay (10MB file) http://rapidshare.com/files/254295390/fzr_at_we1r.rar.html

already reported

Quote from Simpson :

Managed to reproduce it. Only one driver, but i hope it helps.

Thanks... I've had a look at the replay in Z15 and Z - same thing happens, so at least that does not mean I broke something today. I guess that racer who wrongly appears to be in the lead (although he is last) just crossed the finish line when you joined the host, so your computer thought he was going onto his second lap. I don't know if it's easy to fix but I've made a note to have a look at it.

That has happened to me quite a few times, even in older patches. I always thought its of lag or something.

Dont know how you count this, but maybe you could "fix" position at T1, not only at start/finish.
I know its a minor bug, but good to know that its exists

Except this thing, everything works great.

Quote from Aid :

Hm talking about start list positions.. we had a weird bug at the start of the race a few months ago... i was using 0.5z but it probably was dedi error because every body had same bug with the position list i have no idea what version of dedi was running.. there is a screenshot http://xs941.xs.to/xs941/09285/lfs_00000170664.jpg i can upload mpr if u like... not sure if it is connected in any way to Simpson bug but if it is, that might help you...[/url]

I don't think that is connected. There is a bug in Westhill reversed - the finish line is between grid slots 3 and 4. So I guess that when LFS works out where you are, it thinks the guys in positions 1, 2, and 3 are very far back around the track.

yeah i didn't know about that bug...

Quote from DevilDare :

That has happened to me quite a few times, even in older patches. I always thought its of lag or something.

Same

Quote from Scawen :

I don't think that is connected. There is a bug in Westhill reversed - the finish line is between grid slots 3 and 4. So I guess that when LFS works out where you are, it thinks the guys in positions 1, 2, and 3 are very far back around the track.

Why is the finish line before the marked finish line? Shouldn't it Be at the same spot?

I said it was a bug

A bug means - something is wrong. If it was in the right place, nothing would be wrong and it wouldn't be a bug!

Quote from Scawen :

I said it was a bug

A bug means - something is wrong. If it was in the right place, nothing would be wrong and it wouldn't be a bug!

Yea but, when you created the track, didn't you test it before release? (sorry if i am rude)

Yes, we tested it and we thought "this will be a nice amusing bug" so we left it there.

*Cringe*

Screenshotted, tbh

Quote from Scawen :

Yes, we tested it and we thought "this will be a nice amusing bug" so we left it there.

That reply was just win! Sig quoted!

yes classic

not nearly as amusing as the barrier bug though...

Quote from Scawen :

Thanks... I've had a look at the replay in Z15 and Z - same thing happens, so at least that does not mean I broke something today. I guess that racer who wrongly appears to be in the lead (although he is last) just crossed the finish line when you joined the host, so your computer thought he was going onto his second lap. I don't know if it's easy to fix but I've made a note to have a look at it.

Hmm, I've spotted a weirdness that *could* be Z15 specific...
I've got WE1R replays (of me): an SPR from Z, and an MPR from Z15. I was comparing them the other day and noticed that the finish line (and all splits) are in different places. The finish line isn't where I expected it to be in either case, btw. If this is interesting I can dig up more detail. If it's a simple manifestation of the known bug, then I won't

Quote from SpikeyMarcoD :

not nearly as amusing as the barrier bug though...

It would be nice for that age old little gem of a bug to be addressed whenever we get 0.6a though.

honestly that is the dumbest thing i have ever heard. i have not had any problems with vista 64. this is on a i7 with a gtx 295 and 6 gigs of ddr3 you can't get a faster system with all the vista updates. there is no reason all of a sudden vista changes its mind and keeps me from playing/running/opening a file i was just using.