Joe_Carrick

Members
  • Posts

    12061
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. Knowing there might be other numerical characters in the original string I took the approach of specifically eliminating values at the beginning and end.
  2. Yes, there is a way to do this. For the beginning of the string it requires that you get the integer value of the string. You can then convert that to a string value (str) and use string.sub(str,"") For the end of the string it's a little more complicated in that you need to determine which how many characters are numerical and just shorten the string.
  3. Jorge, Do you use Rescheck in Fresno? Down here in SoCal we have to use CalCERTS.
  4. The "Reference Elevation" for Level 1 will in fact always be 0. But if you need to show it differently in plan or section/elevation - that can be done with a custom macro.
  5. If you have a Terrain Perimeter, you can set the Level 1 Elevation Offset in the Terrain dbx.
  6. When you add a Floor below "Level 1" Chief simply re-numbers the "Levels". It can't have a Level below zero so whatever floor is above Level 0 will always be Level 1. That's not the same as 1st Floor. For Example you could have the following: Level 0 = Foundation Level 1 = Basement Level 2 = 1st Floor Level 3 = 2nd Floor Attic = Attic -or- Level 0 = Foundation Level 1 = Basement 1 Level 2 = Basement 2 Level 3 = 1st Floor Level 4 = 2nd Floor Attic = Attic
  7. Kyle, Chief doesn't actually label anything as: Foundation Lower Level Main Level Basement etc. Rather, it uses: Level 0 Level 1 Level 2 etc Attic It's up to you to name those as above. Level 1 will be by default "0.00" unless you change it. Within Defaults, you can specify the "Elevation" of the "Current Floor". It's generally best to start with the Attic and work down to get these values to agree with what you are wanting.
  8. The Diamond Box appears to be an Appliance Schedule Callout. Turn off the "Fixtures, Labels" Layer to prevent it from being seen.
  9. It worked great for me. I needed lasik surgery to eliminate cataracts so I just got the smart lenses with 2 corrections for close up vision. Both eyes are corrected for distance and the left eye is corrected for computer monitor (30-36") and the right eye is corrected for reading (12-15"). Initially I had a little problem with night time driving - tail-lights and signal lights had halos but over time my brain has learned to ignore that effect.
  10. Since Wall Types are Plan Specific, I would just export the "Glass Wall" from a plan where it's correct and Import to the one where it isn't.
  11. Yep, but Scott has hijacked a few in his time
  12. Yes, and not all my projects are residential so I need the software to be able to handle that situation. Interestingly, CA's headquarters are in a 2 story commercial building with exactly that stair configurations where the Guards and Handrail co-exist. The Guard is in the form of a Railing Wall and the Handrail is attached to the Guard. It would be a great example for the software engineers at CA to use. btw, Hotels also need this kind of Stairs with 42" high Guards & 34-38" high Handrails.
  13. I'm not disagreeing that "Guards" as currently specified in the IBC, CBC, CRC, etc are as you and Richard say. It's just that once upon a time when I was much younger we had the UBC and the terminology at that time was "Guardrail". It's the terminology that was used for the first 45-50 years of my working life so it's what my somewhat calcified brain uses.
  14. That's interesting. My Project Browser is docked and it still works.
  15. Richard, Really? You are using Hospital Wall Handrails/Crashrails for this discussion? I spent the first 12 years of my career doing predominately Medical Facilities. That included several very large hospitals as well as about a dozen convalescent hospitals. Those items serve 2 purposes: Handrails for patients to use when getting exercise. Protecting the walls from medical equipment impacts (gurneys, rolling stretchers, wheel chairs, etc) Let's be sensible here. I use the term Guardrail to describe what the building code refers to as "Guards". The can be a Railing Wall or a Solid Half Wall. The key is that they have to meet the requirements for Railing Walls at a Minimum. That includes the height and maximum opening requirements - which have changed drastically over the past 50 years. Currently (as Doug stated above) Stair Handrails and "Guards" are often required together. The Stair Handrail can never suffice by itself at the open side of a Stair.
  16. Reversing a plan often causes problems. That may be one of those cases.
  17. Interesting, it works for me. Are you using the default room label? I change the Room Name. In fact, I just started a new plan in X10, set the Room Type to Garage and the default label has a rotate handle that works.
  18. That's not true. Room Labels in (at least in X10) have a rotate handle that can be used. AFAIK, the only thing that can't be edited directly is the Text itself.
  19. Can you select the Room Labels? If not, that Layer may be locked. Without the Plan itself we are only guessing.
  20. Only in the Building Code. That's really pretty dumb because a "Guard" by definition is generally "a person who protects or controls". There are Bank Guards, Prison Guards, even Guard Dogs - but there is no such thing as a "Wall Guard". Obviously the person(s) that wrote the code were not linguists.
  21. The program determines if the wall is an exterior wall or an interior wall. Garages are strangely considered Exterior Rooms in Chief, so any Garage Wall is classified as Exterior. But any wall separating 2 Garages is considered as an Interior Wall. That's what determines if the door is exterior or interior. Basically, it's about weather exposure & fire rating - nothing else. IAE, you can specify whatever door type, style, thickness, description, etc.
  22. BTW, You can actually do that for any symbol in the plan. You don't have to do it in the Library. IOW, select the Symbol and then the little chair icon on the edit toolbar.