• Welcome to PiBoSo Official Forum. Please login or sign up.
 
March 28, 2024, 08:49:50 PM

News:

GP Bikes beta21c available! :)


Default Groove

Started by PiBoSo, November 23, 2016, 01:05:07 PM

Previous topic - Next topic

PiBoSo

November 23, 2016, 01:05:07 PM Last Edit: October 19, 2019, 08:22:34 PM by PiBoSo
There is a little feature that could be useful.

1) Open global.ini ( by default generated in "My Documents"/PiBoSo/GP Bikes/ ) and add the following lines
[edit]
groove=1
2) Ride several laps in testing mode on a track to create the groove ( it's possible to use groove_multiplier to generate it faster )
3) Press left ctrl + g: a file named temp.grv will be saved in the GP Bikes installation folder ( a message should be displayed on screen )
4) Rename temp.grv to track_id.grv ( for example: victoria.grv ) and move it to the proper track folder, with the matching TRP file
5) GP Bikes should automatically read this grv file at track load time
"La perfezione non è il nostro obiettivo, è la nostra tendenza".

PeterV

Question about the groove build up....

Is there a saturation point? by this i mean i can drive 1000 laps, 2000, 9000 etc etc.
Does it keep building or is there a X amount of laps at which it doesn't work anymore?

Im asking because it would be a bummer if i did it al for nothing.

thank you

PiBoSo

Quote from: PeterV on November 26, 2016, 11:00:07 AM
Question about the groove build up....

Is there a saturation point? by this i mean i can drive 1000 laps, 2000, 9000 etc etc.
Does it keep building or is there a X amount of laps at which it doesn't work anymore?

Im asking because it would be a bummer if i did it al for nothing.

thank you

Yes, there is a saturation point.
"La perfezione non è il nostro obiettivo, è la nostra tendenza".

PeterV

thanks, and could you tell us at which point (laps) i reach that saturation point?

PiBoSo

Quote from: PeterV on November 26, 2016, 11:46:46 AM
thanks, and could you tell us at which point (laps) i reach that saturation point?

It doesn't depend on the number of laps.
It depends on the tyre used and the riding style, and the number of times the bike passes on the same point on the track.
With qualify tyres groove is generated much faster, for example.
You can check visually: when a point on the track is very dark, it will not get any more groove.
"La perfezione non è il nostro obiettivo, è la nostra tendenza".

PeterV

oke ty, i noticed quicker build up with qualifying tires indeed.

jors666

Quote from: PiBoSo on November 23, 2016, 01:05:07 PM

There is a little feature that could be useful.

1) Open gpbikes.ini and add the following lines

[edit]
groove=1

2) Drive several laps in testing mode on a track to create the groove ( it's possible to use groove_multiplier to generate it faster )
3) Press left ctrl + g: a file named temp.grv will be saved in the GP Bikes installation folder
4) Rename temp.grv to track_id.grv ( for example: victoria.grv ) and move it to the proper track folder, with the matching TRP file
5) GP Bikes should automatically read this grv file at track load time


I changed gpbikes.ini file, used multiplier groove but
Why doesn't work?
After 30 laps at silverstone no temp.grv file created

jors666

Quote from: jors666 on November 29, 2016, 10:27:05 PM
Quote from: PiBoSo on November 23, 2016, 01:05:07 PM

There is a little feature that could be useful.

1) Open gpbikes.ini and add the following lines

[edit]
groove=1

2) Drive several laps in testing mode on a track to create the groove ( it's possible to use groove_multiplier to generate it faster )
3) Press left ctrl + g: a file named temp.grv will be saved in the GP Bikes installation folder
4) Rename temp.grv to track_id.grv ( for example: victoria.grv ) and move it to the proper track folder, with the matching TRP file
5) GP Bikes should automatically read this grv file at track load time


I changed gpbikes.ini file, used multiplier groove but
Why doesn't work?
After 30 laps at silverstone no temp.grv file created


OK OK
only works at not dns tracks...

Alby46

Still riding a 50cc, but enjoying it :)