Page 1 of 4 123 ... LastLast
Results 1 to 10 of 35

Thread: Release Candidate

  1. #1

    Dev Team Member

    Administrator
    Seven Smiles's Avatar
    Join Date
    Jan 2018
    Posts
    286

    Release Candidate

    Release Candidate 4.18.2.1




    Note that this deliberately uses a fresh set of settings and installs in a separate folder so it doesn’t interfere with the release version.








    Le Mans Ultimate added, like the game itself it's Early Access and some features don't work.








    Speech Recognition Improvements




    Settings have been added that allow the user to disable all unused speech commands, improving the recognition accuracy for commands that you actually use, see:
    - Identify opponents by driver name
    - Identify opponents by race position
    - Identify opponents by relative race position
    to disable some of the worst offenders.




    It is now possible to remove entries from the `speech_recognition_config.txt` file, located in the installation directory, improving the recognition accuracy of what remains. Note that if you remove them from this file, but have a user-level file in your documents folder, the commands will continue to be available.




    Don't forget to read the FAQ on speech recognition to get the most out of CrewChief https://mr_belowski.gitlab.io/CrewCh...nTraining.html and in particular do not forget to set these accordingly:
    - Prefer Windows speech recogniser
    - Speech recognition country
    noting that if you need to change the audio input device you will need to use naudio (and likely match the sampling rate to your microphone).




    If you still encounter problems, make sure to enable "Write speech recognition debug data" and listen to your WAV recordings to get an understanding of what CrewChief is hearing. If it is loud and clear, that's when it starts to be a recognition problem rather than a hardware setup problem.




    If your microphone is too quiet and the Windows mixer is unable to reach the levels you need, consider installing a software booster such as https://sourceforge.net/projects/equalizerapo/
    Experimental Fuel




    A new experimental fuel calculator is available for use and must be enabled via a setting (otherwise the older algorithm continues to be used).




    The new calculator estimates the number of laps for timed races, allowing both kinds of race sessions to share fuel usage data and settings. This becomes even more accurate as the race plays out and the fastest laps of the leaders (including multi-class) are accounted for. If the (existing) "Save pit stop benchmark times to disk" feature is used, the times will be used to greatly improve the accuracy of the estimate, and the amount of fuel that is taken on during the pit benchmarks is taken into account (so you can have benchmarks for a full tank, and each series that you race in, which should be good news for iRacing GT3 drivers who dabble with IMSA and endurance events).




    Fuel usage will be persisted between sessions (to `fuel_usage.json`) to improve the accuracy of the fuel usage estimates, and the "pit window will open" call should arrive earlier and be a lot more accurate than previous. This file can be manually curated (or shared with your team) and will only ever store 5 sessions worth of data for any car / track combination.




    The way the new calculator works is that the projected fuel usage per lap is on a sliding scale from the most typical lap through to the most fuel intensive lap, only considering green flag laps. The sliding scale is user selected and can be anywhere from 50% (the "median" fuel usage) to 100% (the lap that used the most fuel). Additional margin is added for ovals, and also for tracks depending on their length (so your margin at the Nordscheifle can be different to Lime Rock).




    The new settings are:
    - Experimental fuel calculation
    - Experimental fuel percentile
    - Experimental fuel extra laps to include for ovals
    - Experimental fuel reserve (long)
    - Experimental fuel reserve (medium)
    - Experimental fuel reserve (short)
    which are set to sensible conservative values to begin with.




    The margins can be changed dynamically with voice commands
    - "play it safe on fuel"
    - "roll the dice on fuel"
    - "reset the fuel plan"
    which will double or half the margin, accordingly. For example, if you have been pack racing and fuel saving (i.e. drafting and not reaching full throttle on the straight) you might want to "play it safe on fuel" and get a little bit more margin for when you are in clean air.




    Don't forget to "Enable iRacing auto refuelling when entering pit in race" if you want to use CrewChief instead of the iRacing autofueller (which must be disabled), or always ask Jim to refuel you manually using a voice command.
    This is obviously a very important feature for many racers, so any feedback is greatly appreciated and it is highly recommended that prior to any races that you enable "Make the trace recording button visible" and click the tick to record all the telemetry from the race so that the CrewChief developers can investigate any problems that you encounter (this typically generates ~50MB of data for an hour long race).
    iRacing Landmarks




    Thanks to the team at Garage61 we now have the ability to visualise all the iRacing tracks and are actively seeking contributors to update our database! Please come to the CrewChief discord and ask how you can help out as we have a lot of tracks to add, it requires nothing more than a text editor and a web browser to help.




    Some tracks have been updated, most notably all configurations of the Nordschleife, so good luck studying the track map to understand what Jim is saying. If there's an incident in Quiddelbacher Hoehe you know you're in trouble.
    Opponent Information




    Jim is now able to tell you about the rating and safety license of drivers around you in iRacing and RaceRoom. He will also keep you informed if the car you are approaching is a lapped car and if the car coming from behind is coming to lap you, long before the blue flags come out. This is especially useful in series that do not use blue flags and Jim will encourage you to let them past.




    Jim also got a bit better at closing the radio instead of giving out of date information, if you hear him opening and closing the radio a lot, consider disabling "Enable radio beeps" or asking him how his day is going.




    If you want to know what car number your opponents are sporting, make sure to enable "Opponents identified by name and number" which will let Jim know to use their name and number even if he knows their name.




    A heuristic reputation system has been added for iRacing, allowing you to agree with Jim how to detect if other drivers might have a less-than-admirable reputation. This is off by default but can be enabled with the following settings
    - Reputation Messages
    - Club Reputations
    - Rating Reputation
    - Tenure Reputation




    He's not yet able to recognise Red Bull Liveries, so you're on your own there.




    The "Club" is intended to be used as a proxy for network latency so will be heavily dependent on where you are in the world. See https://iracingdata.com/charts/IncidentsPerClub for some interesting statistics. For example if you're in Europe you might want to consider adding "International" to the list and if you're in the US or Australia you might want to consider adding "International" to the list.




    The "Rating" is an absolute minimum threshold and although you may be told about a driver's rating in their description, this cuts straight to the chase. It is intended to be used to filter drivers who are *very* far below your level and are likely to cause you harm by being "helpful" instead of predictable.




    The "Tenure" is a proxy for how long drivers have been using the service. As a point of reference, drivers with id 980000 started using the service around 3 months ago as this is written (Feb 2024) and this can be moved forward 10000 every month or so to continue using that kind of threshold.




    During a race, you can tell Jim to "mark the driver [ahead/behind] as dirty" which will be remembered for following races. If you weren't able to catch the guy that divebombed you from 10 car lengths back, you can always edit the `iracing_reputations.json` file in your crewchief documents folder, which looks something like this. All fields except `customer_id` are informational / optional and you can also record `carClass` and `date` for posterity.
    [
    {
    "customer_id": 408068,
    "name": "Jos Verstappen",
    "comment": "thinks he's Max Verstappen"
    },
    {
    "customer_id": 65874,
    "name": "William Byron",
    "comment": "will never win Daytona racing like this"
    }
    ]
    (lol, this is just an example, we're not suggesting these guys are actually dirty drivers!)




    For more real world drivers on iRacing, seehttps://www.reddit.com/r/iRacing/comments/qym1fo/list_of_real_life_drivers_on_iracing/




    "iRacing Strength of Field is for the player class" can be used to avoid noise from other classes when asking what the strength of field is. Unfortunately Jim is yet to record a gridwalk message that we can use, so you have to ask.
    Miscellaneous




    Some new settings have been added
    - American units for stock car racing
    - Time between announcing new opponent (and we're aware of an issue when the car in front is blinking)




    and a variety of bugs have been fixed. Most notably, the formation side bug has been fixed in iRacing. Or, rather, has been worked-around. We must now maintain a database of the track formation rules since the iRacing telemetry is buggy. New tracks will be added manually.




    New voice commands:
    - what's the gap behind on track
    - what's the gap ahead on track
    - what's the gap to the leader
    - what's my car number
    - what lap is it
    - watch the car ahead
    - watch the car behind




    and
    - pitstop change front tyres only
    - pitstop change rear tyres only
    now work in iRacing
    Attached Files Attached Files

  2. #2

    Dev Team Member

    Administrator
    Seven Smiles's Avatar
    Join Date
    Jan 2018
    Posts
    286
    Release Candidate 4.18.2.2

    • If the Property Enable game auto detect is checked then Crew Chief will switch to the game automatically when the game starts up
    • Stop LMU fast rolling start being announced as a standing start.
    • (If experimental fuel checked)
      • report estimated laps left in timed races.
      • shorten the focus to the next pit stop instead of saying "we estimate 142 laps left" and "we'll need 273 litres of fuel"
        [Subtitle] You: how long's left
        [Subtitle] Jim: 3:hours 48 minutes to go
        [Subtitle] Jim: we estimate 18 laps of fuel left

        [Subtitle] You: how's my fuel
        [Subtitle] Jim: should be about 17:laps of fuel remaining 2.8 litres per lap
        [Subtitle] Jim: and we'll need to stop again to get to the end

    • (More detail in trace file full path error msg)
    Attached Files Attached Files

  3. #3

    Dev Team Member

    Administrator
    Seven Smiles's Avatar
    Join Date
    Jan 2018
    Posts
    286
    Release Candidate 4.18.2.3

    • DRS beeps can be turned off in LMU
    • Trace messages in the boot sequence (run CC from the command line:
      CrewChiefRC.exe > output.txt 2>&1
      then output.txt contains the messages which can be used by the dev team)
    • Default limit_available_games to all games as a reference for all the names
    • Upgrade Newtonsoft.Json library to 13.0.3 to get rid of the vulnerability warning (even though it doesn't apply to CC)
    Attached Files Attached Files

  4. #4

    Dev Team Member

    Administrator
    Seven Smiles's Avatar
    Join Date
    Jan 2018
    Posts
    286
    Trace messages in the boot sequence are only for those who find nothing happens when they run CC. Press Win/R; enter "cmd" to open a command window then
    Code:
    "C:\Program Files (x86)\Britton IT Ltd\CrewChiefRC\CrewChiefRC.exe"  > output.txt 2>&1
    output.txt should normally contain something like
    Code:
    Boot trace 0
    Boot trace 1
    Boot trace 2
    Boot trace LoadSplashImage 0
    Boot trace 3
    Boot trace MW 0
    Boot trace MW 1
    Boot trace MW 2
    anything different may give clues why nothing is visible.

  5. #5

    Dev Team Member

    Administrator
    Seven Smiles's Avatar
    Join Date
    Jan 2018
    Posts
    286
    Release Candidate 4.18.2.4

    Fixes the boot problem.
    Misc other minor fixes.
    Attached Files Attached Files

  6. #6

    Dev Team Member

    Administrator
    Seven Smiles's Avatar
    Join Date
    Jan 2018
    Posts
    286
    The Release Candidate makes it easier to find debug logs and other stuff - click the File menu. It will open your file browser in Documents\CrewChiefRC







    In DebugLogs you'll find the saved contents of the Console window for your recent sessions labelled with a time stamp like console_2024_03_03-20-01-25.txt

  7. #7

    Dev Team Member

    Administrator
    Seven Smiles's Avatar
    Join Date
    Jan 2018
    Posts
    286
    V4.18.2.5.RC

    Initial iRacing rain support.
    Various bug fixes centred on iRacing.
    Handle LMU/RF2 Properties separately.
    Add Janne calls to RBR

    Also: There is a Property Make the trace recording checkbox visible which allows you to record all the information sent by the game while CC is running. This can be very useful to the dev team if you find a specific problem, particularly if it's in a game we don't use often (looking at you F1 2018 ) Even though the data is compressed the files can get quite large quite quickly.
    Attached Files Attached Files

  8. #8

    Dev Team Member

    Administrator
    Seven Smiles's Avatar
    Join Date
    Jan 2018
    Posts
    286
    V4.18.2.6.RC

    Improved rain support for iRacing.
    Add finishing position prediction before race start.
    Improve the overtake detection logic, opponent and overtaking messages improved.
    Various improvements and bug fixes.
    Attached Files Attached Files

  9. #9
    Junior Member
    Join Date
    Nov 2022
    Posts
    4

    No IRacing auto detect, no ACC available

    Quote Originally Posted by Seven Smiles View Post
    V4.18.2.6.RC

    Improved rain support for iRacing.
    Add finishing position prediction before race start.
    Improve the overtake detection logic, opponent and overtaking messages improved.
    Various improvements and bug fixes.
    I don’t know if it is known, but auto detect for IRacing does not work. Also ACC is not available in the games list.

  10. #10

    Dev Team Member

    Administrator
    Seven Smiles's Avatar
    Join Date
    Jan 2018
    Posts
    286
    Thanks, not known, we'll look into them before the next release, coming soon.

    Both are working here, have you clicked the Reset to default button under Limit available games? iRacing (or any other game) must have focus for a few seconds before CC will recognise it. Does iRacing show up as iRacingSim64DX11.exe in Task Manager?

Page 1 of 4 123 ... LastLast

Posting Permissions

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