Jump to content
AutoDesSys Forums

Paulji

Members
  • Content count

    53
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by Paulji

  1. Attached is an example of a set of Keyboard Shortcuts for Architectural Modeling. KEYBOARD SHORTCUTS_2.pdf
  2. First I'd like to thank Tech Support for help on this tutorial. Hopefully, this tutorial about creating windows from existing window components will help those creating new window libraries. Create New Window Component.pdf
  3. The Path Stair command raises some issues concerning how the stair runs attach to landings. In particular, the "Beam Stair" type creates a landing whenever the V-Line path changes direction. Strangely, if one wants to create a curved landing the curved portion where the V-Line changes to an arc become the stairs instead of a landing. . 1. So the first question is how does one create a curved landing? Suggestion: Add a means to create any shape landing. 2. The second question, how does one control the thickness of the riser run? 3. How does one control the thickness of the landing? Generally speaking most landings (I've worked with) are co-planar on the top surface and on the under surface. The structure and finish on the bottom of the landing are parallel to the floor not sloped as the Path Stair/ Beam Stair type command creates. 4. How does one adjust the sloping underside of a landing? Suggestion: Add controls to adjust the "flatness" of the underside of the landing. If one has two or more landings, each landing follows the same landing offset. This isn't necessarily useful. There are many cases where one landing length may be different from another landing. 5. How to make each landing offset unique at each landing? I've tried the S-split tool. This not only splits the landing but the stair changes from a solid to a surface object. I find it difficult to changes the resulting surface objects back into solids. Suggestion: Add controls to the stair so that the landings can be "stretched" or lengthened without destruction of the stair. Sometimes landings tuck under the stair riser runs. This is typical with wood construction where the stair stringers are supported on top of a landing beam or header. 6. Suggestion: Provide a mechanism to recess a landing beneath a stair run. Note: A workaround for all of this is to create a stair on a layer, ghost that layer, set snap options to "Snap to Ghosted" and draw over the "close-but-no-cigar" stair piece-by-piece on a new layer. Make adjustments as necessary. This allows one to create curved landings, custom railings, correct thickness of stair run structure and landings, tuck under landings, and "non-sloped" landings. This takes some work. It isn't quite the time saver one expects from a Stair command. Suggestion: Provide an edit mode to edit the stair using the drawing tools. Well, that's all for now.
  4. Hi Tech, That helps alot. Darwin06, I did want to respond to your comment that trying to incorporate every building code into a stair tool would be nearly impossible. I have to agree with you. For the past couple of days, I've been researching building codes in different countries to determine how tapered or angled treads were regulated. It's practically impossible to find this information online. The building codes of countries I found (ie. UK, Australia, and New Zealand) regulated curved public stairs by specifying walklines at some distance from both the narrow and wide ends of stairs. This suggests a simple solution that could very simply applied to a stair tool. The tool would allow placement of walklines offset at a user's choice of one or both sides of a curved stair. In addition, it would allow the user to specify the dimension of the narrow end of the tread. This I believe would satisfy any code. The safety issue with curved treads is giving one's foot enough purchase or support at the narrow end making sure the wide end of the tread is not excessively different.
  5. Hi darwin06, Could you explain your method of converting the parametric stair created with the stair tool to a plain object? Being a newbie myself it would be informative. Thanks.
  6. Hi Tech, Thankyou for looking into combining arcs and vector lines. You are correct about the Stair tool not written with specific state construction codes. All 50 states in the US use the International Building Code (IBC). Each state has adopted an IBC code version from 2003 to 2017. In 2009 IBC Section 1009.3 introduced the concept of the "walkline" as applied to winder treads. To my knowledge all states use the 11-inch deep tread at a "walkline" 12-inches from the narrow end of a winder....except Hawaii. Winders in residential dwelling units have exceptions to this. Another suggestion you might consider is allowing one to check the Tread width and # of steps in the Step Calculation group at the same time rather than a radio toggle buttons. It would also be great if one had the ability to change the tread dimension using Show Controls and/or by entering a value in the Tread edit box. The most successful stair tool option I like using is the Steps Only type. Thanks again for considering these ideas.
  7. Hi Tech, I'm aware of the ability to edit stairs after construction using the context menu/ Parameters. Curved and other shaped landings can be added to parametric straight flights as you mention. One issue I've been trying to figure out is how to get radius portions of a flight to combine with straight portions without any luck. See attached experiment. One of the issues on radius stairs with winders is how to accomplish code requirements for tread depths along walklines. I've referenced the 2013 California Building codes requirements for winders below: 1009.6 Walkline. The walkline across winder treads shall be concentric to the direction of travel through the tum and located 12 inches (305 mm) from the side where the winders are narrower. The 12-inch (305 mm) dimension shall be measured from the widest point of the clear stair width at the walking surface of the winder. If winders are adjacent within the flight, the point of the widest clear stair width of the adjacent winders shall be used. 1009.4 Width. … Winder treads shall have a minimum tread depth of 11 inches (279 mm) between the vertical planes of the foremost projection of adjacent treads at the intersections with the walkline and a minimum tread depth of 10 inches (254 mm) within the clear width of the stair. 1009.7.2 Riser height and tread depth, (Exception 5 applies to stairs within dwelling units) … the minimum winder tread depth at the walkline shall be 10 inches (254 mm); and the minimum winder tread depth shall be 6 inches (152 mm). Suggestion: See if there may be a way to allow control of the winder tread depths along a stair's walkline. Another suggestion: Ability to explode the stair using the explode tool as one can do with a component. The stair could remain a solid and be manipulated easier. Thanks for getting back to me on this.
  8. There are a number of standard stair configurations that should be addressed in the stair commands. The first stair is a branched stair with a common landing. This was created by joining an L-shaped stair with a straight run. It's not quite right. Problem would be connections to the stair. The second stair is a straight run - curved run - straight run stair. Unable to create this stair configuration. The third stair is a simple straight run stair with a landing within the run. This is common when you have floor to floor over 12-feet in height. Unable to create this configuration using the stair tools available. Suggestion: Add ability to create these types of stair configurations to the stair tools. Other issues that should be addressed: It is very common in commercial construction ... particularly metal pan stairs and concrete stairs that risers slope slightly back under the tread and are not always vertical. Suggestion: Add this capability to the stair tools. Nosings are not always square as created using the stair tools. They may have other profiles ... rounded nosings are common. Suggestion: Add this capability to the stair tools. When I apply a clipping plane to a stair (with or without a railing) the tool options palette is blank. I was hoping to add a crosshatch pattern. Would like to be able to add a different cross hatch pattern to railing and stair. I appears I'm unable to add any hatch pattern. Suggestion: Add ability to add different hatch patterns to stair components. ps. If anyone who has created the stair landing configurations using the stair tools mentioned above please let me know?
  9. When I check Hatch ON for Cross Sections in the PICK Tool Options dialog, there is only one Selected Hatch (ie. Angled Linear) available in the image box. My first thought was to click the Hatch Palette and select a new hatch pattern. I was hoping this would become the Selected Hatch for the cross section ... but that is not the case. The FormZ Pro Manual is silent on how this is accomplished. Either I'm witnessing a bug or there is a hidden means to accomplish this task. How does one select hatch patterns from the Hatch Palette and make them the Cross Section hatch?
  10. REFERENCE PLANE CONTROL WIDGET: By trial and error I discovered: 1. You could accurately rotate the rings of the Reference Plane control widget by their axial bullets on the rings by sequentially tapping the TAB key. Each time you hit the TAB key a different ring with a gray color circular dial is activated. By snapping an axial bullet and tabbing to the desired ring, you can rotate the bullet and accurately snap to a segment or object snap of an object. Sometimes you don’t know what angle to rotate a reference plane. You don’t need to know the angle if you snap with bullet points. 2. Sometimes the Edit Reference Plane is active and the Reference Plane control widget disappears. A solution is to click the Create Reference Plane icon. (Strangely, this does NOT create a new reference plane in the Custom Reference Planes palette.) Then, click on the Edit Reference Plane icon. This brings back the Reference Plane control widget. 3. There is a time delay for the angle readout when rotating a circular dial. (d 45 degrees etc.) Suggestions: 1) I’d like the Angle of rotation to show on the Input Palette. That way I could input an angle directly. 2) I’d like to be able to control the time delay of the angle readout adjacent the circular dial.
  11. OK. I see ... one doesn't simply click or double click a new pattern in the Hatch Palette but must drag it and place it over the Selected Hatch image. Again I feel the FormZ Pro Manual could be a little more explicit.
  12. I see that editing the Scenes palette (link: http://forums.formz.com/index.php?/topic/4900-scenes/?hl=%2Bscene+%2Bpalette&do=findComment&comment=17779) is as simple as: 1. Activating the Scene with the "Make Active" button 2. Making changes in the Modeling Window (Alternately: Right-click the name_ to open the context menu_select edit_make changes in the Scene Options dialog) 3. Click the "Make Active" button to make the Scene inactive. The "Make Active" button in the Scenes Palette makes a scene active for editing in the modeling window. This is not the case for the Views Palette. By clicking the "Make Active" button in the View Palette and clicking in the Modeling Window the View becomes inactive. The editing procedure is different from that of the Scenes Palette. Revised Suggestion: Fix the "Make Active" button of the View Menu so that it remains active when one edits in the Modeling Window in the same way that the "Make Active" button does in the Scenes Palette. Also, Please revise the FormZ Pro Manual to include the use of the Views Palette and Scenes Palette.
  13. The View Parameters dialog allows one to type a new value for the Perspective Parameters. It would be useful to be able to dynamically edit a view using the Set View icon. I would like to suggest that the Set View icon be added to the View Parameter's dialog box. This would be more intuitive than adjusting the camera position (by turning on the visibility and adjusting target and eye position) or entering new values in the edit boxes. Another suggestion is that a description of the View Palette and Scene Palette be added to the FormZ Pro Manual. These are missing.
  14. I have not been very clear about what I was suggesting. I'll try to explain. It is very easy to create a View or Scene using the View Palette or Scene Palettes. I like to use the Navigation tools (ie Set View, Hand, Zoom using my middle mouse button). Once one gets the View in the modeling window the way one likes clicking the green (+) button in the Views palette creates that view. Easy peezy. To UPDATE that newly created View one either double clicks a view name or right-clicks the view name. This brings up the View Parameters dialog. I find this dialog box not very intuitive to use. I would rather: 1. Activate a chosen View. (Click red button in the Views Palette) 2. Change my View or Scene in the Modeling Window using the Navigation tools (Set View, Hand, Zoom etc). 3. Double-Click or Right-Click the Active View and Select an UPDATE VIEWS/ SCENES button. See attached: An alternative to step 3 would be to have a new Update button on the View Palette or Scenes Palette. This would be similar to how SketchUP allows one to update a Scene. (The two arced arrows are SU's symbol for updating a Scene). As a newbie I find the Edit Cone of Vision concept cumbersome to use and tend to avoid it when the Navigation tools are so much more intuitive. Hope I've made this clearer. Sorry for the confusion.
  15. After some additional experimentation, I've come up with what seems to be a quicker way to create a library of window components. There are fewer steps involved. This method involves using FILE > SAVE AS rather than using the Create Window/Door tool. The consequence is that the thumbnail display of a new window component in the Component Manager is not as sharp as it is when one uses the Create Window/Door tool. If one uses the list display of a window in a library however this isn't an issue. See attached. 01_Create Window by Saving an existing window component with Save A.pdf
  16. Note: If (in the last step ... you don't want to re-open projects to display the new window component in its library ... you can re-open the library using the Add component library icon in the Component Management group of the Component Manager. This does the same thing as re-opening projects to refresh the associated Library. I don't know why the Refresh Libraries icon does not refresh the Library display. A bug?
  17. Tool Options for Terrain Model has the option for setting intervals of existing "flat" contours. This is done by increasing the topo interval based upon the sequence of contour picks using the SHIFT key. Using the "Set New: Interval" only increases in the "positive" direction from the Site (Starting) Height. This makes multiple instances of hills and valleys in a large site plan slightly difficult. One must use the MOVE tool to tediously rise each contour to the correct height. My suggestion is that the Terrain Model Tool Options include the ability to repeat an interval and change to a negative interval. See attached.
  18. BTW. Ust for fun...attached is a terrain model using Set New: Interval where the interval is a negative value.
  19. Hi setZ, That's interesting. Good insights. I tried using the Group tool to group two contours on the same contour level. Using the PICK tool one cannot simply enter a Z-value in the OptionTransformation/ Z origin. That options do not appear. So one must use the MOVE tool to move perpendicular to the reference plan. No big deal. Then using the USE Existing option of the Contour Heights option you can select all the contours that are raised to their proper elevation ... including the grouped contours. One doesn't have to explode the group in order for the TERRAIN MODEL tool to work). Grouping of contours of the same height, however, has no effect on creating a terrain model using the Contour Heights/ Set New: Interval. Honestly, I don't see any value of using the Set New: Interval option of the Terrain Model Tool ... unless you are building a terrain model where the contours increase in a positive direction sequentially from one contour to the next.
  20. Hi setZ, I'm trying to understand how you use the join (objects) tool on contour segments. It appears one cannot use the Organize/Join tool on segments but only solid or surface objects. I get the following error message when I try to create a terrain model using the Set New: Interval option: "Object must be a solid or a surface, Use Create Reference Object for all other types of objects." I get the following error message when I try to create a terrain model using the Set New: Interval option: "Reference Objects are not handled by this tool." If however, I use the Reference Objects to "join" contour segments of the same height into a single object I can raise these segments together using the PICK tool. Thanks for that tip. It will be useful. I still believe that my latest suggestion would significantly decrease the time required on complex topo sites with huge numbers of contour lines. Maybe not so much on smaller topos.
  21. Hi All, I'd like to suggest a better solution. Forget about trying to improve the Set New: Interval option. Better Suggestion: Why not improve and automate a technique that already works well. The technique is to elevate each contour line one-at-a-time to its correct contour level by picking each contour line and entering a height in the Pick/Info tab/Object transformations/ Z-origin edit box. After all contours have been elevated, use the Terrain tool /Existing option. The advantages of this technique are: You can see in 3D the contours move to their positions in space. (This is not possible when using the Terrain Model/ Set New: Interval option.) You can check the height of any contour by picking on it and seeing its height in the Object transformation group. (This is not possible when using the Terrain Model/ Set New: Interval option.) You can elevate contour lines in any order ... this makes it easy to switch from a high contour on a hill crest to a lower contour on the foot of a hill and continue downward on a slope. (This is not possible when using the Terrain Model/ Set New: Interval option.) Lastly, you can enter contour height sequences in either a positive direction or a negative direction. (This is not possible when using the Terrain Model/ Set New: Interval option.) The only disadvantage of this technique is that each contour must be picked one-at-a-time and Z-height values must be entered one-at-a-time. This makes it a tedious process when creating large terrains. A better solution is to add a Contour transformation group to the Terrain Model -Tool Options. HOW THIS WORKS: Click on the Contour transformation option radio button. Enter a contour height in the Starting Height edit box. This will be the Starting Height for multiple picked contours. Enter a value in the Contour Interval edit box . This can be a positive (increasing contour interval) or negative value (decreasing contour interval). Pick contour lines in sequence holding the SHIFT key. NOTE: On-the-fly you can then enter a new Starting Height and switch the Contour interval from a positive to a negative value or vise versa, then continue picking contour lines holding the SHIFT key. Contour transformation Option.pdf
  22. Wrapping or connecting open segments of equal elevation outside the property boundary (prior to selecting them) is helpful to some extent when using the Set Interval option. The fact that the elevation of contours only inrease sequentially in a positive direction makes the Set Interval option less useful then it could be. Sure there are ways to set each contour line at their correct elevation prior to creating a terrain model but I believe the Set Interval option could be tweeked to take some of the drudgery out. I sometimes deal with properties that are comparatively large ... 60 to 90 acres. These often have multiple hills, valleys, ridges etc. The way I envision my suggestion working is to turn the Positive Interval radio button ON to sequentially increase contour elevations by clicking each contour line going up to the crest of a hill ... then switching ON the Negative Interval radio button and "back-tracking" downwards re-selecting contour lines downward to the low point of valleys. Switching between Positive and Negative Interval directions would work for both open contour lines (those that extend outside the property boundary) and closed contours within the property boundary. The Repeat Interval would be useful for elevating open contour lines of the same elevation height. An alternative to "back-tracking" or re-selecting contours previously selected would be to select any previously selected contour to get it's elevation height in a similar way that the F4 key resets a base point only instead of resetting a 0 value it would get the elevation value of the selected contour line. You would the with a Positive or Negative Interval set ON continue to select new contours. It would also be nice if you could hover the cursor over a contour line and its elevation would display. Hope this makes sense.
  23. It doesn't appear that one can create a window or door on-the-fly on a custom reference plane but only on the World Cartesian Reference plane. I'd like to suggest that one be able to create a window or door component in-place. BTW: I'm a newbie so if I'm incorrect please let me know.
  24. Temporary reference planes have a distinctive snappable origin that one can snap to. Suggest that the World Cartesian reference plane has a snappable Origin as well. It's true that if you set the Grid Snap ON you can snap to that point but if Grid Snap is OFF it would be nice.
×