Major issues with exported cameras

[fixeighted]

When a camera is loaded to Max from a Vantage config file, although the values are exactly the same the rendered frames do not match.
I believe I have narrowed this down to how the FOV and Focal length are translated between the two.
In my example, in Vantage the settings are as in the image, whilst in Max they come in differently, with the FOV the same but the Focal Length shifted, causing the mismatch.

There is some glitch In Vantage; changing the focal distance changes the fov value, you can easily test that when you do change the focal distance, then change it back again, the fov value shifts to different values.
In my example, I load the scene as config....the values are focal length 15.859/fov 97.101....I go up on the spinner to focal 15.959 and the fov value changes 95.434...when I revert to focal length 15.859 the fov has shifted to 95.802.
This also causes a significant shift of course. As these values are wired together there's no way of getting back that value unless I reload the scene.

Also, If the Lens Mode is set to Focal Length, then ( in my example the focus distance is set to .637 ) if that is set to e.g. 1.637 then the camera shifts very noticeably, whilst the fov and focal length stay the same.
If Lens Mode is set to Field of View then there is ony an almost imperceptible shift.

I have discovered that if I leave the Vantage set to Lens Mode - Focal Length and ignore the wrong fov value, then in Max I need to conversely ignore the incorrect Focal length and instead use the 'correct' fov value from Vantage.
This has taken the best part of two days to figure out, so hopefully this info is of use in trying to fix the mismatch

[npg]

....the values are focal length 15.859/fov 97.101....I go up on the spinner to focal 15.959 and the fov value changes 95.434...when I revert to focal length 15.859 the fov has shifted to 95.802.

I was able to reproduce this, but only after I also entered the same focus distance as yours. So the thing is that focus distance affects the conversion (FOV and focal length are different ways to express the same thing, so we have them linked this way in the UI). This is what real lenses do -- the image changes slightly when you change focus. But our UI doesn't update properly to reflect this when you change the focus distance -- this is the bug. So you only get the proper fov/focal once you change some other parameter that affects fov<>focal conversion. I think as long as you do that (change fov, film gate, whatever - up and down) after changing the focus distance and before saving out a .vantage file you should get the correct values. This is a workaround until we release a fixed version, of course.

[fixeighted]

Yes I actually discovered that it does correctly revert to values if changed once...or something like that. It was really confusing trying to work out what was happening, so I admit to getting very lost down that rabbit hole

I still need to use an online calculator to get the values into Max, which although is not ideal is at least a solution to that extra little hurdle.

Luckily, once this project is over I will never have to do these particular things again. It is only because I have to help the client manipulate things also, using a 2018 version of Max and having very little knowledge of either 3D, Max, or Vantage....total nightmare

Thanks for the response...at least he is loving the freedom this gives him as a cameraman in reality