App Offical release of Crew chief version 4 - auto updating and shiny

NL-Jos · 4. Februar 2017

Is there somewhere an simple tutorial what to do if you run crew-chief as standalone
When i now started crew-chief and click on RaceRoom the program works perfect when I'm going to play RaceRoom
But with the same handling i don't get it work with AC, project Cars or automobilista (other racegames i don't because these are the only one i have)
I realy don't know what to do or must change

Wesley Stokes · 5. Februar 2017

Having an issue getting the Crew Chief app to work, can any provide some assistance?

Rodent · 5. Februar 2017

Project CARS should work much like it does for Raceroom except you need to check if you're running the 32 or 64bit version. AMS requires an external plugin .dll by Gonzo that's to be placed with all the other plugins in the AMS Plugin folder. For AC Crew Chief has a python app in it's install folder called CrewChiefex that you need to place among your AC Apps to get it up an running. Beyond the Apps/Plugins the start procedure is the same as for Raceroom.

NL-Jos · 5. Februar 2017

Zitat von Rodent: ↑

Project CARS should work much like it does for Raceroom except you need to check if you're running the 32 or 64bit version. AMS requires an external plugin .dll by Gonzo that's to be placed with all the other plugins in the AMS Plugin folder. For AC Crew Chief has a python app in it's install folder called CrewChiefex that you need to place among your AC Apps to get it up an running. Beyond the Apps/Plugins the start procedure is the same as for Raceroom.
Klicke in dieses Feld, um es in vollständiger Größe anzuzeigen.

Thanks for your reaction.
I've find out how It's work with project Cars searching on Google and find it on youtube
But for AC and AMS don't.
And your reaction is stil to difficult for me to understand, sorry.
Maybe It's the color of my hair.
Can you, or someone else, explain it in an easy way?

Wesley Stokes · 5. Februar 2017

Zitat von mr_belowski: ↑

This is my little Crew Chief application, which works for PCars and RaceRoom. This release is the first 'official' RaceRoom release since the game update, which has added loads of loads of data which Crew Chief can use.

This application runs in the background while you play RaceRoom. It reads data from the Shared Memory block that RaceRoom writes to, and it uses it to trigger audio messages. To run this windows 7 and 8 / 8.1 users will need to install the .Net framework version 4.5.

Download V4 here:

http://crewchief.isnais.de/CrewChiefV4.msi

This is an MSI installer which your browser will probably warn you about - "not commonly downloaded and could be dangerous". This is simply because the .msi file isn't digitally signed - there's nothing I can do about this at the moment.

And a massive Thankyou to Robert Winkler from these very forums for the hosting awesomeness.

Here's a grotty video of the older version, with some DTM 2014 action with me using the app but being too engrossed in the race to ask it many questions..

The app includes many driver name recordings for AI drivers. For those with a mic, the app can recognise drivers' names if they're sensible (firstname [space] lastname)

Righty, here's the readme....

CrewChief version 4.

Changelog
---------
Version 4.2.1.4: loads of stuff
....[to long to post here]

Known Issues Which Aren't Fixable
---------------------------------
Joining a session part way through (practice or qualify session online) will result in the app having an incomplete set of data for opponent lap and sector times. In such cases the best opponent lap and sector data is inaccurate. For Raceroom we can get the fastest opponent lap time, but if this lap was completed before the app was running, the sectors within that lap aren't accessible. In this case the pace report will include the lap time delta, but there'll be no sector delta reports. As soon as an opponent sets a faster lap, the app will have up to date best lap data so the pace and sector reports will be accurate and complete.

RaceRoom uses a 'slot_id' field to uniquely identify drivers in a race. However, this field doesn't really work properly (there are lots of issues with it), so the app has to use the driver's names. Driver names for AI driver are not unique. All the lap time and other data held for each driver is indexed by driver name so if a race has 2 or more drivers with the same name, the app will get things like lap and sector times wrong. This is only a problem racing the AI - be aware that if you have a car class with a limited number of unique AI drivers (German Nationals / Americal Nationals / Hill Climb Legends / etc), but select a field size greater than this, the app will do weird things.

RaceRoom doesn't have a pre-start procedure phase for offline races, and in the pre-start phase online ("Gridwalk") very little valid and accurate data is available, so there are no messages about pit window, race position, etc before the lights come on.

Detecting 'good' passes isn't really feasible. I've tried to limit the 'good pass' messages to overtakes that are reasonably 'secure', don't result in the other car slowing excessively, and don't involve the player going off-track. I can't, for example, tell the difference between a clean pass and a bump-and-run punt, so you might get congratulated for driving like a berk.

Quick start
-----------
Windows 7 and 8 / 8.1 users will need to install .net 4.5 to use the app. This is already part of windows 10. Download the CrewChiefV4.msi installer and install the app. This will create a start menu shortcut - use this to run the app. On the first run, you'll be prompted to download the sounds and driver name packs (the big green buttons). Once this is done the app will ask to be restarted, then you're good to go.

One Windows 10 user reported that, once he'd installed the app, he had to run the app as administrator the first time he launched. Try this if the app fails to run first time.

Running with voice recognition
------------------------------
If you want to use voice recognition, download the correct speech recognition installers for your system (speech_recognition_32bit.zip or speech_recognition_64bit.zip).

The 64 bit installers are here:
https://drive.google.com/file/d/0B4KQS820QNFbY05tVnhiNVFnYkU/view?usp=sharing

The 32 bit installers are here:
https://drive.google.com/file/d/0B4KQS820QNFbRVJrVjU4X1NxSEU/view?usp=sharing

Alternatively, the Microsoft download links are, for the runtime installer (do this one first)
https://www.microsoft.com/en-gb/download/details.aspx?id=27225

For the language packs (use which ever en-XX best suits your location / accent)
https://www.microsoft.com/en-us/download/details.aspx?id=27224

Run SpeechPlatformRuntime.msi (this is the MS speech recognition engine), then run MSSpeech_SR_en-GB_TELE.msi or MSSpeech_SR_en-US_TELE.msi depending on your preferred accent (these are the 'cultural info' installers). If you want to use US speech recognition (MSSpeech_SR_en-US_TELE.msi) you must modify the "speech_recognition_location" property to "en-US". This can be done by modifying the property value in the application's Properties area. If you're happy with en-GB you don't need to do anything other than run the 2 speech recognition installers.

For speech recognition, you need a microphone configured as the default "Recording" device in Windows.

To get started, run the app and choose a "Voice recognition mode". There are 3 modes (the radio buttons at the bottom right). "Disabled" means that the app won't attempt any speech recognition. "Hold button" means you have to hold down a button while you speak, and release the button when you're finished. "Toggle button" means you press a button once to start the speech recognition, and the app will continue to listen and process your spoken requests until you press the button again to switch it off (while the app is listening you can make as many voice requests as you like, you don't need to toggle speech recognition off and back on again if you want to ask another question). "Always on" means the app is always listening for and processing speech commands. Selecting "Disabled" or "Always on" from this list makes the app ignore the button assigned to "Talk to crew chief".

If you want to use Hold button or Toggle button mode, select a controller device ("Available controllers" list, bottom left), choose "Talk to crew chief" in the "Available actions" list and click "Assign control". Then press the button you want to assign to your radio button.

You need to speak clearly and your mic needs to be properly set up - you might need to experiment with levels and gain (Microphone boost) in the Windows control panel. If he understood he'll respond - perhaps with helpful info, perhaps with "we don't have that data". If he doesn't quite understand he'll ask you to repeat yourself. If he can't even tell if you've said something he'll remain silent. There's some debug logging in the main window that might be useful.

I've not finished implementing this but currently the app understands and responds to the following commands:

"how's my [fuel / tyre wear / body work / aero / engine / transmission / suspension / pace ]"
"how are my [tyre temps / tyre temperatures / brakes / brake temps / brake temperatures / engine temps / engine temperatures]" (gives a good / bad type response)
"What are my [brake temps / tyre temps]" (gives the actual temps)
"what's my [gap in front / gap ahead / gap behind / last lap / last lap time / lap time / position / fuel level / best lap / best lap time]"
"what's the fastest lap" (reports the fastest lap in the session for the player's car class)
"keep quiet / I know what I'm doing / leave me alone" (switches off messages)
"keep me informed / keep me posted / keep me updated" (switches messages back on)
"how long's left / how many laps are left / how many laps to go"
"spot / don't spot" (switches the spotter on and off - note even in "leave me alone" mode the spotter still operates unless you explicitly switch it off)
"do I still have a penalty / do I have a penalty / have I served my penalty"
"do I have to pit / do I need to pit / do I have a mandatory pit stop / do I have a mandatory stop / do I have to make a pit stop"
"where's [opponent driver last name]"
"what's [opponent driver last name]'s last lap"
"what's [opponent driver last name]'s best lap"
"what's [opponent race position]'s last lap" (for example, "what's p 4's best lap", or "what's position 4's last lap")
"what's [opponent race position]'s best lap"
"what's [the car in front / the guy in front / the car ahead / the guy ahead]'s last lap"
"what's [the car in front / the guy in front / the car ahead / the guy ahead]'s best lap"
"what's [the car behind / the guy behind]'s last lap"
"what's [the car behind / the guy behind]'s best lap"
"what tyre(s) is [opponent driver last name / opponent race position] on" (DTM 2014 only - reports "options" or "primes")
"what are my sector times"
"what's my last sector time"
"who's leading" (this one only works if you have the driver name recording for the lead car)
"who's [ahead / ahead in the race / in front / in front in the race / behind / behind in the race]" (gives the name of the car in front / behind in the race or on the timing sheet for qual / practice. This one only works if you have the driver name recording for that driver)
"who's [ahead on track / in front on track / behind on track]" (gives the name of the car in front / behind in on track, regardless of his race / qual position. This one only works if you have the driver name recording for that driver)
"tell me the gaps / give me the gaps / tell me the deltas / give me the deltas" (switch on 'deltas' mode where the time deltas in front and behind get read out on each lap. Note that these messages will play even if you have disabled messages)
"don't tell me the gaps / don't tell me the deltas / no more gaps / no more deltas" (switch off deltas mode)
"repeat last message / say again" (replays the last message)
"What are my [brake / tyre] [temperatures / temps]"
"What time is it / what's the time" (reports current real-world time)

Other button assignments
------------------------
You can assign the 'toggle spotter on/off' and 'toggle race updates on/off' to separate buttons if you want to be able to toggle the spotter function and toggle the crew chief's updates on or off during the race. This doesn't require voice recognition to be installed - simply run the app, assign a button to one or both of these functions, and when in-race pressing that button will toggle the spotter or crew chief on and off.

Properties
----------
The settings can be accessed by clicking the "Properties" button in the app. This displays a popup window where you can tweak stuff if you want to. This interface is a bit rubbish but should let you tweak settings if you want to, although the properties are all (currently) undocumented. If you do change something in this interface, the app needs to restart to pick up the change - the "Save and restart" button should do this.

Each property has a "reset to default" button, or if you get completely stuck you can close the app and delete the user configuration folder and it should reset everything.

Custom controllers
------------------
This is untested. If your controller doesn't show up in the list of available controllers you can set the "custom_controller_guid" property to the GUID of your controller device. If this is a valid controller GUID the app will attempt to initialise it an add it to the list of available controllers.

Program start arguments
-----------------------
If you want to have the game pre-selected, start the app like this for RaceRoom: [full path]\CrewChiefV4.exe RACE_ROOM.
This can be used in conjunction with the launch_pcars / launch_raceroom / [game]_launch_exe / [game]_launch_params and run_immediately options to set crew chief up to start the game selected in the app launch argument, and start its own process.

If you want to run Crew Chief on your 4th CPU core only, and want have the application launch RaceRoom and start running immediately (i.e. just launch Crew Chief and everything else is done for you, no need to click anything else to start Crew Chief listening or launch RaceRoom) you first need to make a couple of Properties changes. Go to the properties screen and set the r3e_launch_exe" property to c:/games/steam/steam.exe (assuming steam is installed in c:/games), check the "launch_raceroom" option, and check the "run_immediately" option. Then create a shortcut to CrewChiefV3.exe with the parameters cpu4 and RACE_ROOM, so the "target" field in the short cut properties looks like this:

"C:\games\CrewChiefV4\CrewChiefV4.exe" cpu4 RACE_ROOM

Running on a single CPU
-----------------------
You can set the processor affinity for Crew Chief in TaskManager, but this will have to be done each time you start the app. Alternatively, you can start the app with an addition argument "cpu1", "cpu2", ... "cpu8", like this:
[full path]\CrewChiefV4.exe cpu4
this will set the processor affinity to the 4th CPU in your system (usually referred to as CPU3 - they're zero-indexed).

Updating the app
----------------
The app will tell you when there's a new version, or when the sound packs have been updated. App updates are handled by a 3rd party component which will download and execute a new installer. Sound updates are from within the app - just click the download button / buttons and the app takes care of it all.

Donations
---------
I made this because I wanted to make it and I enjoy making stuff. Working with the various quirks, errors and omissions in the shared data which the games provide hasn't been much fun, but it's all part of the challenge. Having said that, there are many many hours of hard work invested in this.
If you use it and like it and it becomes a regular and positive part of your sim racing, I'd be grateful if you would consider making a small donation. If only to stop my wife from complaining at me.

My paypal address and a handy "Donate" button are in my signature.

Would be great to recoup some of the investment in making this, but the most important thing is that the app is used 'in anger' and enjoyed as part of the sim racing experience. To this end, I'm always on the lookout for bug reports and feature suggestions.

One final point. If the app says "Jim is faster than you", let him through
Klicke in dieses Feld, um es in vollständiger Größe anzuzeigen.

Having issues getting the app to work for RaceRoom, can anyone help?

FAE_Coyote · 5. Februar 2017

Last version don't open in W10

mr_belowski · 5. Februar 2017

If you're having issues with the app, you need to provide some details. Any .Net errors in the windows event log (under Applications) will also help track down the problem.

The app *does* work with Windows 10, so there must be something specific to your install. One of the Rfactor 2 users reported that their Av quarantined the app (a false positive) - maybe something similar happened?

FAE_Coyote · 5. Februar 2017

Previus versions works well. Afther update to version 4.5, i can't open the crewchief, for the moment i back to version 4.4.3.3
I Try remove and reinstall, several times, but nothing happen.
Sorry for my english

FAE_Coyote · 5. Februar 2017

Nombre de registro:Application
Origen: Application Error
Fecha: 05/02/2017 19:27:53
Id. del evento:1000
Categoría de la tarea100)
Nivel: Error
Palabras clave:Clásico
Usuario: No disponible
Equipo: Fer2
Descripción:
Nombre de la aplicación con errores: CrewChiefV4.exe, versión: 1.0.0.0, marca de tiempo: 0x58921fe8
Nombre del módulo con errores: KERNELBASE.dll, versión: 10.0.14393.479, marca de tiempo: 0x582588e6
Código de excepción: 0xe0434352
Desplazamiento de errores: 0x0000000000017788
Identificador del proceso con errores: 0x11c0
Hora de inicio de la aplicación con errores: 0x01d27fdd9004acdf
Ruta de acceso de la aplicación con errores: C:\Program Files (x86)\Britton IT Ltd\CrewChiefV4\CrewChiefV4.exe
Ruta de acceso del módulo con errores: C:\WINDOWS\System32\KERNELBASE.dll
Identificador del informe: 00314fd5-57b4-49d4-9c2a-3299d71caa79
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-02-05T18:27:53.085552800Z" />
<EventRecordID>38506</EventRecordID>
<Channel>Application</Channel>
<Computer>Fer2</Computer>
<Security />
</System>
<EventData>
<Data>CrewChiefV4.exe</Data>
<Data>1.0.0.0</Data>
<Data>58921fe8</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.14393.479</Data>
<Data>582588e6</Data>
<Data>e0434352</Data>
<Data>0000000000017788</Data>
<Data>11c0</Data>
<Data>01d27fdd9004acdf</Data>
<Data>C:\Program Files (x86)\Britton IT Ltd\CrewChiefV4\CrewChiefV4.exe</Data>
<Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
<Data>00314fd5-57b4-49d4-9c2a-3299d71caa79</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

FAE_Coyote · 5. Februar 2017

Nombre de registro:Application
Origen: .NET Runtime
Fecha: 05/02/2017 19:29:35
Id. del evento:1026
Categoría de la tarea:Ninguno
Nivel: Error
Palabras clave:Clásico
Usuario: No disponible
Equipo: Fer2
Descripción:
Aplicación: CrewChiefV4.exe
Versión de Framework: v4.0.30319
Descripción: el proceso terminó debido a una excepción no controlada.
Información de la excepción: System.Xml.XmlException
en System.Xml.XmlTextReaderImpl.Throw(System.Exception)
en System.Xml.XmlTextReaderImpl.ParseText(Int32 ByRef, Int32 ByRef, Int32 ByRef)
en System.Xml.XmlTextReaderImpl.ParseText()
en System.Xml.XmlTextReaderImpl.ParseElementContent()
en System.Xml.XmlTextReaderImpl.Skip()
en System.Configuration.XmlUtil.StrictSkipToNextElement(System.Configuration.ExceptionAction)
en System.Configuration.BaseConfigurationRecord.ScanSectionsRecursive(System.Configuration.XmlUtil, System.String, Boolean, System.String, System.Configuration.OverrideModeSetting, Boolean)
en System.Configuration.BaseConfigurationRecord.ScanSectionsRecursive(System.Configuration.XmlUtil, System.String, Boolean, System.String, System.Configuration.OverrideModeSetting, Boolean)
en System.Configuration.BaseConfigurationRecord.ScanSections(System.Configuration.XmlUtil)
en System.Configuration.BaseConfigurationRecord.InitConfigFromFile()

Información de la excepción: System.Configuration.ConfigurationErrorsException
en System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean)
en System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(System.Configuration.ConfigurationSchemaErrors)
en System.Configuration.Configuration..ctor(System.String, System.Type, System.Object[])
en System.Configuration.ClientConfigurationHost.OpenExeConfiguration(System.Configuration.ConfigurationFileMap, Boolean, System.Configuration.ConfigurationUserLevel, System.String)
en System.Configuration.ConfigurationManager.OpenExeConfigurationImpl(System.Configuration.ConfigurationFileMap, Boolean, System.Configuration.ConfigurationUserLevel, System.String, Boolean)
en System.Configuration.ClientSettingsStore.ReadSettingsFromFile(System.String, System.String, Boolean)
en System.Configuration.LocalFileSettingsProvider.GetSettingValuesFromFile(System.String, System.String, Boolean, System.Configuration.SettingsPropertyCollection)
en System.Configuration.LocalFileSettingsProvider.Upgrade(System.Configuration.SettingsContext, System.Configuration.SettingsPropertyCollection, Boolean)
en System.Configuration.LocalFileSettingsProvider.Upgrade(System.Configuration.SettingsContext, System.Configuration.SettingsPropertyCollection)
en System.Configuration.ApplicationSettingsBase.Upgrade()
en CrewChiefV4.UserSettings..ctor()
en CrewChiefV4.UserSettings..cctor()

Información de la excepción: System.TypeInitializationException
en CrewChiefV4.MainWindow.setSelectedGameType()
en CrewChiefV4.MainWindow..ctor()
en CrewChiefV4.Program.Main()

XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-02-05T18:29:35.981702400Z" />
<EventRecordID>38511</EventRecordID>
<Channel>Application</Channel>
<Computer>Fer2</Computer>
<Security />
</System>
<EventData>
<Data>Aplicación: CrewChiefV4.exe
Versión de Framework: v4.0.30319
Descripción: el proceso terminó debido a una excepción no controlada.
Información de la excepción: System.Xml.XmlException
en System.Xml.XmlTextReaderImpl.Throw(System.Exception)
en System.Xml.XmlTextReaderImpl.ParseText(Int32 ByRef, Int32 ByRef, Int32 ByRef)
en System.Xml.XmlTextReaderImpl.ParseText()
en System.Xml.XmlTextReaderImpl.ParseElementContent()
en System.Xml.XmlTextReaderImpl.Skip()
en System.Configuration.XmlUtil.StrictSkipToNextElement(System.Configuration.ExceptionAction)
en System.Configuration.BaseConfigurationRecord.ScanSectionsRecursive(System.Configuration.XmlUtil, System.String, Boolean, System.String, System.Configuration.OverrideModeSetting, Boolean)
en System.Configuration.BaseConfigurationRecord.ScanSectionsRecursive(System.Configuration.XmlUtil, System.String, Boolean, System.String, System.Configuration.OverrideModeSetting, Boolean)
en System.Configuration.BaseConfigurationRecord.ScanSections(System.Configuration.XmlUtil)
en System.Configuration.BaseConfigurationRecord.InitConfigFromFile()

Información de la excepción: System.Configuration.ConfigurationErrorsException
en System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean)
en System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(System.Configuration.ConfigurationSchemaErrors)
en System.Configuration.Configuration..ctor(System.String, System.Type, System.Object[])
en System.Configuration.ClientConfigurationHost.OpenExeConfiguration(System.Configuration.ConfigurationFileMap, Boolean, System.Configuration.ConfigurationUserLevel, System.String)
en System.Configuration.ConfigurationManager.OpenExeConfigurationImpl(System.Configuration.ConfigurationFileMap, Boolean, System.Configuration.ConfigurationUserLevel, System.String, Boolean)
en System.Configuration.ClientSettingsStore.ReadSettingsFromFile(System.String, System.String, Boolean)
en System.Configuration.LocalFileSettingsProvider.GetSettingValuesFromFile(System.String, System.String, Boolean, System.Configuration.SettingsPropertyCollection)
en System.Configuration.LocalFileSettingsProvider.Upgrade(System.Configuration.SettingsContext, System.Configuration.SettingsPropertyCollection, Boolean)
en System.Configuration.LocalFileSettingsProvider.Upgrade(System.Configuration.SettingsContext, System.Configuration.SettingsPropertyCollection)
en System.Configuration.ApplicationSettingsBase.Upgrade()
en CrewChiefV4.UserSettings..ctor()
en CrewChiefV4.UserSettings..cctor()

Información de la excepción: System.TypeInitializationException
en CrewChiefV4.MainWindow.setSelectedGameType()
en CrewChiefV4.MainWindow..ctor()
en CrewChiefV4.Program.Main()

</Data>
</EventData>
</Event>

mr_belowski · 6. Februar 2017

these errors are in the code which upgrades user settings from an older version. I don't know why it's failing but I'll add an additional check to the code so if it can't migrate the settings it won't fail to start the app. Thanks for the info, it's really helpful

This line in your error log:
Versión de Framework: v4.0.30319
suggests you might be using an older version of the .Net framework. If this is the case (and you're using Windows 7 or 8), please update to the latest version.

To get it working in the mean time, you need to delete the c:/Users/[user]/AppData/local/Britton_IT_Ltd/ folder - this contains all the old application settings. Note that the AppData folder might be hidden. Alternatively, uninstalling and reinstalling the app should fix it

FAE_Coyote · 6. Februar 2017

Thanks for your support.
I deleted the folder in AppData/ ..., and now works !!

le_poilu · 6. Februar 2017

Hi Jim,
Since ... I don't know when (didn't launched Asseto for a while)... The parameter to auto-start Crewchief in Asseto Corsa mode don't work anymore.
I had previously the parameter ASSETTO, but now it wont work. Parameters: RACE_ROOM, RF2, AMS, etc are all working fine BTW.

And about that: maybe it could be nice to have some readme file listing this kind of parameters/settings

memoric77 · 9. Februar 2017

Hi Mr. Belowski
How can I found out if my name is present in crewchief? I cant hear it by myself "markus doerner"

mr_belowski · 9. Februar 2017

well there's a doerner.wav, mapped to m. doerner and markus doerner, so other drivers should be hearing it. The (3607) driver name sounds are in [user]/AppData/local/CrewChiefV4/sounds/driver_names/

memoric77 · 10. Februar 2017

Thank you for your fast response and sensational work! It sounds wonderfull

heppsan · 10. Februar 2017

I noticed when I did some testing in the WIP build that I don't have a spotter for cars beside me, I still get other notifications like my position and lap times. Any idea what can cause this?

mr_belowski · 10. Februar 2017

yes, the WIP build has a different shared memory layout. It's still correct as the reported offset of the driver data has also been update, but the current CrewChief implementation doesn't use this and assumes the old layout (bad jim...).

Basically, the WIP build isn't compatible with CrewChief because I'm a lazy programmer. The WIP build adds 5 or 6 ints and a float (I think) in front of NumDrivers so the release version of CrewChief is looking at the wrong bits of the shared memory file for its opponent driver data (including their world positions). I can knock up a version that works from the current codebase tonight if you want.

Note that none of this applies to the proper release version of Raceroom - it's only for the testers.

heppsan · 10. Februar 2017

Zitat von mr_belowski: ↑

yes, the WIP build has a different shared memory layout. It's still correct as the reported offset of the driver data has also been update, but the current CrewChief implementation doesn't use this and assumes the old layout (bad jim...).

Basically, the WIP build isn't compatible with CrewChief because I'm a lazy programmer. The WIP build adds 5 or 6 ints and a float (I think) in front of NumDrivers so the release version of CrewChief is looking at the wrong bits of the shared memory file for its opponent driver data (including their world positions). I can knock up a version that works from the current codebase tonight if you want.

Note that none of this applies to the proper release version of Raceroom - it's only for the testers.
Klicke in dieses Feld, um es in vollständiger Größe anzuzeigen.

Okay, good to know.
What I can remember I have at least had some moments when the spotter have worked in the WIP before, thats why I asked.
But I understand that this is more extra work for you, do to the rate of WIP builds.
And I understand if you think it's to much, you certainly need some rest too after all you're fine and continuously work with crew chief!

mr_belowski · 10. Februar 2017

I had a look through my code to see if I could sensibly use the provided driver data offset and driver data size values provided to dynamically adjust the way I map the data. I could split the Struct to use the driver data offset value (so additions to the shared memory wouldn't break the driver data), but if bytes were added to the individual driver data blocks it would really break my stuff. So rather than do a bunch of work which will only support half of the changes S3 might make, I'll just update the app to use the latest shared memory layout when S3 publish it.

In this case it's only a few minutes work to add some padding to make it map the driver data properly - I'll package a non-official version up later and provide a download link for the testers. This version will contain some untested changes (like message volume controls) but it should work

Anmelden oder registrieren

App Offical release of Crew chief version 4 - auto updating and shiny

NL-Jos Well-Known Member

Wesley Stokes Member

Rodent Well-Known Member Beta tester

NL-Jos Well-Known Member

Wesley Stokes Member

FAE_Coyote New Member

mr_belowski Well-Known Member Beta tester

FAE_Coyote New Member

FAE_Coyote New Member

FAE_Coyote New Member

mr_belowski Well-Known Member Beta tester

FAE_Coyote New Member

le_poilu Well-Known Member

memoric77 Member

mr_belowski Well-Known Member Beta tester

memoric77 Member

heppsan Well-Known Member

mr_belowski Well-Known Member Beta tester

heppsan Well-Known Member

mr_belowski Well-Known Member Beta tester

Anmelden oder registrieren

App Offical release of Crew chief version 4 - auto updating and shiny

NL-Jos Well-Known Member

Wesley Stokes Member

Rodent Well-Known Member Beta tester

NL-Jos Well-Known Member

Wesley Stokes Member

FAE_Coyote New Member

mr_belowski Well-Known Member Beta tester

FAE_Coyote New Member

FAE_Coyote New Member

FAE_Coyote New Member

mr_belowski Well-Known Member Beta tester

FAE_Coyote New Member

le_poilu Well-Known Member

memoric77 Member

mr_belowski Well-Known Member Beta tester

memoric77 Member

heppsan Well-Known Member

mr_belowski Well-Known Member Beta tester

heppsan Well-Known Member

mr_belowski Well-Known Member Beta tester

Nützliche Suchen