Configuration Variable for defaul plot config file

We use custom plot configuration files for each project to adjust output colors of fill shapes and utilities for our plan sets. These are stored in the symb folder in our project directory. The problem is every time a new dgn is added to the pset, it resets the plot config to "FDOT.pdf".

Is there a default project configuration variable that would make this select my project plot config when adding new DGNs instead of reverting to FDOT.pltcfg?

I checked this master list here: but none of the ones I tried seemed to work.

Thank you!

  • Nicholas,

    There are two variables to work with here. One is the MS_DEFAULT_PLTCFG variable which is undefined.  You could define it in a "CUSTOMVARS.TXT" file which you would place in your C:\FDOTSS10\WORKSPACE\USERS\ folder for a standalone workstation or the same location on the server for a client/server configuration.

    Additionally in that CUSTOMVARS.TXT file you'd want to add the project SYMB folder to the variable MS_PLTCFG_PATH. You'd want to use an angle bracket > to specify the variable so as add to it and not overwrite the current value.

    Let me know if this makes sense or if I can be of further assistance.


    Matt Sexton
    CADD Applications Support Coordinator
    Florida Department of Transportation
    Engineering/CADD Systems Office

    Answer Verified By: Nicholas Ruiz 

  • Matt,

    I created the CUSTOMVAR.TXT file under my local folder (we use the workstation setup). I added a variable to the project configuration file:

    FPID = [typed out the fpid]

    Then in the CUSTOMVARS.TXT I have to variables:


    For each project configuration, I will just insert the FPID variable because we always name the custom plot config FPID.pltcfg. This worked for me so that now when I add files into the pset, it won't revert to the FDOTPDF.pltcfg.

    I ended up using = signs though in the customvars. I am wondering if that will cause issues when moving to another project, or if the custom plot config doesn't exist. When I had the >, it kept wanting to use FDOTPDF instead.