0
$\begingroup$

As per the instruction, if we want the camera to capture the viewport we have to press ctrl+alt+numbpad[0]. This works for native blender geometry. But when i import the object in .obj format to blender, everything seems ok but the camera doesnt capture viewport using the shortcut.

Is this a known issue?

$\endgroup$
  • $\begingroup$ Can you clarify what you mean by "capture" the viewport? Ctrl-Alt-Numpad-0 moves and rotates the active camera to wherever the viewport currently is. $\endgroup$ – acro Sep 3 '19 at 1:26
  • $\begingroup$ Yes thats what i meant by capture i.e. move and rotate to point to what viewport is seeing, but when you import an object, which is large, it doesnt move/ rotate the active camera . $\endgroup$ – GENIVI-LEARNER Sep 3 '19 at 7:55
  • $\begingroup$ Is the camera the Camera in the Scene Properties? blender.stackexchange.com/questions/149987/… $\endgroup$ – FFeller Sep 3 '19 at 16:04
  • $\begingroup$ @FFeller the problem was the default clipping of the camera because the scene was quite large and due to clipping of the camera it just shows grey. $\endgroup$ – GENIVI-LEARNER Sep 4 '19 at 13:08
0
$\begingroup$

From trying to replicate the described problem, I found this potential pitfall (which has been confusing new users for years). The camera actually does move to the new viewpoint, but only shows grey. If that is the problem you're having... it's because each Camera has its own Clipping Distance limits.

Screenshot showing right panel and where to find camera clip start/end

Once you've moved it far enough out, make sure the Camera's Clip End is increased enough so it encloses the distance back to the origin.

$\endgroup$
  • $\begingroup$ This solved the problem. Yes the camera moves but all i see is grey due to clipping. Not sure why this hasnt been fixed yet. I also had to change clipping for the viewport when I imported the model so it seems like have to redo it for the camera as well. $\endgroup$ – GENIVI-LEARNER Sep 4 '19 at 13:06
  • $\begingroup$ It didn't even occur to me to suggest it at first (as it's "just one of those things" you get used to), but it's very interesting to hear a fresh perspective on it. Just out of curiosity, when you say 'hasnt been fixed yet', do you have any suggestion how it could be fixed? $\endgroup$ – acro Sep 4 '19 at 14:47
  • $\begingroup$ It could be fixed by automatically detecting the size of the geometry and dynamically assigning the clipping values automatically so just like other 3d packages one can see the large or very small model by default and dont have to perform clipping adjustment. In summary I had to adjust clipping parameters when i imported the model and "again" for the camera and subsequently "again" for shading panel and other panels which is quite annoying when you are coming from Rhino or Maya because of Blender hype $\endgroup$ – GENIVI-LEARNER Sep 5 '19 at 11:24
  • $\begingroup$ @GENIVI-LEARNER Thank you for replying to that, it was just personal curiosity, but you're right, totally makes sense, just to get rid of one of those continual small extra manual actions/annoyances that the program could detect pretty easily. $\endgroup$ – acro Sep 6 '19 at 5:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.