Results 1 to 10 of 10

Thread: Family hitboxes

  1.    #1
    Member CRapai's Avatar
    Join Date
    April 30, 2015
    Location
    Michigan
    Posts
    329
    Current Local Time
    01:11 PM

    Not allowed! Not allowed!

    Family hitboxes

    I have been doing some testing with detail component families that contain family types with varying content size. I've been keeping them simple and using visibility parameters to control everything. No linework or nested detail component are controlled by dimensions. Because of this I'm running to the annoying problem of my hitbox being way to large for most family types. Visibility setting do not control the select-ability of the element.

  2.    #2
    Member d.stairmand's Avatar
    Join Date
    February 24, 2011
    Location
    Auckland
    Posts
    400
    Current Local Time
    05:11 AM

    Not allowed! Not allowed!
    Cody

    More information needed - What is the question you are asking us?

    What is a Hitbox? Never heard of that term in Revit before?

  3.    #3
    Forum Addict GMcDowellJr's Avatar
    Join Date
    December 21, 2010
    Location
    Phoenix, AZ
    Posts
    2,822
    Current Local Time
    10:11 AM

    Not allowed! Not allowed!
    In this case hes talking about a cross selection (right to left) that selects the element when you dont want it to. Visibility doesnt mean non-selectable.

    OP Youll have to rethink your approach. Unless these are just lines and you set them to be Not a Reference youre going to get this just using visibility parameters.

  4.    #4
    Forum Addict jmk's Avatar
    Join Date
    December 31, 2012
    Location
    NM, USA
    Posts
    1,572
    Current Local Time
    11:11 AM

    Not allowed! Not allowed!
    The only way around the giant hitbox is to add a dimensional control to the lines with your visibility control. I've onlky used it once, to deal with showing a rough fire extinguisher coverage distance in the family. If the coverage distance was on, the clearance radius matched the setting in the family (75', typ). If it was hidden, the radius was 2" (or something that prevents the family from breaking, but doesn't extend past the visible bounds). If I was rebuilding I'd probably replace it with a nested family.

  5.    #5
    Administrator Twiceroadsfool's Avatar
    Join Date
    December 7, 2010
    Location
    Dallas, TX
    Posts
    11,106
    Current Local Time
    12:11 PM

    Not allowed! Not allowed!
    Quote Originally Posted by jmk View Post
    The only way around the giant hitbox is to add a dimensional control to the lines with your visibility control. I've onlky used it once, to deal with showing a rough fire extinguisher coverage distance in the family. If the coverage distance was on, the clearance radius matched the setting in the family (75', typ). If it was hidden, the radius was 2" (or something that prevents the family from breaking, but doesn't extend past the visible bounds). If I was rebuilding I'd probably replace it with a nested family.
    The nested family still affects the Hitboxes.

  6.    #6
    Forum Addict jmk's Avatar
    Join Date
    December 31, 2012
    Location
    NM, USA
    Posts
    1,572
    Current Local Time
    11:11 AM

    Not allowed! Not allowed!
    Quote Originally Posted by Twiceroadsfool View Post
    The nested family still affects the Hitboxes.
    I'd probably have it swapping with another one with the visibility, but that probably isn't any simpler than what I'm already doing...

  7.    #7
    Forum Addict GMcDowellJr's Avatar
    Join Date
    December 21, 2010
    Location
    Phoenix, AZ
    Posts
    2,822
    Current Local Time
    10:11 AM

    Not allowed! Not allowed!
    Quote Originally Posted by jmk View Post
    I'd probably have it swapping with another one with the visibility, but that probably isn't any simpler than what I'm already doing...
    I think you have to do more than nest the family and use visibility parameters. There would need to be two nested families (one empty) and a Family Type parameter to swap them. Or use Shared Nested and filter them out of the view.

  8.    #8
    Administrator Twiceroadsfool's Avatar
    Join Date
    December 7, 2010
    Location
    Dallas, TX
    Posts
    11,106
    Current Local Time
    12:11 PM

    1 Not allowed! Not allowed!
    Quote Originally Posted by jmk View Post
    I'd probably have it swapping with another one with the visibility, but that probably isn't any simpler than what I'm already doing...
    Whats funny about this, is we've already done the hard work to make that happen, in our doors... but then we didnt do it. (We have a second FT parameter with a formula, so when the vis is unchecked that FT shows "-" which is a blank family). We did it for scheduling purposes, not geometry. But, yeah:

    If i make those Reporters drive the actual Family selection, it DOES minimize the hit boxes.

    I might have to make that a reality in the Doors.

  9.    #9
    Senior Member
    Join Date
    August 19, 2011
    Location
    New Hampshire
    Posts
    519
    Current Local Time
    01:11 PM

    Not allowed! Not allowed!
    When using nested elements, you should control both visibility options. It isn't enough to unsee the linework, you need to disable the nested element.

    In the image, I nested a linework circle into a detail component. If you control the visibility of the circle using "Circle Linework" (assigning a parameter to the linework visibility in nested component) you will be able to select the detail component when dragging a selection box where the circle is. If you turn off the "Visibility" parameter of a nested element in the parent family, it will disable the nested element in the view.

    Second image is a gif of the scenario.
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	Capture.PNG 
Views:	21 
Size:	7.9 KB 
ID:	39064   Click image for larger version. 

Name:	ComponentHitBox.gif 
Views:	20 
Size:	420.9 KB 
ID:	39065  
    Last edited by Andrew K; June 29th, 2020 at 07:04 PM.

  10.    #10
    Moderator DaveP's Avatar
    Join Date
    January 10, 2011
    Location
    St Paul, MN
    Posts
    3,324
    Current Local Time
    12:11 PM

    Not allowed! Not allowed!
    Quote Originally Posted by Andrew K View Post
    , it will disable the nested element in the view.
    I'd be careful with that statement.
    Using this technique does NOT "disable the nested element in the view"
    It disables the element IN THE FAMILY.
    Turning off the visibility of the nested element will affect every View that family is seen in in the entire project

Similar Threads

  1. Nesting Generic Annotation Family into Face Based Light Fixture Family
    By dmudd in forum Architecture - Family Creation
    Replies: 3
    Last Post: November 5th, 2019, 10:44 PM
  2. 2d Family vs 3d Family; Multi-Family Residential
    By deepblue02101996 in forum Architecture and General Revit Questions
    Replies: 15
    Last Post: April 10th, 2019, 06:47 PM
  3. Replies: 0
    Last Post: March 27th, 2016, 07:18 AM
  4. Replies: 0
    Last Post: March 22nd, 2016, 07:15 PM
  5. Live Session - Family Creation Series #3 | Family Phasing and Geometry Modeling
    By rkitect in forum Architecture and General Revit Questions
    Replies: 14
    Last Post: April 25th, 2012, 07:03 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •