Joe_Carrick

Members
  • Posts

    11881
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. I've found that different jurisdictions require different areas to be included in the Floor Area for the FAR calculation. I'm trying to put together a set that would cover as many cases as possible. Please respond to the Poll indicating what areas your local(s) require. Thanks.
  2. Most likely, the X9 Beta has been replaced by the X9 final release. Check the version number. It should be : 19.1.0.47x64
  3. Here's my version of Object Properties. It works much better IMO. _Object Properties.json
  4. Marc, Replace all instances in your macros of owner.top_elevation with (owner.header_elevation-owner.rough_opening_top) The problem is that X9 fails to initialize the top_elevation and bottom_elevation attributes. I reported this to Brian at CA and he acknowledged the problem. It's in their court to fix it but in the meantime, using the above alternative solves the problem.
  5. I received a notice from Brian at CA that he could reproduce the error and logged the issue.
  6. Did you contact Chief Tech Support?
  7. Ed, Have you updated the Library Catalogs since the final X9 release?
  8. Try this link instead https://kcclemo.neocities.org/creating-height-and-normal-maps/
  9. Steve, I always dimension in the Plan. It's much easier IMO. Of course, my Annoset & Layer Set is setup so that I can do this and just send the Site Plan to Layout. I never got the idea of using a CAD Detail Window for the Site Plan.
  10. Yes, and I've reported it to CA. I also had a macro for Vent Labels that used bottom_elevation that didn't work in X9. I've modified it to use other attributes but IMO CA should not make changes that cause things that worked to quit working.
  11. I agree with Michael. Of course he has exaggerated the Top and Bottom Rough Opening values - but it does illustrate the point.
  12. ps: Another way to see this is to open the Ruby Console and type: owner.top_elevation <enter> the result is nil or owner.top_elevation.nil? <enter> the result is true
  13. John, The owner simply eliminates the need to specify owner context. header elevation accounts for the rough_opening_top so if you change the macro to: arr = (header_elevation-rough_opening_top).round().divmod(12) "#{arr[0]}" "'-" "#{arr[1].round()}\" H.H." you will get the same result you did before. The problem currently is that the top_elevation is nil. It's neither a numerical value or a string. top_elevation.round() is the same as nil.round() which generates the error. CA needs to properly initiate the top_elevation & bottom_elevation attributes.
  14. John, Try this: arr = owner.header_elevation.round().divmod(12) "#{arr[0]}" "'-" "#{arr[1].round()}\" H.H."
  15. No, but do you really want that? All the glass panel showers I've seen do not have glass above the door.
  16. Stephen, Show us the Wall Type Definition.
  17. Core Library>Architectural>Windows>Atrium Windows
  18. You probably don't have the Fixtures, Exterior layer displayed.
  19. Here's some samples of the Stairs Macro Package
  20. The only thing you can currently do is to select the schedule and manually drag each row up or down to get the order you want.
  21. I don't see any extra windows. Maybe you've "included all floors" when doing the schedule on the 1st floor?
  22. ??? - Post the Plan. Also, please edit your profile so we know who you are and what version of the software you are using.
  23. I'm holding off on the Videos until the final X9 release. Then I will do a couple that will show volumes with the total calculated for "Conditioned Space". I just want to make sure to take advantage of all the capabilities of X9.
  24. Hopefully, there will be more in the Room Finish Schedule next week when the full X9 version is released.