SNestor

Joey knows what he's talking about. This method makes it "easy-peasy"....

I would draw the fireplace wall...on an angle (like 45 degrees). Place your fireplace...I use a window for the fireplace and place a fire picture on the glass. Then...I'd take a backclipped elevation looking directly at the 45 degree wall. Then...I'd use a wall material region to place some tiles...one big region or small individual pieces if they will have different textures. If you want to change the texture on each then you may want to create a Cad Detail from view from the B/C elevation view...then draw each piece of tile using a cad polyline...then, copy and paste these tile cad blocks back to your backclipped elevation...then, convert these cad blocks to material regions. You can't convert to P-Solids because when you curve the wall...the solids won't curve along with the wall. Then...once all the material region tile pieces are placed, select the wall and curve it to your desired radius. The material regions will curve along with the wall. You don't want to try and draw material regions onto the curved wall...just about impossible.

Thanks Micheal. I saw the current temps in Alaska....brrrr....stay warm!

Darn that was easy...thank you! Very much appreciate the quick response. I saw both of these those posts when they were posted,..but, it's been a while since I have messed with "REF SETS" and I just plumb forgot what I needed to do.

OK...sorry for not asking this before. Can you use a "polyline" with a fill (such as shingles) and then reference the "fill pattern" somehow in a reference set? I ask because I haven't figured out how... Thanks. Below in the pictures I have drawn the polyline with the shake fill on Level 1...and I'm trying to Reference on Level 2...the cad polyline appears...but, no "fill pattern". Is the "fill" on a unique layer?

Rene - Thanks for taking the time to help. Dermot answered the question....I had "XOR" turned on.

Is there a way to show the hips/ridges of a roof either above or below using a reference layerset? Am I missing something? The edges of the roof appear (see pics) but the hips/ridges do not. I've tried this with some of the Chief OOB templates...and I get the same result. Thanks...

Here is a link to a Chief Video coving "Cad Details"...https://www.chiefarchitect.com/videos/watch/5477/

Use CAD DETAIL MANAGEMENT... See pic below;

Well, looks like the original topic has left the tracks... So...I'm excited about the improvements Chief has made in X12. Looking forward to using it!

First off...I'm no expert on plan views. However, I believe Chief's intent was to get away from Annotation Sets. You can actually add all your defaults right in the Plan View Dialogue. There is a box for the "current annotation set"...but, you don't actually have to use an anno set to create a saved plan view. In reality...Plan Views are the big brother to Annotation Sets. They do everything an Anno Set does...but other things also. You can't have two plan views open at the same time using two different Anno Sets...this is the first big advantage. Secondly...you can create plan views that use different "ref sets"...(which are nothing more than "layer sets")...so you can see different things below or above...and still be using the same annotations. There are other advantages which someone like Larry could explain I'm sure....

The "Residential Template.Plan" file contains some SAVED PLAN VIEWS. It should be in the Chief X11 Data Folder...in templates.

Chief needs to produce additional videos that explain clearly (and slowly) the power and time saved when using Saved Plan Views as opposed to Annotation Sets. You need to convince the Chief user base to "go into the light"...so to speak. Unfortunately, it appears from the many comments on this forum that SPV's are nothing more than glorified Anno Sets. I realize this view is inaccurate...but, I sense this is the prevailing view of many users.

Eric is amazing...thanks, I never knew about the "step floor and ceilings" option.

Wow...X12 is an amazing update! So many great new features and enhancements. Over the top!

You need to post the plan...

I think this is where Chief failed in the implementation of this tool. It’s a great tool that many do not understand how or why to use. Chief owes us some in-depth videos on this tool. And - Glenn is correct. I use plan views to navigate around the plan and to have multiple views open all at once. This is one of the big improvements over just using Anno/layersets.

I think most users feel the same as Joey. SPV just don’t provide enough value to take the time to change years of perfected workflow.

If given a choice between SPV and a much improved stair tool....I’d choose the stair tool. Not saying SPV are bad...but tell me why they were needed?

It would have been smart for Chief to make a series of videos on Plan Views. Videos that go from basic to power user...and why you’d want to move toward using them. But - Chief has done a poor job explaining Plan Views IMHO. Seems to me most users give them a try but don’t notice much benefit to using them - so they give up. If you’ve spent years learning and creating anno sets/layersets...hard to justify starting over with a new learning curve.

You should post the plan file.

Bob - watch the videos Eric did. Seems to have something to do with the default pony wall. I can’t seem to find the common denominator...to me it doesn’t matter if I create a custom pony wall or use the OOB pony wall Chief includes with their standard templates.

UPDATE: Chief has been able to duplicate the issue and are researching it. So...I guess that's good news. At least I know it's not me I was told the temporary solution is to not edit walls in the library... Hopefully they get it fixed soon.

I think I've uncovered a real big software issue with Chief. I've reported it...so, I'll let you know what they come up with. Thanks for taking the time Eric!

I don't believe it has anything to do with what Chief Template you are using. Attached is a video showing me creating a pony wall using a template from X9....same problem.