Holeshot Gate

[checkerz]

JLV,

Any chance we could get it so we could set which timing gate is the recorded Holeshot Gate in the Timing Gates file?

I would like to make hte "official" holeshot on the first jump, but don't want to allow people to cut the first turn(s) before getting there.

[James Cryer]

Wouldn't 0 or 1 be the holeshot gate?

[tyskorn]

It's the first gate in your 'First Lap' line of the timing gates, so if you wanted it to be 1, but also wanted a gate 0 before that to prevent any cutting before getting to gate 1, you wouldn't be able to have 1 be the holeshot gate, because 0 would be the first one in the line.

I think this would be a good thing to implement.

[jlv]

The stats scripts use the second gate for the holeshot, so you get one gate for the first turn. I've been meaning to make it possible to use a different gate though.

[checkerz]

The stats scripts use the second gate for the holeshot, so you get one gate for the first turn. I've been meaning to make it possible to use a different gate though.

It would be extremely helpful. For example, SX Open nights 1 and 2, the holeshot wasn't until the first jump; however, there were 2 turns and a straight before. You'd be leaving one turn wide open for cuts - as well as annoying being faced in a weird direction in a first turn pile up, if it wanted to use the 2nd gate each time.

[barrington314]

The stats scripts use the second gate for the holeshot, so you get one gate for the first turn. I've been meaning to make it possible to use a different gate though.

Has this changed yet?

[iNoScope]

The stats scripts use the second gate for the holeshot, so you get one gate for the first turn. I've been meaning to make it possible to use a different gate though.

Has this changed yet?

Way to bring up an old topic guy!!!

[wheels1758]

Yes, kinda.

You have to do it in the .trackinfo file. I believe you add

Code: Select all

holeshotindex=x

where x is the zero-indexed number of the gate you want to be the holeshot (default is 1, meaning the SECOND gate the riders cross).

[pablius]

I think that I don't understand you wheels

IMO, sometimes we don't want to put the holeshot TG in the second gate the riders cross, we need to put it the third one or even further, because the first turn is too long and if you put just 2 TG, people could cut the track.

[AWood]

Yes, kinda.

You have to do it in the .trackinfo file. I believe you add

Code: Select all

holeshotindex=x

where x is the zero-indexed number of the gate you want to be the holeshot (default is 1, meaning the SECOND gate the riders cross).

this is correct. i totally forgot you told me about this

[wheels1758]

I think that I don't understand you wheels

IMO, sometimes we don't want to put the holeshot TG in the second gate the riders cross, we need to put it the third one or even further, because the first turn is too long and if you put just 2 TG, people could cut the track.

The only way to do it is in the trackinfo file, which really is controlled by whoever runs the server.

If you want the holeshot to be the 4th gate the riders cross (for example, they go across 0, 1, 2, and 3 is the holeshot), whoever makes the trackinfo file (for the server) just has to put

Code: Select all

holeshotindex=4

in the trackinfo file for the correct rider to be awarded the holeshot in the results.

[wheels1758]

err, holeshotindex=3, darn zero based indexing...

[pablius]

aaammmmm thank you wheels...now I understand you.

I think that the script would be more useful if it were in the track folder...