Configurable FOV max and min

[pablospe]

In file ViewControl.cpp#L36:

const double ViewControl::FIELD_OF_VIEW_MAX = 90.0;

I was wondering why there is a strict max for the FOV.

As example, one could need to render a depth map from a mesh using the headless rendering example, but such strict limit would restrict the possible camera parameters that can be rendered. More precisely, I am using ConvertFromPinholeCameraParameters and this limitation happens in ViewControl.cpp#L36

field_of_view_ =
std::max(std::min(fov_rad * 180.0 / M_PI, FIELD_OF_VIEW_MAX),
FIELD_OF_VIEW_MIN);

Same for the zoom control, but there is already one issue for this purpose: issue #497

[pablospe]

Related issues: #1417 and #1389
Also related issues: #727 and #834

Many people is having similar problems, I think it should be allowed a more flexible function.

[pablospe]

To made it work I commented some code, something like this: pablospe@206f926

Recompile Open3D (and if you want the python wrapper):

cd build/
make install-pip-package -j16
pip3 install lib/python_package/pip_package/open3d-0.8.0.0-cp36-cp36m-linux_x86_64.whl

For headless rendering you need to activate on cmake this option: -DENABLE_HEADLESS_RENDERING=ON

[radmahdi]

To made it work I commented some code, something like this: pablospe@206f926

I am afraid this just ignores the assert function, and the parameters are not really taken into account!

[germanros1987]

@pablospe this is solved in the new version rendering API.

[pablospe]

From what I see there is not a way to render to an image or depthmap with the current API (the equivalent to capture_depth_float_buffer). Also the option to use intrinsic/extrinsic matrix to control the view.

Based on this replies:
#2190 (comment)
#2190 (comment)

Do you have more information about it?

Also I recently pushed a PR #2564, which allows this with the old viewer.