CIVIL_XIN_FILE configuration

Thank you -will try it!

If they can not see any preferences in the list, it is most likely this: https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/31445/xin-is-blank---preferences-and-styles-lists-are-empty

I am having a perhaps similar issue:  I notice that, although the path in the variable definition remains the same, the source of the configuration variable changes from "Project" when PowerGEOPAK is first started, to "User" as soon as I invoke the Create Cross Section tool. This variable does not get stored into the User Configuration File, however.

But the issue I am having, which may or may not be related, is that for only some of the  PowerGEOPAK users at one client, they cannot access the create cross section or the annotate cross section preferences that are stored in the xin file. Nor do they have the option to Save new preferences as the Save button is ghosted.

We have checked the config files for typos, and moved the file around and changed names etc. to help to make sure that we were not missing a typo, but since some users can actually see the preferences from the xin file, I think that the variable expands to the correct location.

Any thoughts on what to try next?

Judging from the write-up of your problem, it sounded to me like the file Microstation was reading wasn't the file you (or your workspace manager) were expecting. In light of that, it was worth working out exactly where the value of CIVIL_XIN_FILE is being defined.

Looking at it, I see that in line 808 CIVIL_XIN_FILE is defined at the application level.

In line 981, it is defined at the user level, and (in this case) at line 975 you have the name of the file that defines it.

At line 1365, the final value is reported. Of course CIVIL_XIN_FILE hadn't been redefined since then, so it's the same as the definition from line 981.

The only thing I was suggesting to look at is that final value, to confirm that it is the right file that you expect it to be. I hope that helps, though I don't necessarily expect it to. Beyond that, I can't help on this.

Edit: Having re-read your problem, it sounds like this may indeed be part of a workaround without necessarily being a solution. (When you redefine a variable, it should be saved, but apparently it's not. Therefore, you need a workaround.) Locating exactly where CIVIL_XIN_FILE is defined, you will be able to define it to whatever it needs to be in the source file where it is defined now.

Derek, I got debug report. what's next?

6036.msdebug.txt