Problem summary
Perspective camera settings including Far Clipping Plane are set to incorrect values after loading projects
After launching and loading a project, the Far clipping plane is set to 0.0 meaning the Object is not visible in the Perspective view. Closing/opening projects then inconsistently sets the Near/Far/FoV fields to different values.
Customer reported version
Mari 4.8v3
Customer reported platform
Linux
Steps to reproduce
1) Launch Mari and open any project
2) Switch to the Perspective view and check the Near/Far clipping planes and FoV settings.
Notice that the Far clipping plane is set to 0.0 instead of 1,000.0.
3) Change each setting to something memorable, e.g. 0.25, 2,500.0, 25.0
4) Close the project, reopen it and switch to the Perspective camera again
Notice that the Near field has been set to 0.1, but the others remain the same
5) Repeat step 4 multiple times, notice that a different field is reset each time a project is opened.
Expected behaviour
Each time a project is loaded, the Perspective camera settings should be reset to:
Near = 0.1
Far = 1,000.0
FoV = 34.0
Actual behaviour
The first time a project is loaded after launch, the Far clipping plane is set to 0.0 instead of 1,000.0.
After changing the values and closing/opening projects, a different field is changed each time a project is opened.
Workaround
Running Camera > Reset Camera while in the Perspective view will reset the Camera settings to the correct values.
Reproduced by support
This bug has been reproduced in:
Mari 5.0v3 - Windows 10 - CentOS 7.9
Mari 4.8v3 - Windows 10
Unable to reproduce bug in:
Mari 5.0v2 - Windows 10
Mari 4.8v2 - Windows 10 - CentOS - regression
Earliest version tested
Mari 4.8v2 - This issue doesn't appear in this version and has regressed