Joe_Carrick

Members
  • Posts

    12026
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. When you create the symbol you shouldn't classify it as a molding. Geometric Shape or some other Symbol class would be appropriate.
  2. Basically, the X12 "Split Landing Stair" is not something I've ever seen. The "Wide-U Stair" with an intermediate Flight would have been a much better addition since it would provide the ability to fit a stairway into different sized areas. That's what designers need to do.
  3. You can submit an "online support ticket" or email "support@chiefarchitect.com"
  4. Attached is the documentation for the Stairway Design Program that I programmed at CalComp in 1984. It has a few differences in how it worked and what data needed to be assigned simply because we didn't have a 3D Model to get data from and the model didn't know what units were to be used. However, it was in several ways more comprehensive than Chief's current Stairway tool. It included options based on Code requirements (actually user modifiable) It included Spiral Stairs It included true "Wide-U" Stairs with 2 Landings separated by an intermediated Flight vs an intermediate Landing - which is what Chief has provided in X12. It included Handrail Code requirements (which could be modified by the user) whereas Chief has not implemented any code requirements. One thing that Chief did provide in X12 that my program didn't have is the ability to have "Winders" on the Landings. Stair_Design_by_JPC_in_1984.pdf
  5. The key here is that any distance or area attribute that was a "Floating Point" number in X11 is a "Measurement" in X12. If you migrate a macro it will assume it's using the X12 "Measurement" data type and might not work the way it did in X11. "Measurements" recognize a "unit" such as inches, feet, sqft, etc. You can add, subtract, multiply or divide like measurement units - but you can't add or subtract a floating point or integer number to a measurement. If you want to migrate your macros you have to make sure you follow those rules (and there are some more rules) ---- or make sure you convert attributes using .to_f in order to avoid execution errors. My suggestion is to not migrate unless you are sure of what you are doing. I've taken the time to modify all my macros to work in X12 - it was not a trivial effort. When I create new macros I try to use the "Measurements" but it requires understanding and implementing several new methods that are unique to Chief's X12 Ruby. The Measurement Class is not a standard Ruby Class - it's an add-on created by CA.
  6. If I understand what Larry wants, here's how I would do it. Create a Section looking at the wall Set it to double callouts Clip to sides Mask the top and bottom so that you only see the wall.
  7. I discovered that there were quite a few CAD Blocks in the Layout that were indicated as used. However, they were not in fact used anyplace that I could find. Because they were indicated as used, I couldn't delete them and even when I placed them I couldn't find the offending layer. So I used the X12 "Save as Template" tool: Unchecked the "Non Template Pages" box Unchecked "Client Info" & "Revision Entries" The result was a "Clean Layout" for the current project with all proper data maintained. It got rid of the offending CAD Blocks and the offending Layer. I Still can't find the problem in the original Layout file but at least I now have a clean version. It would really be nice if the "Save as Template" tool allowed saving of just specific page content. Then it would be pretty easy to create a template with "Boiler Plate" for various jurisdictions and/or repeat clients.
  8. Too much stuff (Macros, etc.). If I don't find the culprit(s) I'll see if I can strip it down.
  9. Not in a Layout File - only in Plan Files is that available. IAE, I do not have any Notes even in the Plan Files that use those Layers.
  10. AFAIK, you can not assign a Layer to a Text Style. You can assign a layer to a Default for: Dimensions Rich Text Text Callouts Markers I'm pretty sure you can also assign a layer to a Note type - but I don't at this time recall exactly where that's done. I suspect that my problem is in the Note types because I can't find it anyplace else. I've also checked all CAD Detail Windows without success. But "Notes" are not possible in Layouts so that can't be the problem either.
  11. I've been working on cleaning up my Layout - getting rid of unused Layers, etc. Unfortunately, I've run into a couple of problems that I don't seem to be able to solve: I have a Text Layer "Text, Structural" that is indicated as "Used" but I can't find it in any page - even when all layers are displayed. I have another Text Layer that is indicated as specified in a "Default" but I've checked all my Default Sets and can't find it an any Default. Is there any way to search the Layout file to find where these things are located? Note: My procedure (tedious at best) was to turn on all layers (unlocked) and marquee select the everything on every page. Most things I was able to find and edit or delete as necessary. These two have eluded all my efforts.
  12. No, you will need to set the wall thickness yourself. Chief doesn't know anything about the required thickness for the pocket door to fit in the wall. Normally you would need to define a "Wall Type" with sufficient internal thickness to accommodate the door.
  13. I'm in San Marcos. PM me if you need help on a part time basis.
  14. Katherine, What render mode are you using for the views that don't show what you want? What views are you having trouble with? Perspectives or Elevations? This is why posting a picture and even better the plan will get you better answers.
  15. My Warehouse Detail Plans are all at a scale of 3/4"=1'-0" It's all automatic.
  16. I have a series of Detail Plans: Foundation Doors Windows Railings Floor Framing Roof Framing etc. Within each of those I have from 5-20 details stored in CAD Detail Windows which are named and show up in the Project Browser. I simply select the ones I need from those plans and send them to my Layout. This scheme provides a pretty simple "Look-Up" and keeps my project plan and layout pretty clean. In some cases the Details are imported Images (pdf, jpg, bitmap, png, etc) but mostly they are details I've created in Chief.
  17. I went thru this exercise several years ago with a complete set of "Andersen Bay Window" symbols. Unfortunately Chief doesn't handle "Custom Windows" very well. I was only able to set them up as "Exterior Fixtures" and place them in a "Pass Thru Window" in order to get the Window Frame, Casings, Sill, etc correct. At that time the "Exterior Fixtures" wouldn't show in a Window Schedule. X12 may make it possible to put them in the Window Schedule.
  18. Check the displayed layers. They might be on a layer you don't have displayed.
  19. It's a good idea to immediately save elevation & section views. That way they will automatically be saved in the future.
  20. Sorry, their gone unless you have an autosave in the archives folder that just happened at the right time.
  21. It's strange that they put that in the "Accessories" tab. It would make more sense if it was in the "Front/Sides/Back" tab.
  22. Rob, It would be best if you would post the plan.
  23. In my Layouts I only use a couple of Text Styles and they are different than what I use in Plans. However, I am showing many of the Plan Text Styles available in my Layout. Can I delete those without effecting what's available in the Plans?