Physical Camera problem in 3ds max 2018

[Anonymous]

Hello all! I did not find a similar theme on the forum.

My problem is this: In the latest versions of 3ds max (2017-2018) happen some problem with the Physical Camera.

I configure in one scene several options for lighting and camera position with animation keys. Each frame of animation goes to composing and I need hold my camera in one hundred percent correct positions. But the last time I have a problem with this. When I close my scene and open it again the camera has another perspective but all settings the same like early. And also the camera target looks like skewed and in other coordinates.

Also, I can’t merge camera from earlier versions of files because it happened to all of them.

I suppose this is due to a combination of Perspective control (Lens shift and Tilt correction) and animation keys. If so, how can this be fixed? Or how in future don’t make the same situation?

thank you all in advance!

[doug_bowker_3D]

I feel like I've had this issue in some scenes too. I reopened a scene that had not been touched since outputting rendered frames, and when then linked some new objects and rendered them out to a new layer, the perspective was off. I went back and pulled in the first set of frames and sure enough things didn't line up. What the hell? It was like a whole different FOV had been used! 

Another thing: I have had cameras set up with Target and then when I turned the target off the camera just looses it's position or FOV settings! Definitely something buggy going on here guys!

[Alfred.DeFlaminis]

Hello @Anonymous and @doug_bowker_3D,

Which renderers are you using here?  I'd like as much info as possible about this and if you have any scenes you can share that would really be great.  The more renderers the better.   You can strip out the good stuff to protect your clients, just need a box or something as a stand in for geo.  Thanks for any extra info you can provide or any scenes with the problem so I can attach them to the correct cases in the tracker.  

Best Regards,

[Alfred.DeFlaminis]

Hello @Anonymous and @doug_bowker_3D,

I just wanted to follow up here, any thoughts on my previous post? Thanks for the update!

Best Regards,

[doug_bowker_3D]

Thanks- Been swamped but when I come up for air I'll see about getting you a file to test.

[Anonymous]

thank you, Alfred!
I use Vray 3.60.01.
I attached two files with camera bug.

[Alfred.DeFlaminis]

Hello @Anonymous,

I cannot repro this with 3.60.03.   (Or on other renderers.)  Can you please update your Vray to the latest version for me?

Best Regards,

[Anonymous]

I've had this problem since the cameras were released in 2016. If I remember correctly, I posted the problem in the forums, but not enough people noticed the problem to help I haven't found a solution with the updates that have been released.

I refuse to use them. They almost never hold position for me. When we did try to use them, we got same result on 3 different computers. We had a 10,000 frame animation with the camera being animated. We were having such an issue that we had to ditch the physical camera and re-animate with standard cams. Very frustrating. We almost missed our deadline because of this glitch.

I will only use them on still single frame rendering...sometimes.

Dean

EDIT: The only way we could get the cameras to temporarily snap back into position was to change out render quadrant to perspective, then back to camera. This was not a permanent fix however. If still acted up.

[Alfred.DeFlaminis]

I know it's happening @Anonymous, I just cannot reproduce it.  If you have any scenes which exhibit this issue I would greatly appreciate as many files as possible.  You can replace the nitty gritty with boxes but the more files I have the merrier.  Does it only happen with certain renderers for you?  It would be especially great to get some scenes with this issue that aren't using 3rd party renderers.  

I've seen this reported a good 10 times in the past year.  I logged each and every one of them if I could repro.  Then they get to QA and they cannot repro, similar to how I could not repro on the above scenes.  (Which I do believe showed the problem before they were attached.)  I'd like to get some scenes that show the issue with Art, Arnold, Scanline, etc. to demonstrate that the issue is not tied to 3rd party renderers.  Thanks!

Best Regards,

[Anonymous]

@Alfred.DeFlaminis, Since we were having issues, we stopped using them for the vast majority of our projects. I'll put them back into use for certain projects in the "hope" that I'll get them to act up. We don't use any rendering engine other than MR. Once we finally transition to 2018, I'm sure we will get up to our heads on Arnold.

[Alfred.DeFlaminis]

Understood, thank you @Anonymous.  If you (or anyone else) has more scenes with the problem, please attach or PM me a link.  Thanks!

Best Regards,

[Anonymous]

I'm sorry, but we updated vray pair weeks ago. And it is for a big render farm with a lot of computers. I asked my sysadmin about the new version vray, and I must wait some time. (

[Alfred.DeFlaminis]

Understood @Anonymous.  Maybe just test on a single machine when it's time, I know updating a whole studio takes some time.  Thanks!

Best Regards,

[jon.bell]

Hi @Anonymous,

I'm just reviving this thread to see if you had solved this issue, and if so, what the outcome was.

Could you please post here and let us know? (And if it is resolved, mark your Solution.) Thanks, and we hope to hear from you soon!