This was the point of my post chadstevens. Chaos group handed Autodesk a really good camera system and Autodesk mangled it with unnecessary tabs and removed features.
I would love to see the clean layout of the original camera back in Chaos group’s hands since this will be never be updated again. (I know you can access this via script)
I am trying not to be negative but Autodesk after almost 5+ years of shelving Max they seemed to have finally showed some sort of real development in 2016.
I’ll will post this on the Autodesk forums and update if I get any results.
Update. Autodesk has created a support request about this. I will update if they send feedback.
After some fiddling with the new physical camera settings it appears by default the physical camera exposure is overexposed compared to the original Vray Physical Camera (using the same camera settings).
The only way to get the exposure to match you need to change the Environment exposure control Physical Scale to 750 candelas / RGB.
Does Chaos group have a recommended workflow for this since we will need to either use a different physical scale or accept the difference and adjust exposure control to suite.
I am mainly concerned since we regularly match photos to real values.
Glad to hear that you havfe found a way to match both cameras, I have tried it here but I still got a different result between both(Phys.Camera is slightly brighter).
Does that setup works always in your environment? If it is we might considered it as a useful workflow to match the exposure between both cameras.
Thanks Svetlozar,
Actually I tried this again and it is a bit confusing what is happening. Each time I tried to replicate the values they did not seem to match.
So no it did not work in different environments. Is it buggy or am I doing this wrong?
Autodesk has confirmed they are using there own formula for Max’s physical camera exposure. So this means Max’s Physical camera and Pre 3.3 Vray Physical cameras will never match exposure with the same settings.
I presume will need to accept the brighter exposure and adjust to work with those values going forward?
I still do not get why the ISO and Shutter Speed default values are really high numbers but they assured me this is normal.
I ran a quick test sampling different f-stop values with an old vray camera and the new Phys. Cam. and the results are exactly linear, see below. I sampled the float values for each camera and just did a simple division between the terms.
f-stop
VrayCam
PhysCam
b/a
a/b
16
0.03
0.039
1.3
0.769231
8
0.119
0.155
1.302521
0.767742
5.6
0.244
0.317
1.29918
0.769716
4
0.477
0.62
1.29979
0.769355
2.8
0.974
1.268
1.301848
0.768139
2
1.9
2.488
1.309474
0.763666
1.4
3.89
5.073
1.304113
0.766805
Average:
1.302418
0.767808
All that’s needed to match the Phys. cam to the old cam is a simple multiplier for either the light values or even easier the camera ISO. The Physical camera overexposes by 30.5 percent so to get a perfect match (within a few decimal places) just divide the ISO by 1.302 (or multiply it by .768 ). Let me know if I’ve overlooked something.