PDA

View Full Version : 2019 Season 3 - Release Notes [2019.06.03.01]



z4driver
03-06-2019, 08:34
I've just started using CrewChief and have found it a great help. I used it for the first time in anger for last weekend's 24 Hrs of Le Mans. Not only was it informative it was atmospheric as well.

Just wanted to check if any of the spotter/message changes in the latest build (2019 Season 3) will have any impact on CrewChief. I've quoted the relevant bit below:


Spotter

- A significant portion of the base spotter audio has been re-recorded for improved consistency and variety.

- A variety of new spotter calls have been added, including:
- - SPCC_GWC_EXTENDED = Lets you know whether this caution period will extend the race in order to end under the Green-White-Checkered Flag.
- - SPCC_GWC_FINAL = Lets you know that this is the final caution period that will extend the race in order to end under the Green-White-Checkered Flag.
- - SPCC_FUEL_1LAPS = Called when you only have one lap of fuel left.
- - SPCC_MINUTE & SPCC_SECOND = Called for labeling lap time lengths (minute & second).
- - SPCC_MINUTEPL & SPCC_SECONDPL = The plural forms of the above (minutes & seconds).
- - SPCC_1TOGREEN_RESTART & SPCC_GOGREEN_RESTART & SPCC_GREEN_RESTART & SPCC_NOGREEN_RESTART & SPCC_PACEIN_RESTART = Optional spotter calls that are triggered during race restarts. If the flags are not filled in then iRacing will default to the non-restart variations of these spotter calls (i.e. SPCC_NOGREEN).

- The calls, 'SPCC_1TOWIN' (one lap to win) or 'SPCC_1TOGO' (one lap to go), will now always be called when applicable for time-based races.

- Our online guide for how to develop new spotter packs has been updated.
- - See this thread to learn more: members.iracing.com/jforum/posts/list/3646900.page

- A great many improvements have been made to our spotter calls to aid in translation.
- - All existing spotter packages will need to be updated to fit the new form!
- - - You can read about these changes here: members.iracing.com/jforum/posts/list/100/1938030.page#11513531

- Translation Improvements:
- - Support has been added for more plural forms of spotter messages.
- - - We now optionally support zero, one, two or many items. This requires a renaming of the messages, previously the default form was singular, and we marked the plural case with a PL at the end. Now the default form is the plural (many) case and we mark the 0, 1, 2 cases with a _P0, _P1, or _P2 at the end of the message. If your language does not use a particular plural form you can NULL out both the string and wave file and we will ignore that form. For example, in English, we only need the _P1 and default forms to handle 1 and many.
- - All multi-part messages no longer share any message id's.
- - - This allows you more freedom to rearrange the sentences as needed or NULL out a part you do not need. For example, the messages SPCC_PACE_PASS <num> SPCC_PACE_PASS_PT2 says 'pass the' <num> 'car' in English, but could be reorganized to say 'pass car' <num> NULL for another language.
- - Numbers now support a SPCC_Nx_EQ form that is called if the number is an exact match.
- - - For example, this allows us to use two different forms of the word 'one', as in 1, 21, and 301.
- - Support for an optional call SPCC_DECIMAL has been added.
- - - When filled in, this message will be called at the end of a decimal number, used to say 'decimal' after reading a decimal number if that is what is expected in your language.
- - An optional call, SPCC_AND_TEN has been added that when filled in will reverse the tens and ones place.
- - - For example, the number 321 would be called out as SPCC_N300 + SPCC_N1 + SPCC_AND_TEN + SPCC_N20, to say 'three hundred one and twenty'.

- Fixed an issue with the "fuel left" calls triggering when not needed.