Search the Community
Showing results for tags 'door geometry'.
Hi all, I am trying to create a very simple 2-D Door Jamb (see PDF attached for visual cue) which I want to use for a Door Marionette that I created. And I have tried for hours with different nodes to get the result I need but it is not working. So I ask, if my starting approach is the correct / efficient method or is there a better one that I may have not considered? 2-D Door Jamb - Values and Parametrics The 'bold black' shape is created by individual lines with fixed points which I want to be temporary as highlighted in red. Those are values I want the user to input. I.E. if the wall thickness (a) is 200mm, then Door Thickness line will change to accomodate the change in wall thickness(b). Also, I want there to be a fixed length of 45mm highlighted in blue, which will then give the door thickness (b) distance. Makes sense? To make it more complicated, I want the option to add a constraint of the wall thickness (a) value, so it does not go lower than 60mm. I hope I am making sense with the diagram below. I have tried various methods to 'Get Distance', 'Find Points in Polygon' but I just dont seem to understand how to draw the polygon shape and also add the constraints. 20200205163000.pdf
Hi all, I encountered the following phenomenon: I've created a custom door record and I'm using viewport data visualization to check if I've remembered to put the right record info into the right doors. I've found that this is a practical way to check if the correct doors have been assigned, let's say, an electronic access control lock. However, using custom door geometry seems to break the visualization - please see the attached snip. The red doors should be blue. Doors that have custom geometry always show up red, independent of the data. There is no red assigned anywhere: in classes, objects, visualization, object attributes. In normal plan views and other views, these custom geometry doors look fine, no red. Has anyone else had this issue? Before someone asks, the reason for using custom door geometry is that one cannot make an unequal swing door so that the side leaf would have a glass pane just like the main leaf (VW please fix this, important and a very basic requirement !). Another thing I noticed is that the data visualization system doesn't allow umlauts (Ä's, Ö's etc.) in record names - it ignores them, in VW 2017. I haven't tried the 2018 yet. Removing the umlauts solves the issue (but then the worksheed data headers have to be corrected correspondingly). This was surprising since these records with umlauts work just fine with the worksheets.