Alaskan_Son

Open that Patio Room and change your Stem Wall Top to match your Floor (0")

I can’t believe you just typed that whole song!!

This only works if you have Auto Width checked. The factors are many and as Chopsaw alluded to above, seem to be somewhat controlled by the initially pasted text. That being said, the main controlling factors are the Tab Stops and the Margins, and you can gain quite a bit of control by individually adjusting those. Also... Not quite correct. First...The first column can indeed be resized. Don't do it using the left side of the column though. Do it using the right side. Second...Just a quick power tip, but you can reset the seemingly uncontrollable width of the column on the far right to its minimum width by unchecking Auto Height and Auto Width, changing both those settings to zero and then immediately rechecking both.

Bear in mind that some of the advice above may or may not help you if you're using Interiors. The roof tools in Interiors are a bit more limited.

Why does your signature say X13?

The “exterior” notation you’re seeing is just telling you which side of the door you’re looking at. Spin it around and you’ll see it says Interior on the other side.

I’m really not sure what you’re talking about about but it sounds like you must be trying to marquee select walls. If so, you have to hold down the Shift key while drawing your “window”.

I don’t see how any diagnosis is necessary. It’s a simple informative message that means exactly what it says. The symbol has a bunch of faces and might slow things down. Either use something else or check Do Not Show This Message Again.

You just have to make sure you have the correct object selected. Chief will move or resize the object that is selected. It sounds like you were just inadvertently selecting the wall instead of the window.

You might be able to get a little extra speed with an upgraded video card but if you do, I really doubt it would be much and I doubt it would be worth the investment. Maybe if you were a techy geek who did the work themselves and had another use for the video card and possible power source upgrade (that may or may not help)...Otherwise, I think you should probably just keep plugging away with what you have and save up to upgrade to a completely new machine when you’re ready to pull the trigger.

It looks to me like the CPU itself is most likely your bottleneck. I really don’t think upgrading anything is going to do much good. Well, the one thing that MIGHT help would be to upgrade your hard drive to an SSD. It’s not clear from your description though and you may already have an SSD installed. You could also upgrade your video card

Ryan nailed it. Very easy to reproduce too. Its because Chief only recognizes a Room's defining walls with the wall elevation camera. Those walls in the middle are not being used to define the room. It's reasons like these along with many many others that I very rarely use the Wall Elevation tool and prefer to use a standard Cross Section/Elevation Camera along with a simple CAD mask. You could also optionally draw some Room Divider walls somewhere in order to actually enclose that kitchen area within the larger space. If its me, I'm just gonna use the regular elevation camera and a CAD mask though.

Not ideal, and I typically don't recommend using this method very often, but I think the quickest and easiest solution is probably to just break the Wall Polyline in 3D somewhere in the middle of that door opening and drag the bottom so that it's up above that other opening. Just remember you did that because the wall bottom will no longer automatically adjust for certain plan changes.

Schedule Specification>General>Object Preview Options>Scale Images and Use Plan View Scale.

I did those by adjusting the Baseline Angle for each roof plane one at a time....

Check 3D>Camera View Options>Toggle Textures. I'm guessing you have Textures toggled off.

The reason I asked is because Chief introduced the Measurement class in X12. Prior to X12, object attributes like owner.width were stored and reported as Floats which are numeric. They are no longer stored and reported as Floats but as Measurements with specified units. In Imperial plans, the units are inches, and in Metric plans, the units are millimeters. The reason your initial code wouldn't work is because "if referenced.width <= 42..." didn't make any sense. Since referenced.width is being stored as inches you needed to specify 42 of what. Eric's code got around this by converting width to a float (decimal) or an integer (whole) number with no unit. He could then compare the 2 values apples to apples. My recommended approach would be different and I would suggest taking advantage of Chief's Measurement class by just adding a unit to 42... "if referenced.width <= 42.in..." or "if referenced.width <= 3.5.ft..." As a parting tip, I would also strongly recommend against coercing a value into an integer unless it really makes sense for the application. It will always round down to the nearest whole number and values below 1 will always result in 0. It's just bad practice in my opinion. A 41.75" cabinet would report as 41 and any values multiplied by a value less than one would result in zero. The better approach is .to_f.round with or with an argument.

Are you using X11 like your signature says or X12?

In these instances there is no benefit to importing as a PDF anyway since a PDF produced from a scan is nothing more than an image file contained in a PDF. I try not to make a habit of reporting things just because I see another user having a problem or just because I might eventually have a probelm. This really isn't doing much good since among other things: A. It waters down the accuracy of the big picture as it relates to what users are really having issues with. I don't want Chief thinking 5 people are having a problem with something that's only affecting 2 users. There may be another problem that 4 people are genuinely having an issue with. Guess which one just got pushed to the front of the line. B. People need to report their own problems in order for Chief to get an accurate picture of how the problem is actually affecting their workflow, what solutions might be acceptable for that person who's actually having the problem, and the exact steps that led to the problem in the first place. C. I don't want to shoot myself in the foot. Chief has limited resources and if my other issues haven't been addressed yet, the last thing I want to do is add more to the list to detract from what really matters to me.

Have you reported this issue to Chief? I know I never did...mostly because I only EXTREMELY rarely import PDF's into my Layout. I usually just re-draw the desired elements right inside Chief.

There is. You can use a PDF editor and insert the desired PDF after Chief does it's thing. Not ideal but the end results are much better than the aforementioned alternatives.

... and the subfloor height above terrain setting is NOT a piece of elevation data.

You have to supply chief with at least two pieces of elevation data in order to create any kind of slope.

There are several ways. One way is to draw your deck at the larger size first, open the deck room, click on the Deck tab, uncheck Automatically Rebuild Deck Framing and check Keep Deck Framing after Deck Room is Deleted. Now move your railing walls. Another way is to increase the thickness of your walls. And yet another way is to make all your deck defining walls Invisible and then use No Room Definition walls for the actual railing. This is one of the trickier routes (especially with regard to dealing with the various wall transitions) but offers a few capabilities than the other 2 options don’t. There are other methods as well, but see if one of those does it for you.

Pretty sure I’m offended, but good stuff nonetheless. You’ve obviously done your research