Charles Karl
2015-10-08, 03:42 PM
There is a scenario that was not understood right away on our current project, and the consensus was that someone was screwing up the model without realizing what they were doing, or there was a gremlin in the software.
Well, I discovered first hand that when editing within a parent view using temporary view override that any dependent views that were disassociated from scopes boxes would rotate to true north from plan north. Where this gets real interesting is that if you don't catch it and restore view properties, the rotation will stay. Can you imagine print day and seeing one of your block plans rotated and you don't know how it got there. I don't know if autodesk knows this yet and I don't know if 2016 has the same issue, but all beware of this oddity in the software. Or, don't have a mix of associated/disassociate views/scope boxes within the same parent view.
Well, I discovered first hand that when editing within a parent view using temporary view override that any dependent views that were disassociated from scopes boxes would rotate to true north from plan north. Where this gets real interesting is that if you don't catch it and restore view properties, the rotation will stay. Can you imagine print day and seeing one of your block plans rotated and you don't know how it got there. I don't know if autodesk knows this yet and I don't know if 2016 has the same issue, but all beware of this oddity in the software. Or, don't have a mix of associated/disassociate views/scope boxes within the same parent view.