MS_DESIGNSEED

Hello,

I have defined the variable MS_DESIGNSEED correctly.

MS_DESIGNSEED    = $(_USTN_ORGANIZATION)Seed\aaprog-seed-2D.dgn

But when I am making a new file the seed file suggested is not the one pointed to by the variable MS_DESIGNSEED but the last one that was used.

Is this WAD? I would prefer I could force people to use a particular seed file (or at least I would like that the seed file that is suggested is always the correct one).

Furthermore: when i click on browse (right from the suggested seed file) I am not directed to the directory MS_DESIGNSEED is pointing to. As far as I could figure out this has to do something with the space in the path: C:\ProgramData\Bentley\CONNECT Edition\Configuration\Organization\Seed

Thanks for any input!

Luc Dierick

  • Luc Dierick said:

    I have defined the variable MS_DESIGNSEED correctly.

    MS_DESIGNSEED    = $(_USTN_ORGANIZATION)Seed\aaprog-seed-2D.dgn

    Are you sure?

    • It's preferable to use a forward slash as a folder separator in your configuration file:
    MS_DESIGNSEED    = $(_USTN_ORGANIZATION)Seed/aaprog-seed-2D.dgn
    • If _USTN_ORGANIZATION is incorrectly defined, then your definition that relies on _USTN_ORGANIZATION will also be ill-defined.

    Our freeware Configuration Variable Validator will tell you if a configuration variable is correctly defined.

     
    Regards, Jon Summers
    LA Solutions

  • I had the same exact issue when I was setting up our standards.cfg file. What I discovered was that I had manually navigated to a file to use as a seed when I started setting things up and that was taking ownership (don't ask me why) of this variable.

    I had new users who had never touched that field when making a new file attempt to make a new file and it pointed at the correct seed file working as I expected. I then manually navigated myself to the correct seed and it worked fine. We only use one seed file and I haven't set up any work space/sets yet so I have no idea what will happen long term the issue might come back.
  • This is WAD - it will remember the last file selected. If no file has been browsed to, then this variable will supply the file.
    Also - the variable is just a file name and not the whole path like you have it defined.
    MS_SEEDFILES is used for the directories in which to search and MS_DESIGNSEED is the file name you want used.

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

  • Has there been any change to how this functions over the last 5 years? Even if that is WAD for Connect version, why the change from how it worked in V8i? If it remember the last seed file you used, why even bother with the variable?

    We have a DOT workspace we use with many different worksets associated with it, which we typically bounce back and forth between. Each workset should have it's own variation of the master seed file. Generally speaking, we only set the geocoordinate system in the workset seed, and that's it. But this one little change could have a large impact if you don't set it correctly. Seems like there is a greater margin of user error if forced to browse to the correct seed file each time.

    Thanks for any insight on this. I wonder if I'm alone in my yearning for the way V8i handled the seed files?

    Ken

  • You are not alone many of us wish that parts of v8i still worked the same in connect modeling in connect is so much harder then it should be all for a philosophy of saving element history.