Alaskan_Son

Try importing as a different SKP version. Also, you should be able to post the SKP file if you zip it first.

Still don't know exactly what you are trying to do, but maybe you can elaborate...I have used other programs. I actually can't stand how most of those select objects. Maybe if once you illustrate a little more clearly and if there is no reasonable solution given, you can explain how another program would select the objects in question?

Yes, you explained it. Unfortunately I still don't understand. I'd like to help, but I'm just not following. It seems maybe you are trying to select a group of things but not all of that group. Can you not just use match properties and then un-select what you don'tt need? Or perhaps select part of your group, block it, select another part, block that, and then block those 2? Without seeing your specific issue I'm just taking stabs in the dark.

It would most certainly NOT help if you were to attach some screenshots or a plan. Oh wait...yes...it would.

A quick example illustrating one I did not too long ago...

This can be done a number of ways. You can use any number of primitive solid tools, slabs, etc. You can also use a combination of smaller "cabinets", shelves, soffits, and/or partitions to build your cabinets. It sort of depends on the cabinet design as to which option works best. One thing I've personally done in this situation and what probably has the least negative effect on schedules, material lists, etc. is just build the cabinet to extend through the ceiling and add the extra parts and pieces required for the ceiling transition manually. That was actually one of the only times in recent memory that I've chosen to deliberately model something inaccurately. The ability to specify the shape/slope of the cabinet top is one of a number of cabinet improvements I'd really like to see.

Do you have a picture to illustrate what you're talking about? I"m not sure I follow.

I know, right?!!

Agreed. I've always wondered why it was located in such an odd spot.

I wonder if perhaps you aren't hitting the key(s) more than once or if maybe you have a sticky keyboard or something along those lines.

Doubtful. That's what I use too. On a side note...I've found "Control Z" to be a rather humorous way to communicate that you wish you could undo what you just did. I find myself at the job site yelling "Control Z!!" sometimes : ) I'm thinking a "Hotkeys For Life" thread might be in order. That would be one expensive keyboard...

This I have never seen. Can you elaborate a bit? The only way I can see this happening is if your changes were all made in a single dbx (i.e. it was only one operation).

Can you post a screenshot? Or better yet...a plan?

Block them and then make your move. When you're done with the operation, unblock...or perhaps even leave them blocked for a while depending on your situation.

Yes, please post a suggestion. This is something I run into fairly often. I've tried to learn from those mistakes and block those complicated groups before I try to move them, but I often times still forget.

The temperature thing is a very good point. I learned that a few years ago. I take my PC apart every so often and clean all the dust out really well to avoid those crashes.

Without seeing your plan or plans this is just a stab in the dark, but I'm assuming you have 2 different plans for existing and proposed. If you were already using layers I assume you would have known the answer. If my assumptions are correct, I would probably do the following... 1. Do a Save As of the "existing" giving it a new name like "Existing Temp" or whatever you want and delete the house (or portion thereof) that you need to replace. 2. Do a Save As of the "proposed" giving it a new name like "Proposed Temp" or whatever you want and delete everything that you might not need (can skip this step if there's nothing extra in that plan). 3. Make sure all your layers are turned on and Select All. Now Cut or Copy and then Paste Hold Position into your previously cleaned up "existing" plan. 4. As long as everything above went smoothly, you can rename your new file(s), delete the temporary versions, and then relink your layout views as necessary.

Definitely seems odd. As long as you've tried deactivating the license several times with no success, I think tech support may be your best bet. You could try downloading the trial version for now just to keep you moving in the meantime, but I'm not sure whether you can save changes or not.

I still do 45 degree uppers all the time. 45 degree lowers...I don't recall EVER using.

2 things... 1. Is Chief open on your Mac? If so, that may be your problem. You may not be able to deactivate a license that is currently in use. 2. There's really no reason you should need to deactivate the license from your Mac (except maybe that the program needs to actually be closed down). You should be able to do it from any computer. Maybe try disconnecting from the internet and starting up Chief. I often times don't have internet access on jobsites and Chief essentially lets you run the program without activation but stipulates that you need to activate the license within so many days (I think its 2 weeks).

Very creative Jintu!!

I would personally probably just use either a wall covering or a wall material region for the wainscoting and a moulding polyline for the other 3 items. I obviously haven't seen your plan, but I imagine its only the wainscoting that needs notching.

Not too shabby Rich!

I think the way you ended up building those walls (solids/symbol) was the best way. Just for the heck of it I tried to use the wall tools to reach the same result. Here's the best I could do. Its not bad, but what you did was better. Cinder block.plan

I agree. We use SU but never very often, I've become proficient enough with Chief's tools that I usually find it faster to model in Chief, however if you are already proficient with SU and a relative new comer to Chief, as Joe said, just model it in SU and import it as a symbol or just do the whole project in SU. Don't get me wrong. As the guys above pointed out, its totally doable...just not very automatic and not very efficient if you're new to the program. That being said, it would probably be an EXCELLENT exercise in learning Chief's various primitive modeling tools if you actually take the time to model it in Chief.