Home

Welcome to the MFC wiki!

motion feedback controller

this tool uses the native in-game telemetry shared via UDP/TCP from games to control a motion platform. the next thing it does, it uses the USB HID data exchanged between the steering wheel and the gaming console to 'guesstimate' how a motion platform SHOULD move as if it had telemetry available. it does its best and most of the times it manages well. keep in mind however that it guesses that and it relies heavily on the FFB and wheel data to do it.

supported wheels so far:

• Thrustmaster T300RS for PS4
• Logitech G92 for PS4
• Fanatec Elite CSL for PS4

how this works:

the MFC SERVER controls the motion platform drivers. output devices supported so far:

• SCN5/6 - 1 to 6 DOFs
• Arduino - 2 DOFs using commands of type: "XLlpCXRrpC" where 'lp' and 'rp' are left and right positions from 0 to 1023 encoded as 10 bits binary
• Kangaroo - 2 DOFs using commends of type: "R,Prp Srs\r\nL,Plp Sls\r\n" where 'lp' and 'rp' are left and right positions and 'ls' and 'rs' are movement speeds.

the MFC CLIENTS are programs that receive native telemetry data and send it to the server. clients developed so far:

• Assetto Corsa
• Codemaster's F1 and Dirt Rally
• Project Cars 2

the USB XTRACTOR is used to proxy between the steering wheel and the console to extract USB HID data. the MFC XTRACTOR uses the USB HID data to generate game telemetry. the two extractors are only needed if the games you play don't provide in-game telemetry via UDP/TCP. the USBXTRACTOR also requires an Arduino/Teensy atmega32u4 with custom firmware. this solution is based on Matlo's https://github.com/matlo/serialusb . you can get an adapter ready-made from here
the firmware on the arduino is flashed via the command
avrdude -p atmega32u4 -c avr109 -P /dev/ttyACM0 -D -U flash:w:atmega32u4.hex:i
go here for more info on building and flashing the adapter

the end result using the xtractors on a PS4 system looks something like this:
here and here

Tested on a system using Raspberry PI2/3