Pardon me for recycling text from Jim Austin's post on a nearly identical problem. I say it is a nearly identical problem because what solved the problem for him does not solve the problem for me. The reason I'm doing this in a new thread is because his thread is flagged as solved; my problem is not.
I have DGN files referenced into our sheet files and I am able to turn its levels on and off. I "Save Settings" before I exit. But when I re-enter the sheet file, the levels that are turned on and off have reverted back to what they were previously. Is there a variable or setting that will allow MicroStation to hold those level on/off settings?
As I said in the other thread, this problem affects only one file (that I know of), and affects this one file on my computer and at least one other in the office. The settings are saved properly (partly), which fact is obvious when I set levels how I want them and then open this file read-only. I say the settings are saved properly (partly) because certain of the levels in the working model turn off--which fact is undesirable.
For Jim's problem, MS_LEVEL_AUTO_SYNC_ATTRIBUTE_LIST was the problem as it included GlobalDisplay. Mine did too, but when I took GlobalDisplay out of the list, the problem was still not fixed for me.
An early question from Tim Hickman was "look at the attachment settings for the references and tell me what the "display overrides" option is set to." In this case it doesn't matter much because it affects the working model as much as it affects any reference. And whatever value it has, Microstation seems to behave the same way.
Another early question from Tim Hickman is what does "set refleveloverride" returns. "ON", just as was true with Jim.
I'm in a custom workspace. I don't have trivially easy access to one of Bentley's provided workspaces. If there are simple instructions for how to use it, let me know.
Any other thoughts on this?
because it affects the working model as much as it affects any reference
Ok so we can take the references out of the picture and focus on the active file not saving your level changes. You also say it is only one file doing this - so if you open another file you do not see this issue - then is this case it is not your workspace as this would effect any file opened using the workspace.
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Right. Thanks for your thought. I also don't believe it is my workspace. I do suspect it has something to do with the seed file used to create this file.
By way of disclosure, I created a new file from the proper seed file to replace the one that's giving me trouble. That file is fine, and serves the intended purpose. As such, this is not at all a problem of critical importance. However, I would still like to fix the problem file, as in doing so I may have a better understanding of how everything works together.
So, is there any next step in mind?