Hello everyone. I have been working on my first project in OpenRoads Designer. Despite a few bugs, I have been making good progress. However, I have encountered a new problem for which I have been unable to find a solution. Beginning a few days ago, I have had the following issues appear:
1. I have been unable to get my level settings to save when closing files. I have "save settings" turned on, and I manually save the settings out of habit. Despite this, whenever I reopen a file, the levels on/off are consistently reset to a set of levels I do not want.
2. I have been unable to get my referenced in contour lines to display in some of my files, despite appearing to be turned on in the Level Display toolbox.
The only unusual thing which occurred during that time is that another person at my company opened and edited some of these files in an older program. I believed they used OpenRoads (not OpenRoads Designer). However, this issue appears to extend to files which they did not open or edit, so I am doubtful this is the cause. Does anyone have any idea what might be causing this?
There are a number of things that might be at play here.
There is a Wiki article that explains one of the settings: https://communities.bentley.com/communities/other_communities/askinga/w/askinga/1883/saving-reference-level-changes
Another thing to look for: See if your configuration is set to automatically sync any level settings (such as Global Display) back to the DGNLIB.
Also...there are three ways to turn the display of levels on and off. There is View Display (which is on a per-view window basis), Global Display and Global Freeze. I can't tell you the times I've gone 'round and 'round until I realized that I was looking at Global Display (which was on) when I needed to check Global Freeze (which was off). Or Globally a level was on, but it was off in one particular view...
There may be other things, but those are some really quick items that could contribute to what you are (or aren't) seeing.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Hi MaryB. Thanks for the ideas.
I looked around a bit online and in the program settings, but I couldn't figure out how to "see if [my] configuration is set to automatically sync any level settings (such as Global Display) back to the DGNLIB." Could you provide any more detail on how to do this?
As for my other problem, I, too, have mixed up the View Display/Global Display/Global Freeze in the past (and I am still not really sure what the exact differences between them are), so it was one of the first things I looked at. After playing around with more settings, it turns out, though, that apparently the major contour lines are on the incorrect level for some reason. So that issue is now resolved.
Thanks for the help.
The configuration variable in question is MS_LEVEL_AUTO_SYNC_ATTRIBUTE_LIST. Find out what (if anything) that is defined with. If it isn't defined, it isn't the problem, but it's worth checking.
Hello. I think I understand. I navigate to File>Settings>Configuration>Configuration Variables. Under this, MS_LEVEL_AUTO_SYNC_ATTRIBUTE_LIST has "Undefined" in the "Level" column.
After posting my last message, I experimented by creating a new basemap file with all of the other basemaps from the previous basemap file referenced in (i.e. my old basemap file and this new basemap file have all of the same files referenced into each). I turned on/off some levels in this new basemap file, closed the program, and reopened it. It appears that the on/off status of the levels in this basemap file DID save as expected.
I then referenced this new basemap file into a newly created sheet file with nesting turned on, as I had done previously. In this sheet, I again tried switching on/off levels, closing the program, and reopening it. The on/off status of the levels from the nested basemap file DID NOT save.
I then referenced all of the basemaps directly into this sheet file (i.e. with no nesting). I again tried switching on/off levels, closing the program, and reopening it. Again, the on/off status of the levels from the nested basemap file DID NOT save. However, the on/off status of the levels from the non-nested, directly referenced in basemap files DID save.
I opened the new basemap file and adjusted the level on/off in it, then I returned to the new sheet file it is referenced into. I found that the on/off levels of the referenced in new basemap file (i.e. the one with nesting turned on) in the new sheet file will always return to being the on/off levels in the new basemap file itself when the new sheet file is closed and reopened.
So it appears that the issue I am experiencing is possibly related to nesting.
That sounds maybe like SET REFLEVEOVERRIDES or the reference attachment setting "Display Overrides". And no, these are not the same thing. You can probably search the Help for them faster than I can type an understandable explanation.
By the way, if you have nested references, and you make adjustments to the level display of those references in the sheets, you will break the connection to the level tables of the nesting file. When that happens, any future changes to the levels in the nesting file will no longer be reflected in your sheets. This may not be an issue for you, but it was for us...
Answer Verified By: Matthew J.