hi looooong time user, first time poster.

finally got fed up enough to actually find the answer.

why does ‘f’ focus on selected sometimes do what you want it to do and frame the selected object and at other times just zooms waaaaay the heck out making you crawl back to what you hoped to focus on in the first place?  what can i do to avoid this behavior?

i can find no rhyme or reason and if someone can illuminate this for me, i would be very very grateful.

also, same odd kind of behavior in outliner.  sometimes when i hit ‘f’, it brings me right to the object in the list that i selected.  beautiful.  at other times, nada, nothing, zip.

small thing but really adds up over the years.

thanks.

jin

When you select an object, you are selecting the transform that is on top of the object.
The Node for a group is also a transform.

So in theory you can select a transform or group that can contain multiple shape nodes under neath it.
Under the hood, the frame selected command is calculating the total bounding box of all the objects under the group/transform node and frames them.

Why does it frame an area larger than the object in view port?

There are a few reasons, if you have a few objects that are under the same group/transform node.
The will blow out especially if all the objects are all around the 3d space of the scene, ie not all [0,0,0].

Another reason, could be the way the object is modeled,.
if you have any floating points or faces left from combining and extracting, then you could have floaties in the world space.
Quickest way to check this, is select the object and center pivot it, if the pivot is not in the center of the object, then you need to go to component mode and search for floaties.

Hope this helps.

hi kym,

cool.  that was it.  i only ever thought about stray verts (for which this curve object is clean of) but never thought that if the node is a parent of a group, that it would seek to encompass the group… especially since all the items are hidden from view (out of sight out of mind alas).

this is an animation rig and for some reason, under the curve controller for a body part, someone parented a lot of the under the hood stuff… some of which is way the heck out in space for some reason.  would imagine it’s not best practices cuz the curve control should exist just as an expedient for an animator to grab and the rest could have been grouped under a separate node....

cool.  thanks much.  now i’ll know what to look for.

any insight into why sometimes the outliner will jump to an item in the list when you hit ‘f’ and other times not?

jin