Are you sure it's OutSim, and not OutGauge? Or maybe OutGauge was released after S1, not sure...OutSim doesn't carry telemetry data though, it has the data for motion sims.
We are using the telemetry data for motion simulators. We've got a motion sim working with LFS S1 but can't get it to work for LFS S2. The telemetry data is coming through whatever IP / port you're using in the cfg file:
OutSim Mode 1
OutSim Delay 1
OutSim IP 127.0.0.1
OutSim Port 6668
OutSim ID 0
This is from the InSim.txt file in the docs folder of LFS S2:
// OutSim - MOTION SIMULATOR SUPPORT // ======
// The user's car in multiplayer or the viewed car in single player or // single player replay can output information to a motion system while // viewed from an internal view.
// This can be controlled by 5 lines in the cfg.txt file :
// OutSim Mode 0 :0-off 1-driving 2-driving+replay // OutSim Delay 1 :minimum delay between packets (100ths of a sec) // OutSim IP 0.0.0.0 :IP address to send the UDP packet // OutSim Port 0 :IP port // OutSim ID 0 :if not zero, adds an identifier to the packet
// Each update sends the following UDP packet :
struct OutSimPack { unsigned Time; // time in milliseconds (to check order)
Vector AngVel; // 3 floats, angular velocity vector float Heading; // anticlockwise from above (Z) float Pitch; // anticlockwise from right (X) float Roll; // anticlockwise from front (Y) Vector Accel; // 3 floats X, Y, Z Vector Vel; // 3 floats X, Y, Z Vec Pos; // 3 ints X, Y, Z (1m = 65536)
int ID; // optional - only if OutSim ID is specified };
// NOTE 1) X and Y axes are on the ground, Z is up.
// NOTE 2) Motion simulators can be dangerous. The Live for Speed developers do // not support any motion systems in particular and cannot accept responsibility // for injuries or deaths connected with the use of such machinery.
PS - telemetry data is motion data (pitch, roll, etc)
