Skip to content

FreeD / OSC Data to Unreal Engine, Aximmetry, or Disguise — Setup and Pitfalls

Networking / InTime Resolved All rigs

Summary

Flair sends camera position data (FreeD protocol over UDP) to virtual production software such as Unreal Engine, Aximmetry, or Disguise. The most common failure is an IP address mismatch: the receiving machine must be on the InTime subnet (192.168.1.xxx) because FreeD data is transmitted from the InTime network interface, not the standard Windows NIC.

Symptoms

  • Unreal Engine / Aximmetry shows "no data" from Flair
  • Serial Tester app confirms FreeD packets are leaving Flair but nothing arrives at the VP system
  • Data works intermittently or only on some network paths
  • VP system receives data when connected directly but not through a managed switch

Root Cause

InTime controls the network interface used by Flair for real-time data output. FreeD UDP packets leave via the InTime NIC, which is bound to the 192.168.1.xxx subnet. Any receiving device that is on a different subnet (e.g., 192.168.0.xxx or 10.0.0.xxx) will not receive the packets regardless of how routing is configured.

Additionally, Windows Firewall on the receiving PC frequently blocks incoming UDP packets even after Flair is configured correctly.

Resolution

Step 1 — Configure FreeD output in Flair

In Flair (Classic or F7): 

Setups → External Devices → Data Output → FreeD → UDP
IP address: [IP of VP machine, must be 192.168.1.xxx]
Port: 55535 (default; confirm with VP team)
→ Save / Apply

Use Setups -> External Devices for the Flair-side output entry. Use the VP application's own network/input settings for the listening IP and port.

Do not use 192.168.1.20

MRMC Support (June 2025): "Don't use .20" — this IP is reserved. See NET ip reserved addresses for the full reserved IP list.

Step 2 — Configure the VP machine

  1. Assign a static IP on the VP machine in the 192.168.1.xxx range (e.g., 192.168.1.99 / 255.255.255.0).
  2. Connect the VP machine to the InTime switch with a wired Ethernet cable. Do not use WiFi.
  3. Turn off Windows Firewall on the VP machine. Confirm it is fully off, not just a rule exemption.
  4. Close Serial Tester or any other app using the FreeD port before testing.

Step 3 — Configure Unreal Engine

In Unreal Engine, set the listening IP address to 0.0.0.0 (not the Flair PC's IP address). Using the Flair PC's IP as the listen address in UE is a common misconfiguration that prevents reception.

Step 4 — Verify with Serial Tester

Use the MRMC Serial Tester app on the VP machine to confirm UDP packets are arriving on the correct port before troubleshooting UE settings. If Serial Tester sees data but UE does not, the issue is in UE configuration or firewall policy.

Unreal Engine 5.6.1 — Minimal FreeD Receiver Setup

The following steps are from Simon Wakley's minimal field guide ("SetUpUnrealFreed.docx", posted 2025-09-27) for Unreal Engine 5.6.1.

Prerequisites

  • Unreal Engine 5.6.1 or later.
  • VP machine on the 192.168.1.xxx subnet, connected to the InTime switch.
  • Windows Firewall fully disabled on the VP machine.
  • Flair configured to send FreeD UDP to the VP machine's IP on the agreed port.

Steps

  1. Enable the LiveLinkFreeD plugin In UE: Edit → Plugins → search "LiveLinkFreeD" → Enable → restart editor if prompted.

  2. Open Live Link Streaming Manager Window → Live Link → Live Link Streaming Manager.

  3. Add Source → LiveLinkFreeD Source Click + Add Source and select LiveLinkFreeD Source.

  4. IP Address: 0.0.0.0 — do not enter the Flair PC's IP address here. 0.0.0.0 tells UE to listen on all interfaces.

  5. Port: match the port configured in Flair's External Devices output (e.g., 55535).

  6. Save as Preset Save a Live Link Preset so you do not have to reconfigure this every session.

  7. Add a Cine Camera Actor In the level, place a Cine Camera Actor (not a standard camera).

  8. Add Live Link Controller Component Select the Cine Camera Actor → Add Component → Live Link Controller. Set its Subject to the FreeD source. The camera should now track Flair's position data.

Common Mistakes

  • Using the Flair PC's IP instead of 0.0.0.0 as the listen address in UE — this prevents reception.
  • Windows Firewall only partially disabled (rule exemption instead of fully off) — use fully off during setup.
  • Serial Tester left open on the same port — close it before testing UE. See Serial Tester.

"Enable LiveLinkFreeD, Live Link Streaming Manager, Add Source → LiveLinkFreeD Source, IP 0.0.0.0, port matching Flair, firewall off, save preset, Cine Camera Actor, Live Link Controller." — Simon Wakley (field guide, 2025-09-27)

If the VP Machine Cannot Use 192.168.1.xxx

If the VP team's software is locked to a different subnet and cannot be changed:

Use TouchDesigner as a free network bridge running on a separate machine: - Input: FreeD In CHOP (listening on InTime subnet, 192.168.1.xxx) - Output: FreeD Out CHOP (sending on the VP subnet)

This can run on a low-spec laptop or the Flair PC itself (though running it on the Flair PC uses CPU resources).

Broadcast Traffic Warning

Unreal Engine and Disguise can generate significant UDP broadcast traffic. On an unmanaged switch, this broadcast traffic can saturate the InTime network causing packet storms that intermittently disconnect the robot.

Use a managed switch in VP setups

If Unreal Engine or Disguise is connected to the same switch as the robot network, use a managed switch that supports broadcast storm control. An unmanaged switch will pass all broadcast traffic to all ports including the robot's EtherCAT connection, which can cause robot disengagement.

WhatsApp Excerpts

"You must use the Port with the same 'family' — 192.168.1.xxx" — Arturo (2025-06-13)

"Don't use .20" — MRMC Support (2025-06-13)

"If you're using INtime on a Windows machine then you'll need to make sure the Aximmetry machine is configured to match the INtime subnet or else you won't see any data (192.168.1.xxx)" — Ben Myers (2025-10-22)

"I'd go Flair Intime - UE direct. Set static IP on UE to like 192.168.1.99 / 255.255.255.0. Confirm UE firewall is off. Ping UE to Flair comp. If working, network is working." — David Jeffries (2025-06-13)

"I believe you need the IP of UE to be local host, not Flair, as well." — David Jeffries (2025-06-13)

"It's working! Thanks guys! It was an IP issue." — Francisco Aguila (2025-06-13)

"If they're not able to change their IP, you can use TouchDesigner as a free network patch in between [FreeD in CHOP > FreeD out CHOP]" — Ben Myers (2025-10-22)

YouTube How Motion Control Powers Virtual Production

▶ 01:02 — Tracking data flow from camera/robot into virtual production systems

Official Documentation

Bolt Quick Start Guide — p.41–42: Appendix 2 Network Layout and EtherCAT Architecture

Flair Classic Manual — Ch.5 Setups: External Camera Setup — p.90

Flair Classic Manual — Ch.22 Network Direct — p.313

Flair 7 Manual — Ch.5 Setups: External Camera Setup — p.52

Flair 7 Manual — Ch.19 Network Direct — p.263