• Welcome to PiBoSo Official Forum. Please login or sign up.
 
December 09, 2019, 02:08:33 am

News:

GP Bikes beta16b available! :)


Autodromo Enzo e Dino Ferrari "Imola" V1.0 (2 Layouts)

Started by javiliyors, March 29, 2019, 08:46:52 am

Previous topic - Next topic

tzone

Hi,

Great track, I am enjoying it. Thank you.

1 issue:

When lapping the NC layout, lap times are not saved. Only output for lap time is "--". Even when completing a proper lap with no issues.
Lap times do work for the Chicane version though.

Is it only on my machine?

Thanks.

javiliyors

It is possible that you cut some chicane, there are 4 checkpoints in the circuit to avoid cutting them, enter again and complete a lap without cutting anything, it is possible that it was a specific bug of yours.

tzone

Ah, you say 4 checkpoints in the NC version. Now I look inside the rdf file, and I see that num_checkpoints=5. This might be the issue. I will check it when back from work.

num_checkpoints = 5
checkpoint0
{
   long = 537.000000
   left = -6.000000
   right = 7.000000
   penalty = 5.000000
   line = 0
   start = 0
}
checkpoint1
{
   long = 1200.000000
   left = -5.600000
   right = 6.500000
   penalty = 5.000000
   line = 0
   start = 0
}
checkpoint2
{
   long = 2633.916016
   left = -5.000000
   right = 7.000000
   penalty = 5.000000
   line = 0
   start = 0
}
checkpoint3
{
   long = 3172.000000
   left = -7.000000
   right = 7.000000
   penalty = 5.000000
   line = 0
   start = 0
}

javiliyors

July 09, 2019, 09:15:04 am #18 Last Edit: July 09, 2019, 09:41:25 am by javiliyors
Quote from: tzone on July 09, 2019, 08:18:47 amAh, you say 4 checkpoints in the NC version. Now I look inside the rdf file, and I see that num_checkpoints=5. This might be the issue. I will check it when back from work.

num_checkpoints = 5
checkpoint0
{
   long = 537.000000
   left = -6.000000
   right = 7.000000
   penalty = 5.000000
   line = 0
   start = 0
}
checkpoint1
{
   long = 1200.000000
   left = -5.600000
   right = 6.500000
   penalty = 5.000000
   line = 0
   start = 0
}
checkpoint2
{
   long = 2633.916016
   left = -5.000000
   right = 7.000000
   penalty = 5.000000
   line = 0
   start = 0
}
checkpoint3
{
   long = 3172.000000
   left = -7.000000
   right = 7.000000
   penalty = 5.000000
   line = 0
   start = 0
}

I think 4, but not sure. Btw the track nds or ds work fine. Download the tracked and load the rdf and see the checkpoints

Hawk

The check markers are there to make sure you don't cut corners to cheat in your registered lap times and also to implement a penalty time for doing so. If you do cut corners then your lap-time will not register.

It's also possible that you may have missed a sector marker if you have gone off track limits, this will also not register a lap time as well as possibly messing up the whole lap-time recording on the server for sessions. Sector markers on tracks should be of such length that they cannot be missed even due to a crash, but this is something only a modder can implement to make sure these issues don't happen.

As Javi suggests, just ride around the track surface without going outside track surface limits and see if a lap time is shown, this will show you if you have been missing one or more of the check-point markers and therefore forfeiting your lap-time concerned. ;)

Best thing to do to check for these type of issues is to load-up this track in "TrackED" and load in the race data file so that you can visually see all the sector and checkpoint markers to see where these type of issues may occur.  ;) 

javiliyors

Quote from: Hawk on July 09, 2019, 09:41:02 amThe check markers are there to make sure you don't cut corners to cheat in your registered lap times and also to implement a penalty time for doing so. If you do cut corners then your lap-time will not register.

It's also possible that you may have missed a sector marker if you have gone off track limits, this will also not register a lap time as well as possibly messing up the whole lap-time recording on the server for sessions. Sector markers on tracks should be of such length that they cannot be missed even due to a crash, but this is something only a modder can implement to make sure these issues don't happen.

As Javi suggests, just ride around the track surface without going outside track surface limits and see if a lap time is shown, this will show you if you have been missing one or more of the check-point markers and therefore forfeiting your lap-time concerned. ;)

Best thing to do to check for these type of issues is to load-up this track in "TrackED" and load in the race data file so that you can visually see all the sector and checkpoint markers to see where these type of issues may occur.  ;) 

Yes hawk, thanks u!! Better download tracked and see the checkpoints 😉

tzone

Hi,
Thanks for replies guys.

I opened the NC track and track data with the track editor.
There is one checkpoint that has a 0 right-left range.(Please see photo)
Is this why I am "missing" this checkpoint and not saving times?

javiliyors

July 09, 2019, 11:15:16 am #22 Last Edit: July 09, 2019, 11:21:36 am by javiliyors
Quote from: tzone on July 09, 2019, 10:34:10 amHi,
Thanks for replies guys.

I opened the NC track and track data with the track editor.
There is one checkpoint that has a 0 right-left range.(Please see photo)
Is this why I am "missing" this checkpoint and not saving times?


I check it when im at home


Solved: Added fix, thank u tzone.

javiliyors


Hawk

That looks to me like a sector marker you have circled not a checkpoint marker, checkpoint lines are blue not red, or at least they were last time I used TrackEd.  :)

javiliyors

Quote from: Hawk on July 09, 2019, 04:09:20 pmThat looks to me like a sector marker you have circled not a checkpoint marker, checkpoint lines are blue not red, or at least they were last time I used TrackEd.  :)

its in yellow the checkpoints, but i revised the NC track and are wrong. i fixed the checkpoint now in the first post.