Focal length doesn't import correctly

I thought I had this workflow sorted but now I’ve found that a merged camera (.vrscene) will not have its correct focal length as set in Max.
Instead it ‘appears’ that it takes its value from the ‘home’ camera settings, which is is extremely frustrating.
So it will import with animated F#, animated focus distance but not even a proper static focal length.

What is even more bizarre is that with the sensor mode set to focal length, I can see the fov value animating, even with a supposedly fixed value.
And conversely, if the sensor is set to fov, then the focal length value animates. I simply don’t understand that.

Whilst I realise I can reset the focal length to its proper value, this does mean that we can now not animate that value to begin with, as the camera is in a .vrscene.

Sorry if I have already mentioned this in one of the many other posts regarding these issues…I really did think these problems were solved and I’m just so
exhausted with it all…wish I had never started with it…

I just exported another scene, this time an animated range, with a load of different cameras.
Seemingly randomly, only one of those cameras comes in with the correct settings, whilst all the others are completely screwed, all taking their settings from
it appears different cameras…some correct, some not.
It is just broken and I cannot trust it in any meaningful way.
We are so deep into the project that we have no other choice but to hope it works by accident if we try enough times…LOL now that is some serious stress right there :stuck_out_tongue:

Hi fixeighted,

Yes, we are aware of the issue. It is also reproducible when importing a scene with multiple cameras. We are looking into it but cannot say if it will get fixed for the next release.

Best regards,
Alexander

Ok. thanks for mentioning this, as I don’t believe anyone else has done so and I was beginning to doubt my sanity :stuck_out_tongue:

What is even more bizarre is that with the sensor mode set to focal length, I can see the fov value animating, even with a supposedly fixed value.
And conversely, if the sensor is set to fov, then the focal length value animates. I simply don’t understand that.

If you have the sensor mode set to focal length and the focal length is animated, Vantage will recompute the FOV from the focal length.
Same thing if you have the sensor mode set to FOV and the FOV is animated, Vantage will recompute the focal length from the FOV.

This is normal. The only issue it will create is overwriting the parameter that is not animated.
It this an issue ? If you have one of them animated and selected as the “sensor mode”, I assume you are not going to use the other ?

I thought I had this workflow sorted but now I’ve found that a merged camera (.vrscene) will not have its correct focal length as set in Max.
Instead it ‘appears’ that it takes its value from the ‘home’ camera settings, which is is extremely frustrating.
So it will import with animated F#, animated focus distance but not even a proper static focal length.

We will try to fix this ASAP.

Greetings,
Vladimir Nedev

No, this is with no animation of the focal length :slight_smile:

We have decided to not animate this value, as in any case it will not work, as mentioned above. Well, it works sometimes, on maybe one camera, then not others.
But then the length is screwed so that is immaterial. Head hurts…must stop :stuck_out_tongue:

So that is why it is weird that the value animates spookily of its own free will when it has no changes. Ghost/machine…
Luckily the incorrect value can at least be reset correctly on merging a static length.
We’ll stick to this for the remainder of the shots, as we forced everything else to basically work.

So that is why it is weird that the value animates spookily of its own free will when it has no changes. Ghost/machine…

Can you get us a vrscene/vantage scene and steps to reproduce this ?
It sounds like something that shouldn’t happen.

Greetings,
Vladimir Nedev

We have decided to not animate this value, as in any case it will not work, as mentioned above. Well, it works sometimes, on maybe one camera, then not others.

I don’t completely understand. It’s best if you send us scenes we can test with and confirm our fixes.
We would need the .max scene as well.

Greetings,
Vladimir Nedev

Sure…I will try and send something tom
morrow…

You didn’t know at the time, but we were supposed to release 1.4 on Wednesday, so you reported the bug “in the last moment”. We had to delay by one day to fix this focal length issue and one other issue. Can you confirm your cameras now have the correct FOV/focal length?

Ah ok…I didn’t realise there was any update. I will check. Thanks.

I began a separate post about this as it seemed simpler to address this in view of the update.
Sadly not good news :frowning: