Page 14 of 14 FirstFirst ... 4121314
Results 131 to 135 of 135

Thread: How to collect track Corner Data

  1. #131
    Quote Originally Posted by Tim Holmes View Post
    Oh, is that where the "Theres a wreck in xxx comes from?"

    correct - that's how CC knows how to call certain track area.

  2. #132
    Junior Member
    Join Date
    Feb 2023
    Posts
    4
    iRacing Tsukuba 2000 Full
    (tsukuba 2kfull)
    Attached Files Attached Files

  3. #133
    Junior Member
    Join Date
    May 2023
    Posts
    2
    Hello,

    with iRacing's Ring 24h coming up, here are landmarks for the iRacing Nordschleife and Gesamtstrecke variants.
    trackLandmarks.json

    I went with putting Klostertal after Mutkurve, since Mutkurve is in the middle of the Klostertal section and the Klostertal bends leading up to Mutkurve are less significant.
    I've included the start of Döttinger Höhe straight and Tiergarten as per the signs because there is CrewChief audio for it, although these sections are not turns.
    T13 (onto Nordschleife), Sabine-Schmitz-Kurve (ex Nordkehre) and Posten 147 (uphill to Hohe Acht) don't have audio and were left out.

    The measurements for the 73 turns as per the Nurburgring website and the Nordschleife-erfahren track guide with 33 lefthanders and 40 righthanders, and the offsets for stitching the track variants together are saved in a Google Sheet:
    https://docs.google.com/spreadsheets..._vykGWfdlfGWIg
    Last edited by CT128; 10-06-2023 at 16:28.

  4. #134
    Junior Member
    Join Date
    May 2023
    Posts
    2
    Hello,

    the iRacing version of "Sebring Club Course" currently has its landmarks listed under "sebring club course" (with three spaces, which the forum won't show) instead of "sebring club" (with one space).

    Here is a list of the iRacing tracks that have CrewChief landmarks, if anyone is curious.
    https://docs.google.com/spreadsheets...fvid=440170382

    barber full
    barcelona gp
    bathurst
    belleisle
    brandshatch grandprix
    brandshatch indy
    charlotte 2018 2019 roval
    daytona 2011 road
    donington gp
    donington national
    hockenheim gp
    hungaroring
    imola gp
    knockhill international
    lagunaseca
    limerock 2019 classic
    limerock chicane
    limerock full
    montreal
    monza full
    mosport
    okayama full
    okayama short
    oschersleben gp
    oulton fosters
    oulton international
    oulton inthislop
    oulton islandhistoric
    phillipisland
    roadamerica full
    sebring club
    sebring international
    spa combined
    spa up
    spielberg gp
    tsukuba 2kfull
    zandvoort grandprix
    zolder gp


    For NASCAR ovals, I've collected the landmarks data.
    trackLandmarksData.json

    atlanta quadoval
    atlanta 2022 oval
    bristol
    bristol dirt
    bristol dirt 2022
    bristol fullpit
    california oval
    charlotte 2018 oval
    chicagoland
    darlington
    daytona oval
    daytona 2011 oval
    dover
    gateway oval
    homestead oval
    homestead ovalindy
    indianapolis oval
    indianapolis ovalindypit
    indianapolis 2022 oval
    iowa oval
    irp
    kansas oval
    kentucky oval
    kentucky 2020 oval
    lacoliseum
    martinsville
    michigan
    michigan 2018
    milwaukee
    nashvilless
    newhampshire oval
    northwilkesboro
    phoenix oval
    phoenix 2021 oval
    phoenix 2021 ovalopen
    pocono oval
    pocono 2016
    rockingham oval
    richmond
    talladega
    texas oval
    texas 2020 oval
    vegas oval


    For some odd car merely leaving the pits, there may sometimes be a call due to "an incident in <landmark>". I take it CC was unable to identify the car by its race position, although it has been set up to and successfully identifies the cars in actual accidents.

    Therefore, when CC updates its race position for that car that has left the pits, it will seem as if the car has lost places, triggering the call. It could be something like the position changing to 12 from -1 or 0. (I've read the comments in the code that say the data by iRacing can be inconsistent. I haven't been able to spot that visually; it would be a split-second glitch.)

    • The bug requires CC to have been running for a few minutes already; it's not instantaneous.
    • It's not sensitive to the distance the car has moved.
    • Increasing the announcement delay hasn't helped either. In one case, the call shifted to one of the cars behind.
    • Removing the landmark did work.

    Road courses with short distances between the pit exit and a landmark might also be affected, but I haven't tested that.

    Race positions in iRacing are updated as cars claim their positions in crossing the start/finish line; race positions aren't being updated continuously around the track. I guess that means the data is less useful for incident calls to begin with.

    Easy fix for the bug could be to have an option to disable the loss-of-position check in iRacing?
    Alternatively, the incident call could be suppressed unless the car's race position has been identified by CC.

    If you need me to put a note on the Gitlab page, please let me know.

    Thank you, CrewChief team, for your great work!
    Last edited by CT128; 10-06-2023 at 16:55.

  5. #135
    1. Collecting Corner Mapping Data:

    Version 4.8.2.0 of Crew Chief or later is recommended.
    The aim is to map corners, not straights, for accurate results.
    Define a clear turn-in point and corner exit for each corner.
    Begin-distance: Your typical turn-in point.
    End-distance: Point where your wheels are nearly straight.
    Some corners might not have a clear transition; use judgment.

    2. Setting Up Recording:

    Assign two buttons for recording:
    One for starting/stopping recording ("Start / stop track landmarks recording").
    One for adding start/end point ("Add Start / end track landmark").
    Start a practice session and wait on the track.

    For automated data enrichment, follow the steps below:

    Collecting Corner Mapping Data:

    Version 4.8.2.0 of Crew Chief or later is recommended.
    The aim is to map corners, not straights, for accurate results.
    Define a clear turn-in point and corner exit for each corner.
    Begin-distance: Your typical turn-in point.
    End-distance: Point where your wheels are nearly straight.
    Some corners might not have a clear transition; use judgment.

    Setting Up Recording:

    Assign two buttons for recording:
    One for starting/stopping recording ("Start / stop track landmarks recording").
    One for adding start/end point ("Add Start / end track landmark").
    Start a practice session and wait on the track.
    Last edited by thomas.stevens; 25-08-2023 at 13:29.

Page 14 of 14 FirstFirst ... 4121314

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •