Depends largely on what sort of telemetry the SimXperience guy(s) need. We will be adding some more data soon, but I don't know if it will help them in any way.
I wonder how we can detect crashes or driving errors robustly, probably rapid increase in local_acceleration or big orientation/velocity mismatches (going sideways) or so... whether the car is driving "offroad" would also be nice to know (per-tire contact "surface" information). And any sort of impact events (in case it doesn't cause damage), stored in a way that is not simply boolean flag, so we don't have sampling frequency issues. maybe something like LastCarContactTime, LastWorldContactTime
The problem is Simxperience software . Installed Sim Commander 3 instead of 4 ( beta) and now everything works as it should and that by far.
I'm currently beta testing a very nice looking piece of dash software for R3E but the developer was wondering if this list of things can be added to the API; Accelerator % Brake % Clutch % Steering Angle Water Pressure (KPA) Session Type (race, practice etc) Fuel Pressure Tire Wear Brake Temps Brake Wear Suspension Damage Aero Damage Engine Damage Driving Aids (ABS, TC etc) Track Name Vehicle Name Driver Name Ambient Temp Track Temp Sector1 Time Sector2 Time Sector3 Time Competitor Names Competitor Positions He registered here and tried posting it himself but he couldn't post for some reason, which is why I'm posting it for him.
Thanks for the suggestions. Some of those are already in, some are on their way and the rest will probably take a while before they make it in. Keep an eye on the GitHub reposity or this thread for updates.
Which ones are already in there? unless i am missing something, none of those are in there (except for the DRS flag being part of driver aids i guess).
I think "already in" means "already in ready for the next release". Only DRS stuff from your list is in the currently released version
My apologies. I've been staring at the upcoming additions for a few days now, so I forgot which ones were there previously. You're right, none of those are in right now, but a lot of them will be in the patch which hopefully lands some time next week. But again, the ones that don't make it into the patch will probably be a while before they do (if ever). I'll post an update in advance when we start preparing for the next batch.
Hi Makael, According to the comments in the code, the temperatures are in Kelvin (K) but it seems that the values coming through are not in Kelvin (K) as seen below in my streaming dashboard. Can you please let me know what units they are? Thanks!
Yeah, I assumed that too. I think they could be Fahrenheit . In fact as seen in image I am getting around 50s for oil and water temp....the thing is that I have no idea in real life what these values should be As for the tires, they come across around 27 when idle and as seen in image I was hot lapping there
That's what I get for trusting a decade old documentation. Thanks for pointing that out. The temperatures are indeed all of them in celsius. As for the seemingly low values I can't really answer that right now, I'll have to look into it.
Hello Mikael, Since the hot period in Austria (some places over 37°C) is getting over, I´ll have more time and passion for coding Do you have any further infos about 2D-Layout of the tracks? Is there any chance to get them? With best regards from sunny Austria Wolfgang
@Wozy_of_Salzburg here's a quick package you can use. Mind you the naming convention isn't the best, also they have some different styles. But I hope you find those useful.
Hi, I've seen in today's patch notes (7/7/15) there is a line about added Shared Memory API fields. May I ask what fields have been added and if the GitHub project is up to date? Thank you.
Also, check the values of the constant fields before you use them - undocumented example is a bit out for SessionPhase (i've used Formation = 3, Countdown = 4, Green = 5, Checkered = 6). There might be some others that need checking too
Fantastic additions! Thanks for your work. Shame Track and Car Name/ID currently used didn't make it in.