Apparently, just including this directory at the network level is not enough. Not surprising, because I haven't seen anything to redirect to it...
I would like to include some organizational standards (at the network level because I don't plan on doing anything more on the local level than I have to) but I'm not certain how to accomplish that without jumping ahead of system files or redirecting incorrectly.
What would be the best way to do this? I could add an %include somewhere, but at what level would I do that? Before Workspace? During Workspace? Add something to ConfigurationSetup.cfg or WorkSpaceSetup.cfg?
There are a bunch of .cfg files automatically included if they are present. For example in our WorkspaceSetup.cfg I define _USTN_ORGANIZATION and all the .cfg files in that folder are automatically loaded (in alphabetical order).
Once a WorkSpace & WorkSet are selected, all the cfg files in _USTN_WORKSPACESTANDARDS and _USTN_WORKSETSTANDARDS are included automatically.
I recommend going through the msconfig.cfg in the Config folder in the where the application is installed. That shows all the cfg files that get loaded and in what order.
Answer Verified By: MaryB
As for order of loading things, the default order is:
Organization -> WorkSpace standards -> workset standards
if you use Organization-Civil, that isn't automatically loaded, it's usually loaded by the workspace or workset with a manual %include.
I like putting our corporate standards in Organization because I can lock things before the workspace or workset handle them, and what I put there is loaded by all projects.
I agree with Kevin, but it is hard to see exactly what you are doing. It seems like you are splitting everything out Organization in one location, workspaces in another and then your projects/worksets in yet another location....
CADD Manager | CADD Department
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
I'm not actually trying to do anything terribly different than ORD already does:
On my network:
On my computer:
The only thing I really want to do is bypass the local configuration at the Organization level (and beyond) to send it over to the network. The other caveat is that we have a separate project drive for all of our projects. While I can store the project/workset CFGs & DGNWSs in the ...Workspace\Worksets\ directory I need the workset CFG itself to redirect to the project directory. That part isn't hard. It's figuring everything upstream that's got me running around and overthinking.
Kevin's suggestion to redirect _USTN_ORGANIZATION in WorkspaceSetup.CFG actually seems to have worked. I don't have a lot of organizational standards (beyond a collection of cell libraries) but I do have a few (including the variable pointing to the project drive).
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
In WorkSpaceSetup.cfg I define all variables that pertain the the overall setup of the configuration. In Organization I put actual settings/files that are used with the product(s) themselves.
So our WorkSpaceSetup.cfg has:
Although I currently let user prefs go with the defaults this is the file where I'll set them to our company's OneDrive once I'm happy with how what I setup is working.
Things I've noticed setting up ORD (although most apply generally):
Like you I've got little in our organization standards, I have had to create some empty folders in ours to make things work, ours has empty folders named: Descartes, Prostructures and SPC
Things I do in our Organization folder:
Corporate: vba, custom menu, named expressions & item types, reports.
I include the .shx fonts that ship with ORD and define MS_DWGFONTPATH to point at them. I found many clients would set MS_FONTPATH with an = and include no SHX fonts. this caused problems either working in dwg mode or importing dwg files, i think both. Setting MS_DWGFONTPATH separately let me leave their config alone and if they did ship SHX fonts I could just undef the dwg font path.
I have an MstnFontConfig.xml that hides rsc fonts named arial. I only load this in client configs where they include an arial rsc font but their text styles use the arial true type font, but I have the file in the organization level so it's easy to find. (If you don't hide the arial rsc font the arial true type won't show up in the font picker, it doesn't actually break the text styles)
I have a template dgnws file for when the client doesn't include one. Whenever you get a dgnws template from the client be sure to open it and do a file disassociateworkset. If you don't ORD crashes when it right after it creates the dgnws. (at least in a PW managed workspace, not sure about outside). Actually I do a file disassociateworkset on ALL their files with the batch processor.