3d view focal lenght and camera focal lenght don't match (2.73 rc1) #43039

Closed
opened 2014-12-27 17:14:25 +01:00 by Alessandro Padovani · 13 comments

The 35 mm default focal lenght of the 3d view doesn't match the 35 mm camera default focal lenght.

In the 3d view the perspective correction is about doubled respect to the camera.

For example, I usually use a 50 mm camera because it reflects the human eye perspective. To match the 50 mm camera perspective in the 3d view I have to set the lens parameter to 100 mm. That is twice the camera value.

It would be correct to fix the 3d view so that it matches the camera when setting focal lenght values.

The 35 mm default focal lenght of the 3d view doesn't match the 35 mm camera default focal lenght. In the 3d view the perspective correction is about doubled respect to the camera. For example, I usually use a 50 mm camera because it reflects the human eye perspective. To match the 50 mm camera perspective in the 3d view I have to set the lens parameter to 100 mm. That is twice the camera value. It would be correct to fix the 3d view so that it matches the camera when setting focal lenght values.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @padone

Added subscriber: @padone

Added subscriber: @mont29

Added subscriber: @mont29

Quickly checked, could not reproduce that at all, to me a camera view at 50mm and a perspective view at 50mm are matching perfectly. Please add data demonstrating your point (screen captures, .blend file…).

Quickly checked, could not reproduce that at all, to me a camera view at 50mm and a perspective view at 50mm are matching perfectly. Please add data demonstrating your point (screen captures, .blend file…).

I'm very sorry it's my fault I wasn't aligning the camera properly to do comparisons. If I align with ctrl+alt+0 it works fine.

Indeed it is a long time now that I use 100-50 to match and I never felt that it was wrong. Again sorry that I wasted your time I'll use more caution next time before posting.

I'm very sorry it's my fault I wasn't aligning the camera properly to do comparisons. If I align with ctrl+alt+0 it works fine. Indeed it is a long time now that I use 100-50 to match and I never felt that it was wrong. Again sorry that I wasted your time I'll use more caution next time before posting.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2014-12-27 19:55:19 +01:00

Ok, thanks, we can close this one now. :)

Ok, thanks, we can close this one now. :)

sorry, it seems I was too fast in blaming myself ..

I just managed to work out the case when 50mm camera and 100mm view matches. I included two pictures and the blend file to show this.

Just open the blend file (loading the user interface in the options) and use num pad 0 to switch between camera and 3d view. You'll see that 3d view and camera view match perfectly, even if the 3d view is 100mm and the camera is 50mm.

The reason behind this is that if we use ctrl+alt+0 to match the camera to the view it works just fine, but the camera frame is dimensioned about 1/4 of the 3d view. If we zoom the 3d view to have a full frame of the camera, the perspective doesn't match anymore, and we have to switch the 3d view to 100mm to have a perspective match.

This is why I use 50-100 so I can match the camera with a full framed 3d view. This is useful when using ctrl+alt+0 because I can use the full screen as if it was the camera. While if I use 50-50, ctrl+alt+0 frames about 1/4 of the screen instead of framing the whole screen.

So if we use 50-50 then camera and view match but the camera is framed 1/4 of the view, and if we zoom the view then the perspective doesn't match anymore.

If we use 50-100 then the camera matches the full framed 3d view. No need to zoom "back".

So, if we want ctrl+alt+0 to frame the full 3d view, then the correct setting is 50-100. This is why I say that 50-50 doesn't match.

If we use 50-50 then ctrl+alt+0 frames 1/4 of the view only instead of framing the whole view.

Sorry that I'm jumping in/out with this topic, it was a little tricky to find out ..

3dview.jpg

camera.jpg

50-100_match.blend

sorry, it seems I was too fast in blaming myself .. I just managed to work out the case when 50mm camera and 100mm view matches. I included two pictures and the blend file to show this. Just open the blend file (loading the user interface in the options) and use num pad 0 to switch between camera and 3d view. You'll see that 3d view and camera view match perfectly, even if the 3d view is 100mm and the camera is 50mm. The reason behind this is that if we use ctrl+alt+0 to match the camera to the view it works just fine, but the camera frame is dimensioned about 1/4 of the 3d view. If we zoom the 3d view to have a full frame of the camera, the perspective doesn't match anymore, and we have to switch the 3d view to 100mm to have a perspective match. This is why I use 50-100 so I can match the camera with a full framed 3d view. This is useful when using ctrl+alt+0 because I can use the full screen as if it was the camera. While if I use 50-50, ctrl+alt+0 frames about 1/4 of the screen instead of framing the whole screen. So if we use 50-50 then camera and view match but the camera is framed 1/4 of the view, and if we zoom the view then the perspective doesn't match anymore. If we use 50-100 then the camera matches the full framed 3d view. No need to zoom "back". So, if we want ctrl+alt+0 to frame the full 3d view, then the correct setting is 50-100. This is why I say that 50-50 doesn't match. If we use 50-50 then ctrl+alt+0 frames 1/4 of the view only instead of framing the whole view. Sorry that I'm jumping in/out with this topic, it was a little tricky to find out .. ![3dview.jpg](https://archive.blender.org/developer/F133895/3dview.jpg) ![camera.jpg](https://archive.blender.org/developer/F133897/camera.jpg) [50-100_match.blend](https://archive.blender.org/developer/F133899/50-100_match.blend)

I do not understand the issue, this is a matter of zooming, you can zoom out in camera view until it matches exactly your non-camera view… I really see no bug here.

I do not understand the issue, this is a matter of zooming, you can zoom out in camera view until it matches exactly your non-camera view… I really see no bug here.

Thank you very much indeed for your reply Bastien, I'll try to explain better and I hope to be clear this time.

Zooming and focal lenght are related each other and in fact they are the same thing. Indeed when you zoom you change the focal lenght. This is basic photography and optical knowledge.

Now if you set the 3d view to 50mm and the camera to 50mm, then use ctrl+alt+0 to match the camera with the 3dview, you will see that the camera doesn't frame the full 3d view, but it frames only the center part of it, about 1/4 of the total area. This is indeed because the the 3d view focal lenght (zoom) doesn't match the camera focal lenght (zoom). So you need to zoom in to match the whole 3d view with the camera frame.

Now if you set the 3d view to 100mm and the camera to 50mm, then use ctrl+alt+0 to match the camera with the 3dview, you will see a perfect match. The whole 3d view is framed, no need to zoom in. This means that to match the 50mm camera you need a 100mm 3d view. This also means that the 3d view focal lenght and camera focal lenght don't match, as I used as the post title.

This may not seem a big issue to anyone that is not a director or photographer. But having a 3d view that matches the camera greatly helps to better position the camera (when using ctrl+alt+0 for example) and to better have a sense of proportions and perspective right inside the 3d view, without having to use a separate camera view for this.

Thank you very much indeed for your reply Bastien, I'll try to explain better and I hope to be clear this time. Zooming and focal lenght are related each other and in fact they are the same thing. Indeed when you zoom you change the focal lenght. This is basic photography and optical knowledge. Now if you set the 3d view to 50mm and the camera to 50mm, then use ctrl+alt+0 to match the camera with the 3dview, you will see that the camera doesn't frame the full 3d view, but it frames only the center part of it, about 1/4 of the total area. This is indeed because the the 3d view focal lenght (zoom) doesn't match the camera focal lenght (zoom). So you need to zoom in to match the whole 3d view with the camera frame. Now if you set the 3d view to 100mm and the camera to 50mm, then use ctrl+alt+0 to match the camera with the 3dview, you will see a perfect match. The whole 3d view is framed, no need to zoom in. This means that to match the 50mm camera you need a 100mm 3d view. This also means that the 3d view focal lenght and camera focal lenght don't match, as I used as the post title. This may not seem a big issue to anyone that is not a director or photographer. But having a 3d view that matches the camera greatly helps to better position the camera (when using ctrl+alt+0 for example) and to better have a sense of proportions and perspective right inside the 3d view, without having to use a separate camera view for this.

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Adding Campbell as CC here to get second advice, but I do not see any bug here, 'zooming' in 3dview (scrolling) does not change focal length, and it does not affect the same factors even depending on view types.

In camera view, scrolling affect a property dedicated to this view only, view_camera_zoom, which by default (startup scene) is set to 20.0. If you set it to zero (two scroll steps backward), you get perfect match between camera and non-camera perspective views.

(In non-camera perspective views, scrolling just changes the position of the 'virtual' camera along the view axis, view_location parameter).

Adding Campbell as CC here to get second advice, but I do not see any bug here, 'zooming' in 3dview (scrolling) does **not** change focal length, and it does not affect the same factors even depending on view types. In camera view, scrolling affect a property dedicated to this view only, `view_camera_zoom`, which by default (startup scene) is set to `20.0`. If you set it to zero (two scroll steps backward), you get perfect match between camera and non-camera perspective views. (In non-camera perspective views, scrolling just changes the position of the 'virtual' camera along the view axis, `view_location` parameter).

Well, as a matter of fact the point of view (position) and focal length (zoom) are the two factors related to framing (view area).

If it is as you say and everything works fine, then it is not clear why ctrl+alt+0 frames 1/4 of the view. It should be "align camera to the view". That is, what is seen (framed) by the view should be seen (framed) by the camera. And this doesn't happen.

To make this happen you have to set the view to twice the focal length of the camera. If this is not a bug it is certainly something being somewhat weird and unexpected. I hope we can agree on this.

Again thank you very much for you kind reply and your patience. Of course my purpose is to help when I see something odd. But at times I feel to be a PITA and I always fear to waste the very precious (indeed) developers time with something silly. Hope this is not the case.

bye :)

Well, as a matter of fact the point of view (position) and focal length (zoom) are the two factors related to framing (view area). If it is as you say and everything works fine, then it is not clear why ctrl+alt+0 frames 1/4 of the view. It should be "align camera to the view". That is, what is seen (framed) by the view should be seen (framed) by the camera. And this doesn't happen. To make this happen you have to set the view to twice the focal length of the camera. If this is not a bug it is certainly something being somewhat weird and unexpected. I hope we can agree on this. Again thank you very much for you kind reply and your patience. Of course my purpose is to help when I see something odd. But at times I feel to be a PITA and I always fear to waste the very precious (indeed) developers time with something silly. Hope this is not the case. bye :)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#43039
No description provided.