Wrong "Cut Track" warning

Discussion in 'Track Modding' started by rigodon, Mar 19, 2014.

  1. rigodon

    rigodon Registered

    Joined:
    Dec 26, 2012
    Messages:
    218
    Likes Received:
    15
    Hi, we're using Melbourne DRS 1.01 track in our league and some drivers (some, not all :confused:) get a cut track warning (and a penalty in race) just by touching the kerbs in turn 4. I edited the AIW and put a cut area 60 meters out of the road. I thought that change should actually disable cut track checking, but same thing still happens. :confused:

    Is there any other way of disabling cut track checking apart from running with "flagrules=none"?
     
    Last edited by a moderator: Mar 19, 2014
  2. canastos

    canastos Registered

    Joined:
    Dec 23, 2011
    Messages:
    483
    Likes Received:
    2
    Try adding this line to GBD file:
    After that you can save an alternate Melborune.mas file and repack it as an update

    It worked for me

    byyyyyyyye
     
  3. rigodon

    rigodon Registered

    Joined:
    Dec 26, 2012
    Messages:
    218
    Likes Received:
    15
    Thanks, I'll try :)
     
  4. KAMPFBIBER81

    KAMPFBIBER81 Registered

    Joined:
    Dec 12, 2012
    Messages:
    34
    Likes Received:
    4
    We had the same problem, we found out that the sim throws a Cut Track Warning when you are close to an opponent and you can close the cap in turn 3-4. Even when you are in the middle of the track.

    Also, we still had the warnings after disabling the flag rules, btw

    We had to switch to the other version of Melbourne.
     
  5. rigodon

    rigodon Registered

    Joined:
    Dec 26, 2012
    Messages:
    218
    Likes Received:
    15
    Thanks for the answer. What's the other version? 0.55?
     
  6. rigodon

    rigodon Registered

    Joined:
    Dec 26, 2012
    Messages:
    218
    Likes Received:
    15
    If it's something related to saving time, does someone know the proper use of these GDB parameters?

    CutTimeRatioMax = 0.95 // Start penalizing even if we lose 5% of time
    CutTimeRatioPenalty = 0.40 // Penalty for fraction of time savings
    CutSecondsSaved = 0.675 // Penalty for each second saved
     
  7. KAMPFBIBER81

    KAMPFBIBER81 Registered

    Joined:
    Dec 12, 2012
    Messages:
    34
    Likes Received:
    4

    Melbourne beta 0.01, the curbs are green/yellow

    We had the issue with the one with red/white curbs (I think it was 0.55)
     
  8. rigodon

    rigodon Registered

    Joined:
    Dec 26, 2012
    Messages:
    218
    Likes Received:
    15
    Ok, we're using 1.01, which is an evolution of 0.55
     
  9. rigodon

    rigodon Registered

    Joined:
    Dec 26, 2012
    Messages:
    218
    Likes Received:
    15
    Well, finally it's working with these ridiculously high values in the GDB:

    CutWarningThresh = 10.0 // Threshold for warning (or disallowance of lap)
    CutStopGoThresh = 10.0
    CutLeavingThresh = 10.5 // Threshold for leaving track
    CutTimeRatioMax = 9.95 // Start penalizing even if we lose 5% of time
    CutTimeRatioPenalty = 9.40 // Penalty for fraction of time savings
    CutSecondsSaved = 9.675 // Penalty for each second saved
     
  10. Juergen-BY

    Juergen-BY Registered

    Joined:
    Jun 16, 2012
    Messages:
    3,089
    Likes Received:
    440
    Where into the GDB i have to put these lines?

    //Edit: is working, but same result, if you running with "flagrules=none"...

    //Edit2: AIW Cutting Line reworked, no more cutting warnings on the curb. Also, Turn 9, there was no Cutting warning, changed ;-)
     
    Last edited by a moderator: Oct 2, 2014
  11. Lazza

    Lazza Registered

    Joined:
    Oct 5, 2010
    Messages:
    12,382
    Likes Received:
    6,600
    That's pretty much exactly what we do to avoid all sorts of erroneous cut track warnings/penalties - set every single track cut segment to 60 metres. Could go and bring them back in on actual corners where cutting is an issue but since we're only doing league races and have other ways of catching/penalising drivers we just leave it. Haven't had any silly warnings since. Keep in mind leaving even a single 'line' the way it is can be enough for those errors. Personally I use a regular expression search/replace to change the two cut track values of every single wp_dwidth line to 60.0. Easier than the AIW editor for mass changes.
     

Share This Page