HumbleChief

...I've been BSing my way through plans for 15 years.

There's more than one method, check the training videos under 'Layout'

Cool Scott, I had scheduling problems the last couple meetings - hope I can make this one!!

Are you on the correct floor? Sounds like you might be on the attic floor looking for a doorway on the floor below? Wild guess.

I would very interested in the workshop as well.

That's a great idea Perry.

Of course it's user error but whether it's user error or not seems a silly argument IMO. Once a user knows how Chief works it's pretty easy to figure out - it's the 'knowing how Chief works' which can be difficult to intuit. The example Richard give clearly shows how Chief works so anyone who doesn't know this behavior will think there's something wrong with Chief but it's 'user error' because the user has to understand Chief's behavior. Is it the user or Chief's behavior? I would have thought that raising the floor then lowering it back to its original location would have kept the footing in the same location like it would in the field but Chief has shown time and time again it works nothing like buildings do in the field. Like working floors from the top down. You would never do this in the field but Chief has decided that this is the paradigm that works with their software. If you don't get this backasswards way of thinking then once again it's 'user error' but it really is an error in the paradigm Chief has decided upon IMO. Fine, now the users who don't know you need to work floors from the top down (seems weird even typing it) - which is every new user to Chief - has to learn this as well as many other idosynchracies that don't make intuitive sense or behave like buildings do in the real world. Fine again and not really a big deal as all software programs are difficult but every time Chief has an opportunity to make things more intuitive they seem go the other way.

Found it. Thanks Richard, I had a long run of cabinets and a couple cabs in the middle had the counter tops still turned on and the custom counter top was applying that counter top setting everywhere.

Checked there first, of course, but the custom counter top is placing a back splash where I don't want one and can't seem to turn it off.

Is there a setting somewhere? Thanks

Hmmm...I had no idea Archicad could cut a 12" beam...

My older HP110 no longer has Win 10 drivers or support. Which plotter do you have? You can always print to PDF first, which is what I am forced to do but prefer it anyway.

I'm not sure how one could tell for sure but the newer NVidia cards aren't that expensive for a LOT of graphics power. Will that fix it? Again no way to really tell until the money is spent and the computer put through its paces.

Chief has a major problem with large models, there's no denying it. Check the system in my signature. It's pretty muscular but I still get bad slow downs when the models get large. I'm not sure where the bottle neck is, either graphics card or CPU but you'll need LOTS of muscle if you want to try and get through Chief's large models without slowdowns. I'm not talking bothersome slow downs, I'm talking crippling slowdowns that you have to wade through once a model gets so large. If you want a fast computer here's a link I just posted to the Chatroom that has about as much budget muscle that can be reasonably afforded. https://chieftalk.chiefarchitect.com/index.php?/topic/10545-need-a-fast-inexpensive-computer/

Yeah don't make it so difficult. Create a roof plane where you'd like the cricket to be and set the pitch to 1/2":12. They almost never end up beinghe right height etc but just move the plane up/down using the roof dbx or the transform replicate tool. Break the main roofs and join them to the cricket. Some times they are a necessary evil but we do them all the time. They might be ugly, but only from Google Earth.

I sent a couple renders to Layout and didn't notice any 'bluriness'. Not sure what the problem is but am pretty sure the blur is caused when sending 'live' elevations. Don't know about renders.

Pretty sure you're referring to live elevations Perry, not sending a bitmap. EDIT: You could be right about that Perry - I don't send renders to Layout very often. If you send a bitmap picture to Layout the best way to get the best resolution is with the largest monitor you can access. Also can you 'crop' the picture by zooming in a little before you send to Layout? That will save some resolution for the final picture.

Text 99% of the time

Ha Ha...make that 15 years later and still confused. (Wish I was kidding)

...and a VERY good one IMO. I agree Chief should be consistent as in the example you show.

I'm confused. You are in a 3D view and moving a line with the 'Z' coordinate? I'm not saying you're not, but I don't see how that's possible. How do you draw a line in a 3D view? How do you select it? Move it? Can you show an example? (You must be talking about something else because the line tool isn't even available in 3D views, that I can find anyway) ...and Johnny, big deals are not inherently BIG, they are always as big as you make them. Learning a new program that does things differently than the norm is not a big deal - unless you make it one.

Newell...really?? I think your dining room gable wall should be larger and perhaps a pretty blue color to go with the drapes and define it as a gable wall but don't balloon though the ceiling below, or above and set the stucco molding to be larger and inverted but don't change the color, I really like that color. Windows should be larger and not so clear. ...or maybe post the plan so someone can really help you

I don't always have problems but sometimes I seem to follow the same methodology and end up with some really odd and confusing settings and floor/room heights. I think it's always user error but the entire floor/room height system should be easier to understand IMO. I don't think I've ever even seen a really comprehensive tutorial on same.

Good question Scott and I think it's a bug in the paradigm that Chief uses that makes these simple tasks difficult to understand and implement which causes unneeded user errors. In this case there's a setting in one of the dbx's that doesn't allow for a single room's floor height to be dropped or raised independently of the other rooms - but sometimes it does allow for it. It's very confusing. Not just for me but obviously for Dave as well. Dave can you please post that plan you are referring to above? I'm very curious what you/I might be missing.

Somehow the floor heights are depending on the foundation room below but I simply will never understand the paradigm Chief has chosen to define room/floor/ceiling heights.