Converting max16 physical camera to max14 Vray camera/standard camera

[thomaskc]

Hi everyone,

I have run into an annoying problem.

The "new and improved" camera in max2016, is causing me a headache. I have a camera animation done in max2016 using the new camera that I somehow have to try and convert into a max 2014 scene.

Converting is easy, save as.... done... yet the camera completely breaks as max 2014 doesn't recognize the camera. (I also got 2-3 other vray related dll errors, sorry can't remember the exact names right now).

So my question is.. anyone know of an easy way to convert this camera? script to rip the info and create a new one with that info?

Thanks guys!

Edit: I have attached the vray errors I get when trying to open a "save as 2014" file with a max16 physical camera in it.

[thomaskc]

So it looks like I can create a new vrayPhys Camera, put in the same lens values, and link it to the helper 16 creates after given those errors. Animation seems to stay intact as well.

[Morne]

Just remember, you can't use the EXCACT same values for the camera. The new 2016 camera has a slightly brighter exposure. That is because the new one use a formula for the ISO provided by Kodak, and the older traditional VRayCam use an ISO formula from the ISO standard.

[thomaskc]

Interesting, thanks for that.

I am also finding that it's painful when you are doing continues animation on the camera, as if you do as I suggested, all you are doing is linking the new camera to an existing dummy, but if you need to animate the fov and other things, or adjust existing fov changes.. it because really fiddly. Still wish there was a way to go backwards.

[thomaskc]

So I have managed to save my scene out and it's running in max14, camera keys have been copied across to an "old" VrayPhysical Camera.

I still have the problem of the following vray files from 16, missing and giving me an error when I open the 2014 scene. I worry that this will cause a shit storm when I eventually have to render this project?



Any help on how to get rid of these would be amazing!

I get these errors when I open the scene, and also if I try to merge everything in the scene into a fresh clean scene.

[svetlozar.draganov]

If you intent to work on both platforms 2016 and 2014 it would be better to use VRayPhysical Camera instead 3DSmax Physical Camera.
Vray Physical Camera in Max 2016 is accessible via the following maxscript-command:

vrayCreateVRayPhysicalCamera()

I don't think that there is out of the box way to convert 3DSMax Physical Camera to V-Ray Physical Camera but what you can do is to align and parent V-Ray Camera(and target) to Max Camera(target) and then save the file in version 2014. Then when you open that file in Max 2014 you will still get the same error but the V-Ray Camera will still work as expected since Physical Camera nodes will be replaced by dummies and their animation will be kept.

Here is a quick example(please note that the Exposure Control is also changed to Vray):
2016:_________ 2014(rendered in Max 2015)


scene 2016: http://ftp.chaosgroup.com/support/sc...to_vraycam.max
scene 2014: http://ftp.chaosgroup.com/support/sc...aycam_2014.max

[JezUK]

That is because the new one use a formula for the ISO provided by Kodak, and the older traditional VRayCam use an ISO formula from the ISO standard.

Thanks Morne, nice to know

[3LP]

Thanks Morne, nice to know

Yes Morne, nice one!
Where did you get info btw?

Stan

[Morne]

Where did you get info btw?

It was a support request and that was the answer I got from ChaosGroup Support

[3LP]

Nice, behind the scene info heum

Well done

Stan

[thomaskc]

If you intent to work on both platforms 2016 and 2014 it would be better to use VRayPhysical Camera instead 3DSmax Physical Camera.
Vray Physical Camera in Max 2016 is accessible via the following maxscript-command:

vrayCreateVRayPhysicalCamera()

I don't think that there is out of the box way to convert 3DSMax Physical Camera to V-Ray Physical Camera but what you can do is to align and parent V-Ray Camera(and target) to Max Camera(target) and then save the file in version 2014. Then when you open that file in Max 2014 you will still get the same error but the V-Ray Camera will still work as expected since Physical Camera nodes will be replaced by dummies and their animation will be kept.

Here is a quick example(please note that the Exposure Control is also changed to Vray):
2016:_________ 2014(rendered in Max 2015)
[ATTACH=CONFIG]26584[/ATTACH][ATTACH=CONFIG]26585[/ATTACH]

scene 2016: http://ftp.chaosgroup.com/support/sc...to_vraycam.max
scene 2014: http://ftp.chaosgroup.com/support/sc...aycam_2014.max

Thank you for the reply, this is the method I have resorted to, and even gone further and actually copied the animation from the max16 camera to a new vray camera in 14, because the animation isn't final yet.

Had I planned to work in both I totally would have avoided the new max16 camera, but we seem to have a lot of issues with max16 and our renderfarm currently so I am trying to revert back to 14 so I don't run into problems further down the track.

I am how ever concerned that the dll errors I get when opening my scene in 14 will cause render issues on the farm?

[Zdravko.Keremidchiev]

What sort of issues do you have with the network rendering. Are they camera related?

I am how ever concerned that the dll errors I get when opening my scene in 14 will cause render issues on the farm?

This will depend on the render manager, some of them have an option to ignore error messages.

[Vizioen]

Just remember, you can't use the EXCACT same values for the camera. The new 2016 camera has a slightly brighter exposure. That is because the new one use a formula for the ISO provided by Kodak, and the older traditional VRayCam use an ISO formula from the ISO standard.

Seriously? Any more information on that? Why don't they communicate this?

[Morne]

Why don't they communicate this?

Probably because its not the same thing. If you add a vraycam in 2016 using maxscript, then that cam and the one in previous versions, will be the same.
The physical camera is "new" and "improves" on the old standard vrayphyscam. (old paradox, how can something be both new and improved hehe)

[pixela]

Hi guys,

One question: If we have a vrayPhysicalCam from an older scene and want to convert to the new Physical Max Camera,
Is it necessary to use the Exposure Control under Environment and Effects? There is a new Physical Camera Exposure here and I am a bit puzzled about this.