Alaskan_Son

Maybe I'm missing something, but as some of the others have already pointed out, this is completely expected behaviour. Having a non-default pitch in your wall's roof settings will always override the default pitch. Sounds to me like you just need to reset your walls to the default pitch. Just switch to a wall tool, marquis select all your walls, open the dbx, click on the roof tab, and just enter the letter d into the Pitch field. Just a guess, but someone either changed the pitch in one or more individual wall definitions, changed the pitch in one or more of the wall defaults, or you're pulling a wall style from the library and that wall definition has a non-default pitch assigned.

Sent you a PM.

You have a schedule in the plan. Open that schedule, click on the label tab and uncheck Use Callout For Label.

Probably best to post a plan file for one of us to take a look at.

Really? Are you kidding me? You said "It only has to catch one person out one time to be an important behavior that should be changed." and then you went on to say " by all means don't wait until enough people note it because most users will not report bugs - or any other unexpected behavior but once discovered it seems it should be of the highest priority." So your suggestion is that it only needs to affect one person one time and that simply discovering that it is a problem for that one user somehow warrants that it be made top priority and moved to the front of the list. This is simply unreasonable by any measure. I understand that this is a major issue to some of you guys and I sincerely hope it gets addressed for you, but I don't see how its above debate or how it deserves a higher spot on the list. There are plenty of us who have major issues with countless other things in Chief. This particular one is a non-issue for me and many others who take time to report our concerns so it needs to be fairly prioritized accordingly. By the way, I'm kinda curious...why do you guys insist on using modified PDF's that have the same name? I'm honestly not trying to be argumentative. It just seems like good practice to modify the name if the file has been changed.

A world where everything is always the highest priority. A mathematical impossibility but wouldn’t that be great!?

My thoughts exactly. I personally never expected any of my picture files or PDFs to update automatically. That’s just me though. Having the option is a good suggestion but I certainly don’t think it qualifies as a bug just because SOME people expect something different.

I can tell you from extensive experience in this arena that reported bugs very commonly get fixed. Unreported bugs pretty much never get fixed. For the reported bugs that do not get fixed, I believe that it's usually a matter of priorities. If only 1 person is reporting a bug and 4 people are reporting another, which one do you think is going to get fixed? Take the wall hatching bug for example. I'm assuming Richard has reported it, but has anyone else? If that bug is the result of a notable programming flaw that would take a substantial amount of time to fix and only one or 2 users are reporting it, I don't know that I would want to spend much time fixing it either. "Why would we?" To make sure Chief knows about it. "Why should we?" To help increase the likelihood that it will get addressed. There was one easily reproducible and non debatable bug in particular that really annoyed the crap out of me that I reported multiple times. It remained unfixed for years though. Why? I honestly believe I may have been the only user who was reporting it. It finally got fixed (either in X9 or X10 I think), but my point is that if other users had taken time to report it, maybe I wouldn't have had to report it 4 or 5 times and raise a major stink to get it taken care of. Do us all a favor and just report this stuff. If you do and it doesn't get fixed, at least you know you've done what you can. If you don't and it doesn't get fixed, well...

This ^^^^ is a pretty bad one too. Not a matter of opinion, not debatable, not subjective in any way...just not important enough to fix I guess (insert sad emoji shaking its head).

This is not true. The extrusion shape can be edited from either end (left/right, front/back, or top/bottom), and in ANY view where you can see the extrusion profile (from either end). This includes almost any perspective view (so long as your camera is positioned in such a way that the appropriate face can be selected), opposing elevation views, angled elevation views, and orthographic overviews.

Chief actually does this with many referenced files. I imagine they're doing it to help speed the program up, but it's certainly a liability from a drafting standpoint and can be very limiting.

And also...HOLY COW!!! There's no shortage of stuff going on there. Looks like a lot of work.

Here's how to recreate what I did in the image in my earlier post. Create a Plan Footprint CAD Detail from the first floor using CAD>Plan Footprint. Select that Plan Footprint Polyline, open the Plan Footprint Specification dialog, uncheck Display Plan Details, and then specify a Fill. While still in the Plan Footprint CAD Detail, create another Plan Footprint by clicking on CAD>Plan Footprint again. You will be prompted to select a floor number. This time select the second floor. Select that new Plan Footprint Polyline, open the Plan Footprint Specification dialog, check Display Footprint Polyline and Display Plan Details (should already be checked), and specify the desired Fill. NOTE: For more control over whats displayed on the floor with the Plan Details, check Use Current Layer Set To Display and either use the appropriate layer set for that CAD Detail, or create a new one from scratch.

...and don't forget the new Inserts Into Wall option for symbols either. That one is a pretty versatile tool.

Try to update your video card driver.

Thanks for the plug Eric. To the OP: Yes, this can be done using a custom macro in the room label, but I can also be done using another special tool I created. The latter will even pick up on custom ceilings planes. Anyway, both methods require custom macros. Just shoot me an email at alaskansons@gmail.com if you want to discuss further.

Yup. I do something very similar. I’ll also add additional details to the file name sometimes just to help remind me what the fork in the road might have been or what the specific phase might be such as “Smith Res. (with columns)”, “Smith Res. Phase 3”, “Smith Res. 2 (tall cabs)”, Smith Res. 2 (short cabs)”, etc. The most important part to me though has been maintaining a “Smith Res. Current”, or like I personally name it...”Smith Res. Main”. Whenever I hit a fork in the road, I’ll do a Save As with a new naming suffix but always continue drawing using the most likely final version and making sure it has the “Smith Res. Current” name, even if that means doing another Save As immediately after the first and overwriting the previous “Current” version.

Sorry for the interruption. I’ll try not to let it happen again. Carry on.

To be fair, you kinda left out this important detail.

In my opinion, you’re going about this in a much more complicated and problematic way than you really need to. I’m not gonna write the code for free but consider this: Be be more straightforward and specific about what you want from Ruby, and make data entry more intuitive. Do you really want Ruby to remove numbers from the beginning and end of the string, or do you actually want to remove quantities and prices? And what if you or someone else decides they want to tweak things a bit or use a different naming/numbering convention? my suggestion would be this: 1. Clearly define what is what both in your macro and at your data entry point... part number = 1235 color = yellow and black size = large name = bumble bee suit price = 300 2. Break that down and reconfigure using additional code to get your schedule formatting... name>part number>size>color>price 3. Reconfigure separately to get your desired label... Large Yellow and Black Bumble Bee Suit $300.00 SKU# 1235

Yep. And for the maximum lights, you set that in the Camera Tools defaults.

Yes and no. In Chief, they both work to Delete objects. In many other apps, only the Delete key will delete objects, and in most word processing scenarios, the Delete key removes characters in front of the cursor and Backspace removes characters behind the cursor. Anyway, I digress. Like I said, they both work for me. I wonder if perhaps its a system setting you inadvertently messed with. Or, do you maybe run any other hotkey or macro recording software?

Might sound like a silly question, but just in case... You do realize that backspace and delete are 2 different keys right?

Never seen that before...at least not that I’ve noticed, and I create new 2D blocks all the time.

Chief seems to be getting confused because that roof single roof completely envelops that wall. In other words, if you look at it in plan view, the same roof plane exists above the wall, below the wall, to the right of the wall, and to the left of the wall. It seems you can fix it by just splitting that roof plane into 2 separate pieces...