Forums

Hello PootNoodlez, I was wondering if you (or anyone else) could elaborate further on what you mean by "unpacking the buffer using the [given] string"? Thanks.

Thank you Turn 10 for this incredible feature! I'm used to use dash app on my tablet with my racing sims and now that you brought support makes it so much better, thank you so much!

With this and race regulations it is becoming my most favorite game of all times and I've been racing all my life. Thank you for adding and improving!

Hi all,
I am totally blind and use the Narrator feature on the XBox console.
Right now, I am playing Forza to a limited extent using all the assists in the game. This new data feed could allow some fascinating accessibility add-ons. I'm thinking of an app on a iPhone or on the PC that could output telemetry data using text to speech. Obviously, It couldn't speak all the data as it updates, but certain metrics like speed and rpm could be really helpful.
I know that Microsoft is looking into adding text-to-speech directly into Forza, but it will probably be a while before we see that.
Just my 2 cents.

basically, its a telemetry control for dof platforms and dash controllers.

I’ve been able to use motion with my DoF Reality simulator and it is awesome....love this update!!!

Just a follow-up / teaser video to show all our products in action with Forza Motorsport 7, including our alternative customizable force feedback option. Tutorials will be made available tomorrow explaining how to get the most of Forza 7 with SimXperience gear. A sincere thanks to the Forza team for making this possible!

https://www.youtube.com/watch?v=s2_DcY22erE

Forza 7 now has three versions (Standard, Deluxe, Ultimate). Do these three versions support udp data output?

I can't see why not, it's just a feature of the game... So, yes 3 versions have it.

BTW, can't wait to see more features in the next update, I need gears and other data on my tablet... :)

Will this allow support for direct drive wheels without having to use adapters to emulate supported wheels.

Hi Everyone,

Glad to announce that Sim Racing Studio Power wind simulator and shaking software and hardware is now fully supporting Forza telemetry.

Thanks Microsoft for UDP support

www.simracingstudio.com

This already works with Forza EmuWheel. No adapters needed. Visit support chat if you need help (link in my signature).

This is something I would love to have for Forza 7. Thanks you for your initiative on providing the community this future application =) Looking forward to following your work.

I have set three parameters as required:
1.Data Out -ON
2.Data Out IP Address -127.0.0.1
3.Data Out IP Port -10001
But my own application doesn't receive any data，I use my application for live for speed, can receive udp data normally.

Why is that?

I have the same problem, both with my own app and with Sim Racing Studio - it looks like there is just nothing there to capture. Has anyone been successful with capturing the data on port 10001, or with getting Sim Racing Studio to capture the data? If so, what did you do?

If you read the original post carefully, you will see that it says localhost data streaming is not supported. This however is not because Forza chose not to support it, but because UWP apps have certain limitation on Windows.

Anyone got gear indicator to work ?

I use Simdashboard, and unlike just about every other driving sim, the only data that can be derived from the data out function, is Revs, Speed and a couple of pieces of relatively useless information, like Class and PI.

Seems very sub standard.... no real surprise I guess !

No Gear indicator, lap times, position, lap number and so on ...... nada. You really need this very basic data to enable you to turn off all the HUD stuff.

Developer of Simdashboard blames the extreme limitations of Forza 7 output system... and judging from the sophisticated Android displays I get for my other sims, he is undoubrefly correct in this assertion.

Edited by user Wednesday, July 4, 2018 2:48:16 AM(UTC)  | Reason: Not specified

You're being quite unfair. Turn10 haven't released this claiming that this is specifically designed for dashboard apps. In fact they are explicit about this (quote from original post): "The initial data structure is designed specifically for motion sleds. We are working with several peripheral manufacturers and will be adding many more data points in the future." This clearly states the purpose for which the data out was made and also promises to add more stuff in the future.

Can anyone please explain the difference between these 3 parameters? The explanation copied from the OP isn't all that clear:

# f32 TireSlipRatioFrontLeft; // Tire normalized slip ratio, = 0 means 100% grip and |ratio| > 1.0 means loss of grip.
...
# f32 TireSlipAngleFrontLeft; // Tire normalized slip angle, = 0 means 100% grip and |angle| > 1.0 means loss of grip.
...
# f32 TireCombinedSlipFrontLeft; // Tire normalized combined slip, = 0 means 100% grip and |slip| > 1.0 means loss of grip.
....

I would expect one to show weight distribution, one to show angle of road force on tire, and one to show fraction of max possible grip (given weight and compound) - but I'm not sure it that is what these are showing

TireSlipRatioFrontLeft << this is longitudal slip or just spin.
TireSlipAngleFrontLeft << this is lateral tire slip angle (not the same as wheel angle).
TireCombinedSlipFrontLeft; << this is combination of the two above. Although the way they normalize this, it is hard to make sense of this third value.

None of those three show weight distribution, not sure what you mean by "angle of road force on tire", and none of those show fraction of max possible grip. Also, just to be completely clear. None of them show tire load.

TireSlipRatioFrontLeft can be used to calculate Fx, and TireSlipAngleFrontLeft could be used to calculate Fy at pure slip. TireCombinedSlipFrontLeft can be used to calculate the same at combined slip.

Edited by user Saturday, July 7, 2018 4:59:55 PM(UTC)  | Reason: Not specified

Good info. I looked at a dataset and the data for first parameter shows slip in negative sense only for a front wheel (braking) and both senses (-/+) for a rear wheel (brake and traction) on a RWD car, which is much as you would expect. The data for second parameter shows slip in both senses consistent with lateral slip. And you are right in about the third parameter too - its just the root sum of the squares of the other two, so all it really gives us is magnitude of slip (lateral and longitudinal).

The release notes for the July update does not mention any changes to the data out format. This is disappointing, I was hoping that we would see a number of useful values (suggested in this thread) being added. Maybe we'll see them in August?

Not to worry, we will get an update the day after I transition to playing Horizon 4 :)

Haha, I wouldn't be surprised if that happens! 😃

I've made a few updates to the Python library on GitHub over the past few days. First to fix the missing acceleration parameters in the output when writing out data to a file. Thanks goes to Gryphon962 for reporting that bug! Secondly, to add CSV support for those who prefer to work with data in that format. I also switched the default behaviour so the script starts a new file and writes a row with the names of all columns at the beginning of the file. There's a command line parameter available to have it append to an existing file.

When are we getting more data such as Gear info ?

Very cool, have xb1 Forza and just installed Simhub on a old laptop, which serves up a web dashboard to my phone, would also like to see some more dashboard features added, eg gear, lap time etc.. great feature, nice work