Joe_Carrick

It would have to be in a macro accessing a roof plane. (Roof Label or Roof Plane Schedule) This requires a more sophisticated approach than just a text box. - but might work if the text box has an arrow connected to a roof plane.

Most of the Core Library undercounter appliances don't currenty work properly. They don't display flush with the cabinet fronts and many don't add a panel if at the end of a cabinet run. I've reported this to Chief. It appears all of the Manufacturer Libraries are properly updated but some items may have been missed.

Usually SIPs. R value depends on the energy calcs which can require a thicker SIP.

Here in California with the wildfire problems I like to design "Unvented Attics". Basically that means the roof is the thermal barrier and there are a couple of additional code requirements. See IRC/CRC R806.5. Typically I would use an HRS (Heat Recovery System) for energy conservation - this actually requires an unvented attic.

You could use the: projected_overhang_area NVP's for each roof plane to determine the amount of soffit vents. Of course with a gable end roof plane that might not be 100% accurate since you would only want soffit vents at the eave and not at the rake.

X17 has many new options for symbols. For DW's, TC's, and similar appliances the following can be used: Appliances (built-in base cabinets) Appliances (under wall cabinets) Appliances (undercounter) If you have any such items in a "Place Library Object" toolbar button you can find the object in your library and edit the Options to make it function properly. Most - if not all Core, Bonus and Manufacturer Library objects will already have those properly set. You should however check the User Library Objects. Rene - take note

Offset should be 0 Bounding Box y should also be 0 However, I find that placing a Dishwasher or Trash Compactor or a Wine Refrigerator on a wall at 45 degrees is pretty much impossible. I will investigate further and report my findings to Chief. I suspect it's a problem with any angle other than 0 and 90.

BTW, You really should modify those Cabinet grouping (Architectural Blocks) so that the Dishwashers are not inserted into a cabinet. X17 treats DWs as being installed between cabinets vs in a cabinet - just like they ar installed/built in a kitchen.

Version 4 or Version X4 ? Those are 2 very different things. I Started with version 9, 9.5, 10, X1......

Steve, You don't even need to regen the 2D. All you need to do is edit the y offset of the bounding box to 0. The other option is to just delete the cabinet and place the dishwasher from the library. X17 symbols work correctly when placed that way. You will have a countertop above the dishwasher - or you can create a custom countertop over all the cabinets and the dishwasher.

FWIW, in X17 a Dishwasher doesn't insert into a cabinet. It is placed instead of a cabinet and the countertop generates on top of it..That way the Dishwasher is placed correctly in the plan view. But any existing plans brought into X17 at this time will need to be fixed.

I can confirm this, not only for dishwashers but also for wall ovens in cabinets. I had to open the object and set the bounding box y-offset to 0. I've submitted a bug report.

Does anyone have a good set of stair connection details showing top and bottom of various conditions?

Apparently it's programmed to be offset to one side, maybe even a little more. You shoudlprobably report this to Chief as a "Bug".

Try rebuilding the wall framing

AFAIK, that's just no longer available. Maybe it will be for the final release but I suspect they eliminated it for the Project Manager. Most drives today are fast enough that a ram drive wouldn't make much difference for undo speed.

A named material would work. Personally, I have a text file with spacing and other framing defaults that I read to set $Global values that my framing label macros use. It's not very elegant but it works for most framing members. I suppose you could have a few special objects that when placed (and sized - perhaps by setting the length between joists, etc) would set the spacing as a $Global value. You would need one for each different type or role of framing member. Another option would be a custom field "Spacing" that you could assign to the framing members individually so referenced macros could pick up the values. It could assign the $Globals depending on the "role".

What DPI setting are you using for the PDF?

So what happens if you create a room divider wall along those edges of the stairway?

Thanks Rene, My way of getting the path to the project has historically been different, relying on different NVPs. Your explanation should help me revise this - still resulting in a $global. It will take me a little time to ensure that it's working. See you at Couer d,Alene in August.

Hi Rene, This was a great video. Chief should have hired you to do their PM online presentation. I've over the years always kept my projects in Chief Version specific Folders with Project sub-Folders. I guess I'm going to need to bring everything forward to X17 if I'm going to use PM. I'm a little reluctant - especially with Beta - due to the risks of getting something messed up. IAE, do you have any suggestions for this? Should I keep my old Folder system and just use PM for current projects and older projects that become active again? Thanks

Seems a bit complicated. Can you show screen shots of this setup or a video?

Doug, The key is to extend the handrails the same 1/2 tread dimension and specify "No Transitions".

My problem is the text files are in my plan folder and I don't have a way to identify that in the PM. If they were just in a fixed Windows Folder it would work but in my use case they have to be in a project specific folder. I didn't see a way to get that. The NVP is probably what's missing.

Hi Val, I'm in the same boat but I have additional problems with the PM. One major problem is the inability to read/write external files with Ruby. I hope CA will fix that and simplify the PM. If so I might use it - but I'm not holding my breath. BTW, the PM also causes some problems with timing of macro operations.