Problem with Curtain wall profile editing

[dbaldacchino]

I have been running into this problem for some time now on a few occasions. I'm editing the profile of a curtain wall that is adjacent to another wall. Curtainwall joins have been disallowed. I edit the profile, align one of the edges to the adjacent wall, and as soon as I finish the sketch, the curtain wall edge "jumps" into the adjacent wall. It seems to be trying to clean up somehow.

The only solution I found is to align the profile to the wall and then move it at least 1/128" away from it. Why is this happening? Is this a known issue? I don't want to create stacked curtainwalls for this, although that's one solution. The other is to remove the mullions and change panels to empty system panels, but it seems to be a long process compared to just editing the profile.

[Mike Sealander]

Do you mean this happens with a wall perpendicular to the one you are working on? I've noticed that happening with concrete walls. I have a project where I tried editing a wall that is perpendicular to a number of cantilever wall beams that passed through it. Each time I created a profile that followed the section cut of the cantilever beam (don't ask why), Revit made one of the vertical profile lines jump to the center of a cantilever beam.
So, I don't think your issue is limited to curtainwalls. I think it's a clean-up issue.

[dbaldacchino]

Not just perpendicular walls, but even paralell ones (like when you have a curtain wall in teh same plane as another wall).

[aaronrumple]

Make it a 3/8" gap and call it sealant....

Buggy - I'd submit it to adsk.

[dbaldacchino]

Thanks Aaron. You're right, in actual reality there is a joint. The reason I don't want to model the joint is so that when we dim the curtain wall we get nice, round numbers. I'll submit tis to Support. Thanks for looking into it!

[brd]

Couldn't you still just dimension to the wall and not the end of the curtain wall, then just call the dimension "rough opening"?

[dbaldacchino]

Sure. This wouldn't work with our current workflow though since at the end of a project, we have been creating worksets to place each unique frame type (curtain wall/store front) on them in order to better check our work. This way we turn on only one workset in a frame elevation view and nothing else shows up, so there won't be an adjacent wall to dim to. So for example Curtain wall 1 will go on a workset called CW1, etc. Of course, there are always detail lines to use for faking dims :)

[Mike Sealander]

I don't know if this would help with your curtain walls, but I ended up disallowing joins on my concrete walls, and then aligning wall ends to wall ends, and also making walls by doing a lot of joining geometry.

[twiceroadsfool]

Ive found when that starts happening i can go to a Plan, and draw a detail line where the CW and the wall should meet. Then i drag both the CW and the wall a few inches away from it, and disallow joins on both. Then i use the align tool, or drag the endpoints and snap to the detail line. It alsways seems to work, or ive been lucky, LOL...

Ive also had TONS of BAD luck with using Edit Profile to make walls clean up where they join. I spent a couple hours this week cleaning it up when others had done that as well... I try to make sure they only use Profile to punch a hole in a wall or something....

[dbaldacchino]

Yeah, I try to NOT edit the elevation profile, but sometimes it's the easiest route (or so it seems!). In this case I tried disabling all joins in both walls and CW but it didn't help.Support said that it's been escalated to Development for further investigation, so we'll see.

[aaronrumple]

"Escalated to Development " = Thank you - now go away.

I've got quite a few items escalated that have yet to be resolved.

[dbaldacchino]

LOL! Yep, have a few of those too. And some "pending change request" or some other terminology. Well, my conscience is clean that I did my part ;)

[twiceroadsfool]

Ouch, is that what it means when something escalates to development? Bummer, i sent something in recently, and the tech replied that he was able to replicate the issue, and has now sent it on to development.

Should i not be expecting an answer? Hehe... I cant be too hard on them, i wouldnt want to have to do that job. :)