If I use the Toolbar button to create a VrayPhysCamera from a perspective view, the camera view is distorted. The Focal length looking now is at 152400.0 mm and there does not seem to be a way to recover this. Changing values has no effect. I don’t remember this being like this before the Vray 5 hotfix.
It’s not a recent thing. It usually happens when creating a VRayCamera from in either Top, Bottom, Left, Right, etc. views since the camera tries to adapt to a non-physically accurate view.
No, this happens every time I try from regular perspective views. Does it work for you?
Yes, it works fine from perspective views. Does this happen on a specific scene? Could you attach it here?
When that happens, have you tried selecting the camera target and moving it away from the camera (i.e. into the view)?
I restarted Max and haven’t had it happen since, but will try that next time.
Im having this issue or similar as well as that im not sure the ‘vert shift’ is working correctly all of a sudden.
If I create a new camera using toolbar, same as OP, it creates a cam with focal length of 5000.It also seems to double the vert shift value, if i repeat the process you can see the camera going crazy (see video link) Restarting max fixes it i think, but it breaks again.
I also noticed that if change the ‘free cam’ to a targeted, the target line doesnt look correct in the viewport, and the target box is rotated oddly.
Ive attached a scene.
Video link
https://drive.google.com/file/d/1tfw…usp=share_link
Vray 6 hotfix 3
02_3dsmax.zip (196 KB)
Often happens to me for years when creating from a perspective view (although I have to tried camera from T,L,B,R) and this tip from LeLe and always seems to fix it quickly.
ignore this post
I have this every single day. Every second time I create a camera, this happens. I never found the cause and got used to it.
I only have a 0.0 target distance for ortho views, and i have asked we change that to a unit (whatever that may be in real units.).
For perspective, i couldn’t (ever) repro the behaviour, and may imagine it could be due to unit setup, but in that case too i couldn’t make it misbehave, no matter how skewed i set the units up.
Fresh start of max, did it straight away..doesnt always happen…but notice how the target mode isnt on by default. (see attached video)
Also, and this is more likely because of newness to 3dsmax, but when i used the create cam from max’s create menu, the target option isnt togglable…just greyed out.
cam.zip (488 KB)
it’s shown in my gif how to fix it: set camera target distance to anything but zero while the fix is implemented.
Interesting, I had the same problem today. My Vraycam FOV was 5000 and changing the values did nothing. Multiple cameras had this issue. The software crashed on the weekend, so maybe the cameras got corrupted.
What I did was select the broken cameras, save select and create a new file. Then I went into this new file and the cameras worked properly. So I merged them back into the scene and deleted the old corrupt ones. Problem solved, for now. I use Vray 5, 2.3
There is some more weirdness, too. Some values from an old VrayCam are carried over if you create a new one. Values like vert/horizontal shift/tilt.
I found another issue of this kind, something I don’t understand. If you have a VrayPhysicalCam, you disable “Targeted” and use Focal length instead of FOV, which is my default workflow. If you then change the Target Distance, the FOV will change, even though you have target mode deactivated. You can see the FOV change, in the viewport and in the values. But the focal length stays the same.
Why is this happening? 
When using the FoV mode, the camera is instructed to strongly adhere to the FoV value, at the expense of any other parameter: change target distance in this mode, and see how the Focal Lenght changes to accommodate the selected FoV.
When however one is in Focal Lenght mode, priority is given to the Focal Lenght, and the resulting FoV changes based on target distance.
This is the physical modelling of the camera, and its expected behaviour.
The fix for the ortho views is now in place in nightlies, for those with access, I will write here again when it’s made its way into the stable builds.