I have a habit of figuring these things out as soon as I post about them...

So it turns out it's the Focus Sensor Data I waned from the camera tracking module...

That I was able to plug in to my focus value to control the focus point in UE. However, it's off by a factor of 100 so a simple divide and you can get accurate focus distances...

Aximmetry doesn't natively control the aperture (It's set to a default F2.8). I find this to be slightly off from what I tend to use in the studio (around T5.6). So you can either set this manually or edit the blueprint to access the camera aperture as a scalar from aximmetry.

Hi,

Note that Aximmetry uses the Focus Distance pin. This pin gives out a value that is already adjusted, so there is no need to divide it:

You can access this pin without opening the unreal tracked camera compound, like this:

The Focus distance value is sent to Unreal through the Control Data connection. You can access and modify the Focus distance within this Control Data collection by changing the Cam Focus collection value.

Warmest regards,

That's what I thought, but the focus distance value wasn't changing when I moved the focus encoder, which was why I ended up using the focus sensor value. This was fine as I could just plug it straight back into the focus distance (with the multiplication applied). The only reason I had to edit the camera blueprint was to be able to adjust the aperture to match my lens. (This isn't hooked up by default)

Hi,

To clarify my previous misleading comment, the Focus Distance pin only works when the tracking system sends calibrated focus data or when a Calibration profile is selected with focus calibration. Currently, it is possible to make focus calibration like this in Aximmetry: https://aximmetry.com/learn/tutorials/for-studio-operators/basic-lens-calibration-without-lens-distortion/#focus-encoder
The Focus Sensor pin will return data even when there is no calibration.
You could use the previous link to make focus calibration and then you would no longer need to do your own multiplication.

Warmest regards,

Hi,

Aximmetry 2025.2.0 BETA has just been released.
This update introduces general handling of camera aperture settings throughout the system:

• Calibration Profiles now can contain a mapping between the raw Iris Encoder values and the F-number (called Aperture throughout the system). It can be edited in the Basic Calibrator app (or directly in the XML file).
• Iris encoder value is read from protocols that support it. (Free-D officially does not support it, but some tracking systems like HTC Vive Mars use the spare "user" field for that purpose, and Aximmetry reads that.)
• Some camera tracking systems and protocols are capable of sending the final aperture value (Canon CV Protocol, NCam, Trackmen, AGTP). In these cases this value is used.
• For Virtual Camera paths, the aperture values can be defined for the A, B points both by mouse combination (Alt + Space + Right Mouse) or numerically.
• Record_3-Audio: aperture is added as an animated user property to the FBX.

Warmest regards,