MHA Depth & Stereo

General Feedback & Requests
,
1

Hi, three questions here.

  1. When processing depth data in the Performance Asset, the new documentation for 5.6 mentions the Skip Per Vertex Solve and that solving is more accurate.
  • In what regard is it more accurate?
  1. For the Skip Filtering, it is mentioned that the curves will either be post processed for smoothness or you can use your own filters.
  • How would someone create and apply their own filters?
  1. For Stereo HMC data, using the UE5.5 and earlier workflow there are many instances where the control curves are incorrect such as the jaw dropping open when the lips were sealed, along with a few others.
  • Have any improvements been made to way the data is solved and mapped to the control curves? If so, where can we see a changelog of those updates?
2

Hey!

Sorry we took a while to respond on this one.

  1. When Per Vertex Solve is enabled, it allows the solve to go ‘outside’ the constraints of the rig, adding a tiny offset to each vertex so that it exactly matches the target solve. This will indirectly slightly improve the solved controls / curves since each individual frame will be closer to the target. To get the better results it relies heavily on having very good input data, eg well calibrated HMC or Scanner.

  2. For the depth based pipeline, this is not possible for users at this time. For realtime or the mono pipeline there is this page within the docs on how to use it.

  3. There haven’t been any improvements on this.

Hope that helps!

Cheers

James