Previous    Contents     Next

12. Motion Driver for Live for Speed racing sim

A beta version is available for the racing sim Live for Speed. The download is on the Introduction page.

Access to the racing sim telemetry data is via the sim's OutSim telemetry data output via UDP - there are no plugins required.

IMPORTANT: this is BETA software and may contain bugs - please use with care!

Installation:

Installation of the motion driver is mainly the same as the other versions - see section 2.

To enable the LFS UDP telemetry data output -

1. Go to the LFS cfg.txt file (usually in the LFS installation folder).
    

2. Find the OutSim parameters and set them  -
   
   OutSim Mode 1 :0-off 1-driving 2-driving+replay
   OutSim Delay 1 :minimum delay between packets (100ths of a sec)
   OutSim IP 127.0.0.1 :IP address to send the UDP packet
   OutSim Port 20777 :IP port
   OutSim ID 111 :if not zero, adds an identifier to the packet (this is optional)
   
   Where IP is the IP address of the PC on which the motion driver is running (= 127.0.0.1 if on the same PC as LFS)  - this value must match that set for the IPAddress parameter in your motion cue .bff config file.
   
   Port is the target port for the UDP data - this value must match that set for the PortS parameter in your motion cue .bff config file.
   
   Update: Thanos reported that he had to set Port to 4123 to get the UDP data working - if you try this remember to set PortS to the same in your cue .bff config file.
   
   ID is an optional identifier for the UDP packets - it isn't used directly by the motion software.

Operation:

The software operation is mainly as described in Section 3 Operation.

Some of the flight sim related features such as heave movement recording due to turbulence etc are not active in the LFS motion driver for obvious reasons.

The default .bff config files in the LFS motion driver zip file contain cue settings better suited to the faster dynamics of the racing car sim. You may wish to experiment with them. Generally because the on-ground vehicle accelerations are held for shorter durations before changing again rapidly there is less need for washouts in the cue, so the sample configs don't use acceleration washouts (other than where they are needed for basic cue development - ie in the heave and yaw cues). The acceleration scaling to fit the cue limits may also need to be adjusted to suit different vehicles.

NOTE: The telemetry UDP data is not available from LFS when the sim is either paused or not in a live driving session. When LFS leaves a live driving session the UDP data can become erratic and it is best that the motion drive is not left on Drive when this happens. By default therefor the drive will switch to Hold at Start Pos mode whenever a break is detected in the UDP data flow.

To disable this behaviour use the Park_on_Int parameter in your cue .bff configuration file.

Remember you can use the Drive and Hold hot-keys or hot-buttons which are defined in your .bff cue configuration file.

To switch LFS in and out of Full Screen mode use the Shift + F4 buttons.

The refresh rate of the motion driver output can be increased up to the data refresh rate of the LFS telemetry data output using .bff configuration file parameter MD_Delay.

UDP Data Forwarding:

If you want the motion driver to share the UDP data you can set the software to forward the data on to a further IP address and port.

To do this set the IP_F_target and PortF parameters in your motion cue .bff config file to the IP address and port of the new target location.

Also set the IP_F_this IP address from which the motion driver sends the forwarded data (can be 127.0.0.1 if sending to the same PC or the LAN address of the motion driver PC if sending to a remote PC).

If you find any bugs or strange behaviours in the beta version then please let me know.

Previous    Contents     Next