Forums

I've been playing this track some lately and I like it a lot. There are a few issues I'd like to point out and hope to see fixed.

First off, the first time I make it all the way around the track, the lap timer is not triggered. It does seem to trip the second time I cross it. Maybe it's backwards?

Next, the track has some strangeness going on in the area I'll call the "back straight". By this I mean, the long straight section just before getting to the straight section that has the starting line. There are two areas over the track that look kind of funny. I'll upload some screenshots and put them here shortly.

thelusiv Wrote:First off, the first time I make it all the way around the track, the lap timer is not triggered. It does seem to trip the second time I cross it. Maybe it's backwards?

i just gave it a try and the lap timer worked just fine. maybe you missed the second lap sequence.

thelusiv Wrote:Next, the track has some strangeness going on in the area I'll call the "back straight". By this I mean, the long straight section just before getting to the straight section that has the starting line. There are two areas over the track that look kind of funny. I'll upload some screenshots and put them here shortly.

post a picture, i didn't really see anything strange.

--alex--

@thelusiv

Irritated by the shadows?

Here's the issue on the back straight, it's right before the last turn:

thelusiv Wrote:Here's the issue on the back straight, it's right before the last turn:

i don't see that:

--alex--

I don't see that problem either.

I did have trouble getting the lap to register. I may have gone off, though... I'll try it again.

joevenzon Wrote:I did have trouble getting the lap to register. I may have gone off, though... I'll try it again.

we might want to rethink the lap sequences anyway. there are two problems with the current scheme: one, if you go off track at the lap sector the lap doesn't register. maybe we can extend the lap sector on either side of the track somehow. and two, if you go through the pits the lap doesn't register either (most of the lap sequences coincide with the starting line which is next to the pits). looks like we need some kind of special lap sequence to mark the pits as well.

--alex--

And another problem... I looked into the problems I was having on Sepang a bit more. It seems like sometimes I can trigger the lap, sometimes I can't. I stay on the track the whole time. After looking at the track in the track editor, I notice that the sector patch associated with the start of the lap is very narrow. If I switch the patch to a wider one, then it works fine. Also, if I drive slowly, I can trigger the sector patch more reliably. So, I think if the car is going too fast, and the patch is too narrow, it can get missed.

Ideas? Using bounding boxes for the sectors would work, but would require definition for each track (maybe as a 3D model?). Another (easier) option would be to treat any patch between two "sector" patches the same as a sector patch, so if you missed the sector patch but hit the one after it (or several patches after it, in the case of a pit lane) it would, at that point, register the new sector/lap. Thoughts?

joevenzon Wrote:So, I think if the car is going too fast, and the patch is too narrow, it can get missed.

i wonder if this is related to going through collide-able objects when the car is moving fast.

--alex--

Alex, I can't reproduce it again either. I'm not sure what causes this, but at times I see polygons in the wrong places on the track and sometimes on the car... That screenshot was a more extreme example.

thelusiv Wrote:Alex, I can't reproduce it again either. I'm not sure what causes this, but at times I see polygons in the wrong places on the track and sometimes on the car... That screenshot was a more extreme example.

i've seen glitches like this before but they usually go away if you restart the game (the whole game not just the race). there is probably some memory being overwritten or, more likely, some variable is not initialized and gets assigned random values (most of the time zero i guess)

--alex--