Walls on the A-Wall Layer Turning on When We Don't Want them to

[IMPACT Drafting 1]

I've been battling this for nearly a year (since ACA 2015). We leave all of our 1st floor walls on the pre-set A-Wall layer. Our 2nd Floor walls are on a layer we've created (2nd-Wall). Even if the walls on the A-Wall layer are turned off AND frozen while we're working on the 2nd floor, if we do ANYTHING to our 2nd floor walls (move, copy, mirror, stretch, etc.) the A-Walls automatically turn on and unfreeze.

I can't for the life of me figure out why. We did not have this problem in ACA 2014.

All help is appreciated.

Cheers,

[dkoch]

I can reproduce that behavior in 2015 (SP2) and 2016 (SP1), as well as not having the A-Wall layer turn on/thaw in 2014 (SP1). I am not certain that I can offer any help, however.

That will be a potential problem for my firm, as we are preparing to roll out 2016. We do not have multiple floors in one file, but we do renovation work, and the same thing happens if you have a renovation project. When working on the demolition plan, with A-Wall off/frozen, edits to the Walls on A-Wall-E or A-Wall-D turn on and thaw layer A-Wall.

[dkoch]

The same thing happens with Doors, too.

[dkoch]

After additional review, all that is necessary for the layer specified by the default layer key for an object to be turned on or thawed is for an object of that type (on a different layer) to be selected. I have reported this behavior to Autodesk and asked that it be fixed.

The more feedback Autodesk gets on this issue, the more likely it is that something may be done about it. You can help push action by providing feedback on this page.

[neje]

Yes this is a known defect from ACA15 & 16 but fixed in the 17.
Disappointing and makes it quite hard if you work with multiple levels in the one file.
Edit : So in 17 it's back working as it should and was in 14 (I think) and prior. There was a change to layers that possibly brought this error in - transparency?



Deleted [still not fixed in 17.]

[dkoch]

Yes this is a known defect from ACA15 and still not fixed in 17. Disappointing and makes it quite hard if you work with multiple levels in the one file.

Really? I have not installed the shipping version of 2017 yet, but I was told that this issue had been resolved in time to be included in the shipping version.

[neje]

Well David looks like you are correct. Woohoo. It wasn't in the last beta so I stand corrected.