Joe_Carrick

Members
  • Posts

    11782
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. So here's my method: Find a door on the web from a cabinet door mfgr such as Conestogawood. Capture the image - gif is a good format. Create a new material texture in the plan (see help for how to do this) Set the material to "Stretch to Fit" Apply the new material to the Cabinet Door in your plan. Note that you will probably have to have a separate version of the material for drawer fronts and you will probably need to apply different scaling factors depending on the proportions of the doors and drawer fronts. Here's a pic of one I just did.
  2. Did you save it as a "Molding"?
  3. Export Default Sets, Layersets, Toolbars, etc from a copy of the plan in X11 (should be at least one in the X11 Archive Folder) and then Import to your plan in X12.
  4. Use the Schedule Callout for the Label and make sure that layer is displayed in the Room Elevation Camera Layerset.
  5. I downloaded a newer version and it works. The only problem is that it doesn't include the USVI as a "State" so I'm having trouble getting the Climate Zone. Puerto Rico is probably the closest. OTOH, since the temperatures are so constant I probably will just leave almost everything "Unconditioned" and anything will pass.
  6. No, but I'm working on a project in the USVI.
  7. I downloaded REScheck and exported from Chief. However, when I try to load REScheck it displays "Loading" for about 15 seconds and the aborts. What's wrong? Does it need to be excluded from Antivirus Checking or is there something else that causes it to crash? Thanks, Joe
  8. Anyone have a Shuffleboard Court Symbol to share? Something like the plastic tile courts that can be assembled on top of a concrete slab?
  9. I would like to insert a Tub or Fibreglass Pool into a floor or Deck, similar to inserting into a Countertop or Terrain Hole. Does anyone have a way to do that? Does it require placing a hole and then manually setting the height of the Symbol? It would sure be nice if there was another more automatic way to do it.
  10. The problem with that is that you get the appearance of just a narrow casing both inside and outside. It's not the same as a double door. But it you're just looking for the appearance in a rendering...…..
  11. A 55" TV is about the right size for a 24"x36" sheet. in Chief, depending on where you have the Library and Project Browser located. I use 2 additional monitors so I can have the plans at full size. It also eliminates a lot of pan/zoom while working.
  12. Is that really a mullion or is it an astragal? Chief doesn't include the astragal on a double door. It's a 3D detail that just isn't included.
  13. The outside mounting is not my favorite but sometimes that's what's existing. It's also a good way to prevent water intrusion problems when there's enclosed space below. So yes, we do need to be able to show it as fascia mounted.
  14. I am now using Glenn's method. It would be real ice if CA would just make the railings more flexible so that they could be set to the outside of the deck edge and extend down a specified distance. We can already offset the Newells. Why not the following: offset the Balusters offset the Railings extend both Newells and Balusters below the Deck surface. That really shouldn't be too difficult for the great programmers CA has.
  15. I know it's been done but I can't remember what the method was. We can offset the Newels but not the Ballusters and I can't seem to find a way to extend them below the floor. Does anyone have a link to a thread that covers this?
  16. When you create the symbol you shouldn't classify it as a molding. Geometric Shape or some other Symbol class would be appropriate.
  17. 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.
  18. You can submit an "online support ticket" or email "support@chiefarchitect.com"
  19. 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
  20. 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.
  21. 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.
  22. 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.
  23. Too much stuff (Macros, etc.). If I don't find the culprit(s) I'll see if I can strip it down.