Joe_Carrick

Members
  • Posts

    11782
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. Recessing in most cases because other things will be attached and I need a flush surface.
  2. I think I'm just going to note it as: 1/2" x 1-1/2" Threaded Studs @ 32" oc Welded to Steel Beam These are standard products the Steel Fabricators are familiar with.
  3. Does anyone have details of the threaded studs to steel beam - ie: welded to beam with nuts & washers for the 2x plates?
  4. When you select a cabinet or multiple cabinets: open for edit highlite the custom field in the Object Information Panel enter your text in the panel to the right. (or if you have a predefined text macro for that test you can just put the macro there)
  5. Just add the custom fields. Then when you've selected the desired cabinets you can enter the text you want in the correct custom fields to show up in the Schedule.
  6. I think you're almost there. Watch Rene's video Selecting things accurately in Chief Architect X15 - YouTube to see how you can select just the objects you want to edit any of your custom fields. They will then be in the Schedule and you don't need to select them individually or enter the text in the elevation view.
  7. We had a CalCOMP system with a 50 MB removable HD. I actually went to work for CalCOMP where we had both 50 MB & 100 MB removable HDs. Boy the aingst when someone had a head crash and spread it to 50-60 HDs. You really needed the tape backups.
  8. That was my other thought. Plan View has different available tools than Layout. Chief Premier has a lot more File Export & Import tools than HD Pro.
  9. Was that a CalCOMP system by chance?
  10. What version of Chief are you using? It appears to be either an HD or Trial version. Most of the Import/Export tools aren't available in the Trial version. I'm not sure about the HD products/versions.
  11. Kate, I don't know of any file type that can be imported into Chief to do that. Perhaps a 3D file like SKP or OBJ but from AutoCAD you can't get that. You are unfortunately going to need to build the model in order to do a rendering. Tracing over the DWG using walls, doors, windows, etc will get you close.
  12. Rene, Inevitably an Evaluation Error is caused by some variable (NVP) not being initialized. I find this most often with macros in a Schedule column. In which case I have to open & then close the Schedule. It really depends on the macro and what "error handling" is being done in that macro. In my case I have 2 schedules and one of them isn't initializing an array that the other needs data from. I would need to see your macro that's producing the error to be able to identify what might be causing it. I agree with you it's most likely a bug in how Chief updates macro execution. They specifically tend to minimize so performance isn't degraded. Repeated macro execution can slow Chief down.
  13. Preferences > Appearance > Toolbars - Button Size.
  14. Just don't include it in the Wall Schedule. You can label it separately.
  15. Notes are not the same as Callouts so: I want separate tools. A combination tool could be useful as well. I want separate defaults for Callouts in Plan vs Layout. Layout Box Labels have a Callout Option. This is the primary use for Callouts in Layout. Callouts (Stand Alone and Camera) in Plan are used to reference the Views sent to Layout. Notes are typically used to minimize the text on a Plan View. They provide a reference to the Note Schedule(s). That said, I prefer actual text in my CAD Details to minimize contractors & subs from having to search for the information. I've seen too many ConDocs with Notes incorrectly cross referenced.
  16. That's because CA keeps making changes to their Catalogs. You can of course skip the updates and just do them at a more convenient time.
  17. Eric is correct that it works in a text box - but you have to put it there as a macro evaluation. ie %...........%. You can even use a RTB and get all sorts of formatting. The advantage however of using a custom macro is that it can get data from the owner or referenced object and use that to return results.
  18. The wall in the 6th row is controlling all the row heights. Why is that wall so thick?
  19. I just tried the following in the Ruby Console: y = 450.00 ; x = Math.sqrt(y).round(4) ---> 21.2132 It works fine. However, the data in the parentheses has to be numerical. Otherwise you'll get an error. Also note that Ruby is case sensitive. So as Eric said, Math works, math doesn't.
  20. You would need a custom macro. It's not a difficult one to create.
  21. This is why I don't like the Schedule method. The Detail Callouts should be based on their position on the Layout Page automatically. Then any Plan Callouts linked to the view sent to Layout will automatically be correct. Detail Callouts should be based on their position on the Layout Page & Plan Callouts should always be correct.
  22. I use a custom sheet size for my Interior Elevations. Typically 4" tall x 7-1/2" wide with a corresponding CAD Box (invisible linestyle) When I send the view to layout it's automatically that size and will snap to other layout boxes. The Layout Box can be resized if needed but I only need to do that for the width in most cases. I also have a default set for my layout boxes so they are labeled to match the project browser name.
  23. Actually using the "Match Properties" tool works. OTOH, the "Object Painter" tool really should match the "Arrow Style". Submit a request.
  24. Unless you have birds that perched on the clothes line and left their calling card.