Results 1 to 3 of 3

Thread: Beta Test Thread

  1. #1
    Crew Chief Mega Corp CEO mr_belowski's Avatar
    Join Date
    Feb 2017
    Posts
    1,406

    Beta Test Thread

    This beta is very much a work in progress and the new features are changing all the time...

    http://crewchief.isnais.de/CrewChief...0.0.0_beta.msi


    There are some performance improvements in the audio pipeline and a few other bug fixes, but the main addition is overlays.

    Crew Chief can render in-game overlays to show the app's console output or user-configurable telemetry charts controlled by voice commands. This only works with the game running in windowed (or borderless windowed) mode.

    Full documentation TBD. These can also be shown in VR and positioned in the game world using 3rd party apps like "OVR Overlay". Enable this functionality with the 'Enable overlay window' property. By default the app will record the telemetry data specified in Documents/CrewChiefV4/chart_subscriptions.json - this file can be edited to include new data channels but it requires some understanding of the internal game data format and / or the internal Crew Chief data format - we're still working in this. The telemetry recording is not active during race sessions - you can enable this by selecting with the 'Enable chart telemetry in race session' property.

    Telemetry is available for the previous completed lap (excluding out laps), the player's best lap in the session (excluding invalid or incomplete laps) and in some limited cases, the best opponent lap in the session (opponent data is limited to car speed, and is only available for some games at the moment). Typically, you'd drive a few laps in practice and pit, then ask the Chief "show me last lap car speed" or something like that.


    General overlay commands:


    "hide overlay" / "close overlay"
    "show overlay"
    "show console"
    "hide console"
    "show chart"
    "hide chart"
    "show all overlays" - show console and chart(s)
    "new chart" / "clear chart" - removes all data from the currently rendered chart
    "clear data" - clears all in-memory telemetry data for the current session
    "refresh chart" - redraw the current chart with the latest data
    "show stacked charts" - show each different series on its own chart
    "show single chart" - show all active series on the same chart
    "show time" - change the x-axis to be time
    "show distance" - change teh x-axis to be distance around the lap (this is the default)




    Series specific overlay commands:


    "show me..." - add a series to the chart
    "chart, remove..." - remove a series from the chart
    "best lap..." - add player best lap to the chart
    "last lap..." - add player last lap to the chart (can be omitted - the app will assume you mean last lap if you don't specify it)
    "opponent best lap.." - add opponent best lap (over all opponents in the player's class) to the chart


    e.g. to show a single chart for car speed, with your best lap and your opponents's overall best lap overlaid on the same chart with x-axis as distance (metres):
    "show me best lap car speed"
    "show me opponent best lap car speed"


    e.g. to show 2 charts, one for speed and one for gear for your best and your last lap with x-axis as distance (metres):
    "show me best lap car speed"
    "show me last lap car speed"
    "show me best lap gear"
    "show me last lap gear"


    e.g. to show 3 charts, speed gear and RPM for your best and last laps with x-axis as time (seconds):
    "show me best lap car speed"
    "show me last lap car speed"
    "show me best lap gear"
    "show me last lap gear"
    "show me best lap engine revs"
    "show me last lap engine revs"
    "show time"


    e.g. to show a single chart with throttle position and gear for your last lap with x-axis as distance (metres):
    "show me throttle position"
    "show me gear"
    "show single chart"




    Note that data for the same series (e.g. car speed) will always be overlaid on the same chart. Stacked charts only applies to data from different series (speed / gear, for example).

    There are a bunch of pre-defined data series for the charts - car speed, engine revs, gear, brake pressure, throttle position, lf/rf/rl/rr inner temp, lf/rf/rl/rr middle temp, lf/rf/rl/rr outer temp.

    The definition of a "series" is held in Documents/CrewChiefV4/chart_subscriptions.json - these override and extend the built in definitions. You can add to this as you wish but bear in mind that opponent data is very limited - for some games no suitable data is available at all, for some only car speed is available. We'll add more here and documentation as we go along. The rawDataFieldName refers to a field in the raw game data (the shared memory block), use this to access unmapped data or use "mappedDataFieldName" to access data that CrewChief has mapped from the raw data. In both cases dot-notation is supported. For example, car speed can be obtained from R3E by using rawDataFieldName=CarSpeed, or from the mapped data (for all games) using mappedDataFieldName=PositionAndMotionData.CarSpeed . All opponent data comes from mapped data, and the only available fields are Speed, RPM and Gear.


    The voice command fragment for each series is also in this json file. The voice command is constructed by the app, prefixing "show me best lap..." / "show me last lap..." / "show me opponent best lap..." as appropriate (e.g. "show me last lap car speed").


    To move the overlay, hold left control and alt keys down while dragging with the mouse


    the overlays look like this (with the console enabled):




    or this (just the charts enabled):

    Attached Images Attached Images  

  2. #2
    Junior Member
    Join Date
    Nov 2019
    Posts
    1
    The VR telemetry overlay is a great idea.
    I can get it to work but once I close it out RF2 then has really bad stutters that makes it unplayable.

    Not sure if I am calling it up properly.

    I checked the appropriate boxes in CC property (Enable overlay window, and the oculus check box).

    Once in game I call up the overlay and access it by hitting the dash board button on the controller to call up the oculus dashboard, then I add crew chief overlay as a toggle button on the dash board and press this to view the overlay.

    Works great, but after I shut down the dash board, that is when the in game stutters start, like the FPS are suddenly incredibly low.

    Before CC overlays I would access my telemetry through motec by calling up the oculus dashboard, then virtual desktop, then starting motec and viewing my data. I would then shut down the oculus dashboard and return to racing with no stutters.

    Not sure if I am doing this correctly or not and would appreciate any help.

    Also I think a good idea for an overlay sheet would be a list of the verbal commands that we can give...your program has become so incredibly verbose over time that I can't remember everything that I can query.

    Fantastic work!!

  3. #3
    VP PR Manager Sparten's Avatar
    Join Date
    Feb 2017
    Posts
    531
    Do you also have the console display enabled on the overlay ?, when ooulus dashboard toggles the overlay window does it remain active as a window on the taskbar ?
    Also can you please provide us with a log file from when your have been using the overlay it should be located in C:\Users\{USERNAME}\Documents\CrewChiefV4\debugLog s it might help spread a light on whats could be wrong.

Posting Permissions

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