Recently I have found myself needing to add and change class visibilities during revisions on viewports quite a bit. I find that these changes do not always get executed on the first update, but often do work after making no further changes and re-updating. It is most noticeable when turning off a class visibility.
For example, imagine if I had a hardware class activated on a viewport, but then I realize I need the hardware to be invisible so I can dimension the hole patterns. I have a standard array of ortho views set up already, so I highlight all of them, I turn off the hardware class, and I update. The image of the hardware remains, though it often appears in a lighter color or just peaking out from behind the updated viewport. Then I update again immediately and it usually (but not always) comes out as expected with the hardware now invisible. If not, I update again and it probably works.
This happens very commonly if i am updating more than one viewport at a time. It seems perhaps a little less frequent if I update a single viewport, though it is still happening most of the time.
My current file is sitting at 155 viewports so far (I realize this is not a huge project for some of you but it is a lot of viewports in a single file for my typical workflow) and I don't relish updating them individually twice or needing to go back for an extra proofing session to find the ones that did not update properly.
Is anyone else seeing this or is it just me? Any thoughts on remedies?
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
jmcewen
Recently I have found myself needing to add and change class visibilities during revisions on viewports quite a bit. I find that these changes do not always get executed on the first update, but often do work after making no further changes and re-updating. It is most noticeable when turning off a class visibility.
For example, imagine if I had a hardware class activated on a viewport, but then I realize I need the hardware to be invisible so I can dimension the hole patterns. I have a standard array of ortho views set up already, so I highlight all of them, I turn off the hardware class, and I update. The image of the hardware remains, though it often appears in a lighter color or just peaking out from behind the updated viewport. Then I update again immediately and it usually (but not always) comes out as expected with the hardware now invisible. If not, I update again and it probably works.
This happens very commonly if i am updating more than one viewport at a time. It seems perhaps a little less frequent if I update a single viewport, though it is still happening most of the time.
My current file is sitting at 155 viewports so far (I realize this is not a huge project for some of you but it is a lot of viewports in a single file for my typical workflow) and I don't relish updating them individually twice or needing to go back for an extra proofing session to find the ones that did not update properly.
Is anyone else seeing this or is it just me? Any thoughts on remedies?
Link to comment
6 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.