Bump this thread please. Anyone from @aximmetry?

Hi David,

We will need a bit more information to figure out where things go wrong.
Do you use Vive Mars or just the normal Vive?
Do you use it with calibration files? Does every camera have its own calibration file? Also, did you set anything in the ORIGINs and SCENE panels in the Inputs control board?

Warmest regards,

Hi Eifert@Aximmetry

Hi David,

You are using the Aximmetry Camera Calibrator?
If so, did you try to do the camera calibration with each tracker and camera, while having the same up rotated setting?
In theory, the camera calibrator should work out on its own if the tracker is up rotated or not, and you shouldn't touch that setting at all.

If it still occurs, you could try what Ahmed says in this thread: https://my.aximmetry.com/post/1163-htc-vive-tracker-30-axis-are-inverted

Warmest regards,

Hi Eifert! Thanks for your replies. Another shot at calibration solved the problem. Now we encountered another one. We are combining Unreal with Aximmetry renderer. We have created bar chart in aximmetry and injecting it into Unreal scene. But even after exposing cam trans to unreal, we cant match right FOV/focal distance so when we use virtual camera move, move of the chart doesnt match with the scene. Any suggestions how to solve this one? Thanks!

Hi David,

Can you show your Flow Editor setup?

If you used the Render_General compound to render the chart in Aximmetry. Then the Unreal scene and the Aximmetry rendered chart should have the same camera properties as FoV, as the Render_General reads the camera properties from the Camera compound. It uses transmit modules to do so.

https://aximmetry.com/learn/tutorials/for-aximmetry-de-users/aximmetry-and-unreal-combined-rendering/ 

Warmest regards,