TFDIR variable cannot be locked or defined in site level?

I find it frustrating that in Structural Version 08.11.05.25, I could not use TFDIR variable at all. It automatically gets defined from TF_DATASETS it seems. Is it a known issue? I even tried locking the %lock TRDIR but still no success. Any help would be great for me. I am testing it for other application such as Architecture, Mechanical, and Electrical and there is no problem redefining TFDIR variable. But simply doesn't work in that version of Structural.
  • I think I solved my issue. The "_USTN_PROJECT" is defined in the "stflocal.cfg" which is pointing the project roots to "examples" folder. This is the reason why projects were not loaded in the Project drop down menu in Microstation manager.

    Thanks :)

  • Hi Steve,

    I noticed, my project.pcf's are not being read properly. Some of the variables are defined there and they are the ones which are not read. I will see if I can drill down to find the issue. The configuration works for all but Structural. So I am finding it little trouble to debug.

     I will let you know if I am able to solve the problem.

     Thanks,

    Rabi

  • Rabi -

    I tried adding TFDIR and TF_DATASETS to the workspace\standards\standards.cfg configuration file and I was able to change the default locations for the general (tf_imperial) and Structural-specific (stf_imperial) dataset files.
    It seems very odd that STF_DATASETNAME is not defined in your configuration. On my machine it comes from stflocal.cfg.

    Steve

  • Hi Steve,

     Thanks you for your reply. I understand what you tried to explain. My concern is, when I try to set TF_DATASETS or TFDIR in my site configuration file, Bentley Structural simply ignores it. I even tried %lock TFDIR and still doesn't work. I don't get STF_DATASETNAME either. I usually EXPAND ECHO $(STF_DATASET) key in to get the value which evaluates nothing in this case. It works beautifully with Architecture, Mechanical, Electrical but Structural. So I wanted to know if you were familiar with the issue. I am also not sure if its a bug or something i am missing that could be an unique setup to Structural. Any configuration specialists want to help me in this?

     Rabi

  • Rabi -
    Yes, both TFDIR and TF_DATASETS control the search paths for the Structural dataset files. Some of the general dataset files come from TFDIR. In addition, the Structural-specific files are located relative to TF_DATASETS. In the Structural configuration file, Structural.cfg, the dataset search locations are expanded to include additional directories relative to TD_DATASETS.

    TFDIR_COMP < $(TF_DATASETS)$(STF_DATASETNAME)/comp/
    TFDIR_CPART < $(TF_DATASETS)$(STF_DATASETNAME)/cpart/
    TFDIR_PART < $(TF_DATASETS)$(STF_DATASETNAME)/part/

     In an imperial workspace Structural uses the general dataset files from TF_DATASETNAME (tf_imperial) and the Structural-specific files from STF_DATASETNAME (stf_imperial). I think you should be OK if you set TF_DATASETS in your site configuration file.

    Steve