Future of VRayPhysicalCamera?

[Morne]

Hi team

So what's the verdict here? Is the VRayPhysicalCamera officially scrapped and will eventually be phased out even from Maxscript, or can we hope to see a new improved VRAY Physical Camera returning to the UI somewhere in a next version?

[cheerioboy]

Yeah this makes me sad that they gave the camera over to Autodesk. In max 2012 at least, I would have wished for a tweak to the camera so that when exposure is ticked off, it uses the global vray exposure control. Then I could use them. At the moment I have too many cameras to deal with all the individual settings. So it's basic max cameras with the Vray Exposure Control.

[glorybound]

I like the Physical camera. I had to use a V-Ray Camera yesterday and forgot how to use it, already. What don't you like about it?

[Morne]

What don't you like about it?

Well, for one thing, their internal calculation for the ISO is based on a different model than the V-Ray one. Therefore, with the same exposure values, the new Physical Cam will always render brighter. There's a couple other small things that adds up.
Overall the "idea" of it is great, just wish it stayed in ChaosGroup's hands

[glorybound]

The DOF seems to be missing. I have spent the past 1/2 hour trying to turn it on.

[werticus]

DOF isnt missing. But one thing the new max camera does not do (in 2016) is guess the shift. You can only tick the box 'auto guess' not just 'guess right now.'

Which does not keyframe animate properly. If you do a DR render the nodes don't pick up the auto guess is ticked and you end up with buckets that are not aligned the same.

So i guess this is a bug.

With the old vray camera you can easily key frame the guess shift button and it works over dr too. So for this reason alone I import the old camera from old scenes into the newer scenes and they work fine.

vlado should probably look into that, we really need the old camera in vray still, and I wouldnt hold my breath for autodesk to actually fix anything.

[jacksc02]

You can still create vray physical cameras in 2017.
Use this maxscript - vrayCreateVRayPhysicalCamera()

[Morne]

You can still create vray physical cameras in 2017.
Use this maxscript - vrayCreateVRayPhysicalCamera()

Jip, most people know this. Max's camera has bugs. We all know this too. The point of my original question was to see if ChaosGroup understand that users are frustrated and want the VRay cam back into the UI. If they do that, maybe we can also get some improvements to it, like for example EV, which is pretty cool. So far however, they're yet to comment...

[Vizioen]

Jip, most people know this. Max's camera has bugs. We all know this too. The point of my original question was to see if ChaosGroup understand that users are frustrated and want the VRay cam back into the UI. If they do that, maybe we can also get some improvements to it, like for example EV, which is pretty cool. So far however, they're yet to comment...

Might be better to bring it back indeed, I want clipping (far and near) to be disconnected for instance, and I know a lot of people might use it. So I can clip near but not far for instance. Autodesk won't listen I'm afraid.

[vlado]

Well, I was hoping that we could forget about the V-Ray one and just have everyone switch to the Max Physical camera - it's one less thing for us to worry about.

But, if the Physical camera is indeed not worked on anymore, we won't have much of a choice except to bring the V-Ray camera back.

Best regards,
Vlado

[Art48]

Let's just hope AD fixes it. Thank god I'm still on 2014. Although I do miss MCG :P