Michael_Gia

Mods? What Mods? haha

Doesn’t show up on mobile. Can you post the link here?

You need a YouTube channel. I will subscribe. Great video. You cut to the chase which is appreciated. Thanks.

Ha ha. That’s it. I still haven’t set up X11 as default.

Call me crazy, but sometimes I don’t see the Material List tab in the Define Materials DBX. It just isn’t there sometimes. Sometimes I get: - General - Pattern - Texture - Properties Other times I get: - Pattern - Texture - Properties - Materials List Am I hallucinating?

I always forget about this one! That is definitely the best way to do this sort of thing. Did that come in with X10 or earlier?

I opened your plan. The rooms on the second floor that are misbehaving simply do not have the default ceiling height "checked" in the structure tab of the room dialogue box. Check the default for ceiling height for each is the long way to correct it. Quicker would be to select the one room that is at the proper default ceiling elevation and use the "match properties" tool to set all the other rooms to that correct height.

Somewhere, there is a comment from someone at Chief Architect that said they were unimpressed with the Imac Pro and that its price was not justified compared to a regular iMac or even a MacBook Pro with regards to any noticeable performance advantages over these far lesser priced systems. Here is the link to that post...

Anything you put on page “0” will appear on all pages.

Of course you can. Change something in a default from the active default list in the “saved plan view” dbx, and any plan view that uses that default is changed as well. The only difference is that, as was mentioned, since you have this control from the saved plan view dbx, anno sets are redundant. Which leads us us all the way back to OP’s original question in the post he started.

Too bad we can’t create “plan view sets” for elevations. You know, so that the plan view sets list can reflect the layout?...

Is this your approach these days, Scott?

I agree with changing anno sets as well. The idea of leaving the saved plan view to “using active defaults” for anno set is setting yourself up for potential mayhem.

...so, create a unique layer set and anno set for each saved plan view? now why didn’t I think of that? anyone else use this approach?

I kind of wish “saved plan views” worked the way OP thought they did. That is, whatever changes you make to a default or annotation, changes only in said saved plan view without affecting other saved plan views which share the same default, layer set or anno set. This way you actually have a wysiwyg version of the view that you will send to layout. Also wish you could set the layout page number in the stettings dialogue box of that view in advance.

Huh? I don’t quite get that. If you move your kitchen from one wall to another then your camera is looking at a blank wall. Isn’t it? I do wish we could rotate the cameras at least and reposition them for each new plan. That way we can at least keep the Camera View Name ans all we would have to do is re-dimension the elevation

Thank you! I’ll check that link out.

I still don’t get the hubbub about plan views. Other than when a specific reference floor is necessary I just use anno sets and send to layout. Am I missing something else?

As in other programs such as Archicad. You define your “levels” in the beginning. Every floor is a level. Each level is the “0” or default level for any room on that floor. Then each room’s level can be defined with respect to the floor level it is contained in.

+1 Richard The lure of Chief is its efficiency in how fast you can go from your client’s floorplan idea scribbled on a napkin to a Camera View complete with floor finish and mouldings, right in front of his eyes. Also cabinetry and how quick you can whip up a kitchen, live is another big advantage of Chief over Archicad. PBR or even the Standard View in Chief is just good enough to make using Archicad’s rendering pointless in as far as it would take to get a similar render. I also have to include Archicad’s insane inability to select a wall and then click on a dimension to change the wall’s position. With all of its power and seemingly limitless capabilities it still doesn’t have editable temporary dimensions! wtfffff..... These features are the “crack” that Chief offers, that keep us coming back. X11 has some great improvements. ...in my opinion.

While I love a lot of the new enhancements there just seems to be too many looooooong over due simple improvements that are sitting in the long-in-the-tooth suggestions forum. My SSA subscription is the only accolade I’ll give Chief for now.

You most probably have some room definitions with varying floor structure. Example, living room has 11-7:8” truss-joists with 5/8” plywood and then maybe your bathroom has 14” I-joists with 3/4” plywood. (Floor finish thickness doesn’t matter). So even if you diligently went through floor defaults per floor, when you change room type and the floor strcuctue of the room is different than the overall floor default then you have a real bad day.

Very nice. The title says “custom room schedule” but when I open it, the title is “note schedule specification” Also how do you get your macro for volume and name to magically appear in the “available columns” list in the Note Schedule? ...and why do you guys have Florida weather compared to us here in Montreal?

You were right sir. I was working on an X10 plan in X11. When I created a new plan in X11, all behaved properly. I think this gives weight to the idea that for each new version of Chief we need to create a new template or plan from scratch in that new version as opposed to using an older plan or template from previous versions. ....which sucks

Here’s the plan... https://www.dropbox.com/s/71yu4s7alqwoa81/X10 TEST.plan?dl=0