Joe_Carrick

You could also try reducing the Text Margins. That also solves the problem.

So here's one other thing to check when you have a seeming lockup. Look on the Taskbar and see if there's a modal app (popup) running that's not visible on the screen. It might be asking for input but you can't see it because it's hidden behind Chief. If so you can bring it to the forefront and answer. This happen sometimes and we just don't recognize that it's the problem.

It's a bug that's been reported. The text line spacing is being affected by the top and bottom margin spacing. Converting to RT fixes it - until CA fixes the bug (assumedly the next release.

Not that you can see, but internally within TMM a loop can be entered. That evidently is what has happened in this case. It's always best to test that a variable is initialized to a value that works with any condition the script attempts to perform. ie: <=>+-*/, etc. If an error occurs within a script it's possible to initiate an infinite loop - particularly when using TMM which tries to determine validity. In this particular case I suspect it's not the macro itself that has the offending loop. Rather it's probably TMM that's caught in a trap.

It's not so much that it can bring CA down, just that it has control of the Application and doesn't allow any other input. But of course the OS can terminate any process - ie: via Task Manager. In this case the Ruby Script is running under Chief Architect so that's what has to be terminated.

Hi Mick, I took a quick look at the macros as listed in the original thread. They're very poorly written with no checks to make sure the variables are initialized properly - or providing a way to exit gracefully. I would not import that into my system for exactly the reasons I stated. One of those - or maybe both - have the potential to enter a loop with no way of exiting. I'm not going to try to "fix" the problems - just beware installing such code without knowing what sort of trouble it can cause.

Chances are that you have an infinite loop in the macro. When you open it in TMM it tries to execute the macro but it never gets out of the loop so it can't exit the macro and release the CPU. It may be that if you first select an object that uses that macro before opening TMM then the macro will exit properly. Proper error handling might eliminate the problem. It could be as simple as an unitialized variable.

Here's one I designed

It would be best to just use a Cabinet and modify it in the dbx to look the same as the Kohler Vanity. The Cabinet Tool has all the features needed to create almost any Casework. You may notice that all of the "Cabinet Manufacturer Libraries" only have the materials, colors, etc. They rely on the Cabinet Tool to provide the basic structure. Chief had and maybe still provides a "Cabinet Symbol" tool - but it's not at all easy to use. Using the Cabinet Tool provides a much better method. Once you've configured a Cabinet you might want to use again - save it in the Library.

Correct. But once you've numbered them you can link other Plan Callouts to the view and there's a macro to fill in that number.

Hi Rene, Do you include your toolbars with this? Are they needed to make the system work? If I purchase the Standard can I upgrade to the Pro for just the difference of $200?

Correct. It's whatever the name is in the Project Browser

Also check to make sure you haven't assigned that layer to something in the defaults.

Larry, Try a marker (very small)

This rather obscure setting prevents the wall from obscuring the surfaces of abutting floors, ceilings and walls. This is important especially for 3D Views - since otherwise you might be seeing a wall or floor that doesn't have a surface material at the intersection (half walls, railing walls, etc.) Instead of using a PSolid to cover such conditions it's usually possible to eliminate the problem just by specifying the Wall Type as a "Partition". Personally, I think this setting should be more a general setting than a "Wall Type" setting.

I think it would make a lot of sense if "Wall Types" could assigned a default [exterior, interior, railing, none,etc....]. Then the software could know and inform if a wall was being edited to a type that wasn't appropriate - allowing the user to accept of reject.

The only downside is if you need to edit stretch planes or other details. Then you would need to actually copy the item to your user library rather than just linking.

I have my user Library organized in Folders. Mostly I have in broken down to Layout Objects vs Plan Objects. Within that context I have Text, 2D Symbols, 3D Symbols, and then subcategories within that. For things I use a lot from the Core, Bonus and Manufacturer Libraries I generally just link to the item rather than actually copying it. That's more efficient. Maintaining a useful organization if an ongoing process but can be a big help in the long run.

Really? X14 is the first time we've had the set a default for locating the location of a Layout Box Callout Label. Actually, we never even had Layout Box Callout Labels before. On that basis I contend that it's totally new in X14.

Dermot, it's the LAYOUT BOX I'm talking about so a positive (not negative) offset value is correct for positioning the Label up from the reference location. This is totally different from Wall, Door, Window, Cabinet, etc Labels IOW, the offset means "Move this Much - to the (x) right or (y) up" The software should be attuned to the way a designer or draftsperson thinks - not an arbitrary programming "rule". ie: User Friendly

A couple of comments: Please fill in your "Signature" so we know what version and hardware you're using. Please post Questions in the Q&A Forum. Tips and Techniques is for sharing your tried and true methods. You could do one of two things to solve this: Use 2x12 Rafters Use 2 Framing Layers (2x8's and 2x4's) for the Roof Framing. (the framing would be stacked but only 11" thick so you might want a 1" air gap between) OTOH, if this is an existing attic and you just want to furr-down then Perry's method would probably best.

Layout Box Callout "Y-Offset" is backwards. To place it UP from the referenced location a "negative" (-) value is required. It should be a "positive" (+) value.

I use a macro for the openings in Framing Plans that shows the Header_Size, # of King Stud, # of Jack Studs. This information can also be included in the Door & Window Schedules - but I'm not sure the framers would pay much attention to that.

Stange, I have no problem inserting a Niche. It doesn't matter what the wall is - even a single layer concrete wall works. What are your "Wall Niche" defaults? Maybe one of the dimensions is too small.

Do any of you have a Matterport Pro camera? Are you using a service for your 3D Scans? If so, what's the typical cost per sq.ft.?