Quantcast
Channel: Andrew Bell's Communities Activities
Viewing all 5174 articles
Browse latest View live

MICROSTATION-HATCH PATTERN

$
0
0

Hello,

I am using Microstation v8i SS2.

I have created some hatch patterns as shown in the attached screen shot.  However, the vertical line dividing the two patterns is not coming in with the hatch pattern.  How do I get the vertical line to appear as part of my hatch pattern?


MicroStation CONNECT Edition System Requirements

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):CONNECT
 Environment: N\A
 Area: Hardware
 Subarea: N\A
 Original Author:Yvonne Lohse, Bentley Technical Support Group
  

NOTE: This is accurate as of the date it was published. Advancements in technology may supersede what is identified below. Please refer to this article's history for changes and updates.

Overview

This document outlines the minimum system configuration for installation and minimum recommended workstation profile for running MicroStationCONNECT Edition.

This information can also be found in the "Readme" file of MicroStation CONNECT Edition, which can be downloaded here: MicroStation CONNECT Edition Readme
or in the installed MicroStation CONNECT Edition by selecting File> Help> Readme.


Installation Requirements

A CD drive or access to the Internet is required for product installation. The minimum system configuration for installation is:

Supported Operating Systems
  • Windows 10 (64-bit) - Home, Pro, Enterprise, and Education
  • Windows 8 (64-bit) - Standard, Pro, and Enterprise
  • Windows 8.1 (64-bit) - Standard, Pro, and Enterprise
  • Windows 7 SP1 (64-bit) - Home Basic, Home Premium, Professional, Enterprise, and Ultimate
  • Windows Server 2008 R2 SP1(64 bit) - Standard and Enterprise
  • Windows Server 2012 (64 bit)
Note: Windows 7 operating system is supported only if you have its service pack (SP1) installed.

Bentley does not support its software running on Microsoft operating systems versions that Microsoft has "retired". For more information see Microsoft's application retirement policy and the Bentley Application Support Lifecycle.

InternetInternet connectivity is required to use some of the features of the product and installation of software pre-requisites, if not already installed on the machine.
Communications Protocols
  • Internet Protocol version 4 (IPv4)
  • Internet Protocol version 6 (IPv6)
Virtualized EnvironmentsCitrix XenApp 6.5 64-bit on Windows Server 2008 R2
Software PrerequisitesThe Prerequisites for Bentley Desktop Applications are automatically downloaded and installed to your workstation while you install MicroStation. The contents of the Prerequisites for Bentley Desktop Applicationsinclude:
  • Microsoft .NET Framework 4.5
  • Microsoft Visual Basic for Applications core
  • Microsoft Visual Basic for Applications localized

Microsoft Internet Explorer, minimum v8.0, recommended v9.0 or later, with 128-bit cipher strength is also required. It is not installed as part of the product pre-requisites.

Copyrights in all components are owned by Microsoft Corporation or one of its affiliates, subsidiaries, or licensors.

Supported DatabasesThe database versions supported by MicroStation are subject to updating after the product release. You can search for MicroStation CONNECT Supported Databases for the latest information.
 


Minimum Profile

The minimum recommended workstation profile for running MicroStationCONNECT Editionis:

ProcessorIntel® or AMD® processor 1.0 GHz or greater. MicroStation is not supported on a CPU that does not support SSE2.
Memory4 GB minimum, 16 GB recommended. More memory almost always improves performance, particularly when working with larger models.
Hard Disk9 GB free disk space (which includes the 5.6 GB install footprint for a complete installation)
VideoSee the graphics card manufacturer for latest information on DirectX drivers. 512 MB of video RAM or higher is recommended. If insufficient video RAM or no graphics card supported by DirectX can be found, MicroStation attempts to use software emulation. For optimal performance, graphics display color depth should be set to 24-bit or higher. When using a color depth setting of 16-bit, some inconsistencies will be noted. For more information on recommended workstation profiles for MicroStation V8i, see MicroStation System Requirements and Hardware Recommendations.
Screen Resolution1024 x 768 or higher.
 

Before You Start

  • When installing or uninstalling this product, you must be logged on with Administrator rights.
  • It is highly recommended that you close any programs and disable any antivirus software that is running prior to the installation of this software. Be sure to turn on your antivirus software when you are finished.
  • MicroStation CONNECT Edition  is designed so it can be installed and safely coexist on the same workstation as an existing MicroStation V8i or MicroStation V8 XM Edition commercial release. It will not attempt to upgrade or uninstall the existing commercial release, and by default it installs its program and configuration files to different locations than the other commercial release. When you install MicroStation CONNECT Edition  it creates the registry entries responsible for file associations. If you do not want this to happen, during installation, in the Select Features to install list, turn off the File Association check box. MicroStation CONNECT Edition  also creates the registry keys for VBA-initiated launching. Windows architecture allows for only one program to own these registry keys and the existing MicroStation V8i or MicroStation V8 XM Edition Commercial Release should continue to function normally by default.
  • If you installed MicroStation V8i and MicroStation CONNECT Edition  on the same workstation and then uninstalled MicroStation V8i, you must run the Repair tool to make sure the registry and file associations are correct. Note: If you used Microsoft's program to uninstall, the Repair tool will work correctly. However, if you used a third-party's product to uninstall, it may have removed files needed by MicroStation. For the procedure to repair MicroStation, refer to the topic To Repair MicroStation.
  • MicroStation CONNECT Edition  will not install if any technology preview (“beta”) release of MicroStation CONNECT Edition  already exists on the machine. You will have to uninstall the technology preview (“beta”) release before installing MicroStation. You should always back up your data prior to installation.
  • When you install MicroStation CONNECT Edition , the following applications are installed with it: 
    - Product Documentation
    - Example WorkSpace
    - Visualization Content
    - CONNECTION client
    - Bentley DGN IFilter
    - Bentley DGN Index Service
    - Bentley DGN Preview Handler
    - Bentley DGN Thumbnail Provider
    - HDR Preview Handler
    - Bentley i-model ODBC Driver
    - Bentley DgnDb i-model Importer 1.5 (64 bit)
  • Examples WorkSpace contains optional downloadable examples, selected to install by default. Unselecting will avoid download of these examples.
  • Visualization content in the form of ready-to-render cell libraries is selected to install by default.
  • The Bentley DGN Reader for Windows 7 is an application that can be downloaded from Bentley iWare section on http://www.bentley.com/en-us/free+software/. When you install this application on your system, the following applications are installed along with it: 
    - Bentley DGN IFilter
    - Bentley DGN Preview Handler
    - Bentley DGN Thumbnail Provider
  • Bentley DGN Thumbnail Provider is required to correctly view DGN thumbnails on the Windows 7, Windows 8, and Windows 10 operating systems. Immediately after installing Bentley DGN Thumbnail Provider, you still may not see the correct thumbnails for DGN files. This will be corrected by rebooting or re-logging onto the system.
  • The Bentley i-model ODBC Driver is used to expose properties in i-models as an ODBC data source. It offers direct access of i-models from ODBC-compatible third-party applications such as Microsoft Office, reporting systems, and Business Intelligence applications. It allows application developers to use familiar tools to access and present i-model data from databases. When the driver is installed, the Bentley i-model ODBC Driver User Manual (Bentley_i-model_ODBC_Driver_User_Manual.pdf) is also installed.
  • Bentley DGN IFilter, Bentley DGN Thumbnail Provider, Bentley DGN Indexer, HDR Preview Handler, Bentley i-model ODBC Driver, and Bentley DgnDb i-model Importer are installed as separate applications. When you uninstall MicroStation CONNECT Edition  (v10.0.0), these applications are not removed. If you do not need them, you will have to uninstall them separately.
 

See Also

MicroStation CONNECT Edition Readme
Making changes to MicroStation CONNECT installation
MicroStation V8i System Requirements and Hardware Recommendations [TN]

MicroStation V8i [FAQ]

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):V8i
 Environment: N/A
 Area: N/A
 Subarea: N/A
 Original Author:Bentley Technical Support Group
  

 

 

 

 

 

 

 

 

Overview

MicroStation V8i is Bentley's latest version of MicroStation and was unveiled and released on November 6th, 2008.

What is new with MicroStation V8i?

There is a product page devoted to MicroStation V8i here.  

For a list of the new items, review the product "readme" document that is delivered with MicroStation.  Click here to view the online readme of the latest version.

Which operating systems are supported by MicroStation V8i (SELECTseries 3)?

See the Installation Requirements section of the Requirements for a list of supported operating systems.

Does MicroStation V8i require a Prerequisite pack?

Yes.  MicroStation V8i requires certain Microsoft resources to be available on the workstation before it can be installed.

"Prerequisites for Bentley Desktop Applications 08.11.xx" is a MicroStation V8i dependency and can be downloaded along with MicroStation V8i on "SELECTservices Online: Downloads/MySELECT CD", here.

Starting with MicroStation V8i SELECT Series 3, a separate perquisite pack is no longer needed.  The installer now checks for what is needed and automatically retrieves it from the web.  A web connection is required. 

Do I need to install the Prerequisites for Bentley Desktop Applications manually before I install MicroStation V8i (SELECTseries 3)?

You have the option of installing the Prerequisites for Bentley Desktop Applications manually prior to installing MicroStation V8i (SELECTseries 3) or you can allow the MicroStation V8i (SELECTseries 3) installer to download and install them during the MicroStation V8i (SELECTseries 3) installation. You can also include the Prerequisites for Bentley Desktop Applications in the deployment image. For more information on creating a deployment image, see the Deployment Guide.

Do I need to uninstall the previous version of MicroStation?

No, if you are using MicroStation V8i SS2 (08.11.09.292) or later.  New versions will prompt you that it will "update" the currently installed version.  However, If you are using an older version of MicroStation V8i, you will be prompted to uninstall.  If you using an older version (Example: MicroStation V8 XM Edition), MicroStation V8i will not attempt to "update" it and can safely co-exist on the same machine (as long as you keep the install location seperate).   

Do I need to install the Prerequisites for Bentley Desktop Applications manually before I install MicroStation V8i (SELECTseries 3)?

You have the option of installing the Prerequisites for Bentley Desktop Applications manually prior to installing MicroStation V8i (SELECTseries 3) or you can allow the MicroStation V8i (SELECTseries 3) installer to download and install them during the MicroStation V8i (SELECTseries 3) installation. You can also include the Prerequisites for Bentley Desktop Applications in the deployment image. For more information on creating a deployment image, see the Deployment Guide

Can I install MicroStation V8i (SELECTseries 3) on the same workstation as MicroStation V8 XM Edition or MicroStation V8i?

You can install MicroStation V8i (SELECTseries 3) on the same workstation as MicroStation V8 XM Edition. The only restriction is that you do not install both versions into the same directory. For information about installing MicroStation V8i (SELECTseries 3) on the same workstation as MicroStation V8i, see "Before you start" in the QuickInstall Guide.

Can I install MicroStation V8i (SELECTseries 3) on the
same workstation as MicroStation V8i (SELECTseries 1) or MicroStation V8i (SELECTseries 2)?

Beginning with MicroStation V8i (SELECTseries 2), the installation behavior was changed to allow only one instance of a major MicroStation release to be installed on a workstation. This was done to facilitate greater flexibility for supporting multiple versions of design applications on each version of MicroStation. This allows you to choose the versions of design applications that can be run on your chosen version of MicroStation. Additional details regarding application compatibility can be found in each application's documentation. 

How do I activate MicroStation V8i (SELECTseries 3)?

Activation can be accomplished during or after the installation process through MicroStation's License Management Tool. You will need two pieces of information in order to complete activation: the name of the SELECTserver and an activation key, which should be available from your system administrator. See MicroStation V8i (SELECTseries 3) Product Activation for more information. 

What is the new activation state for licensing called Evaluation mode?

MicroStation V8i (SELECTseries 3) adds an additional licensing mode for new users to “test drive” our products prior to purchase. Evaluation mode allows full use of the product for up to 30 days. A window will display daily presenting the option to purchase or continue the evaluation. After the evaluation period concludes, the product will not function until it is activated. If you want to purchase a product, contact your account manager or fill out a Sales Contact Request.

How is Clash Resolution in MicroStation V8i (SELECTseries 3) activated and licensed?

Clash Resolution in MicroStation V8i (SELECTseries 3) is initially available running in a pre-activated trial mode. It will run in trial mode for up to 29 days following the first use. To license Clash Resolution you must obtain a ProjectWise Clash Resolution Visa. For more information:

See MicroStation V8i (SELECTseries 3) Product Activation for more information about using the License Management Tool to obtain a visa.

Contact the Bentley Sales Support Center at one of the phone numbers or Web sites listed.

How is Schedule Simulation in MicroStation V8i (SELECTseries 3) activated and licensed?

Schedule Simulation in MicroStation V8i (SELECTseries 3) is initially available running in a pre-activated trial mode. It will run in trial mode for up to 29 days following the first use. To license Schedule Simulation you must obtain a ProjectWise Schedule Simulation Visa. For more information:

See MicroStation V8i (SELECTseries 3) Product Activation for more information about using the License Management Tool to obtain a visa.

Contact the Bentley Sales Support Center at one of the phone numbers or Web sites listed.

Will MicroStation V8i (SELECTseries 3) use my existing commercial MicroStation V8i, MicroStation V8i (SELECTseries 1), or MicroStation V8i (SELECTseries 2) licenses being managed by SELECTserver?

Yes. MicroStation V8i (SELECTseries 3) can be activated using your existing MicroStation V8i, MicroStation V8i (SELECTseries 1), or MicroStation V8i (SELECTseries 2) licenses managed on SELECTserver XM Edition and later. Existing MicroStation V8i, MicroStation V8i (SELECTseries 1), or MicroStation V8i (SELECTseries 2) users who are currently activated will only need to upgrade MicroStation. Since the machine is currently activated, MicroStation V8i (SELECTseries 3) will acknowledge the existing activation and will not need to be re-activated. MicroStation usage, regardless of the version, will be recorded by SELECTserver XM Edition and later.

Will MicroStation V8i (SELECTseries 3) use my existing commercial MicroStation V8 XM Edition licenses being managed by SELECTserver?

Yes. MicroStation V8i (SELECTseries 3) can be activated using your existing MicroStation V8 XM Edition licenses managed on SELECTserver XM Edition and later. Existing MicroStation V8 XM Edition users who are currently activated will only need to upgrade MicroStation. Since the machine is currently activated, MicroStation V8i (SELECTseries 3) will acknowledge the existing activation and will not need to be re-activated. MicroStation usage, regardless of the version, will be recorded by SELECTserver XM Edition and later.

Will MicroStation V8i (SELECTseries 3) use my existing commercial MicroStation V8 XM Edition licenses being managed by SELECTserver 2004 Edition?

No. MicroStation V8i (SELECTseries 3) requires SELECTserver XM Edition or later and will not run with SELECTserver 2004 Edition. Bentley now provides two options for licensing your applications: SELECTserver ONLINE hosted by Bentley, or you may choose to download and deploy SELECTserver at your organization. More information can be found regarding our SELECTserver ONLINE option.

SELECTserver can be obtained from the Downloads/MySELECT CD area of SELECTservices Online. Please note: both SELECTserver ONLINE and SELECTserver require a new license file. Contact the Bentley Sales Support Center
that services your area for information on upgrading your current SELECTserver 2004 Edition license file.

Where can I review the MicroStation V8i  SELECTseries 3) End User Licensing Agreement?

The End User License Agreement is named "EULA.pdf". See the ReadMe for the default location.

Have the hardware requirements for MicroStation V8i (SELECTseries 3) changed from that of MicroStation V8 XM Edition? What are the requirements?

The requirements for MicroStation V8i (SELECTseries 3) have changed slightly from the requirements for MicroStation V8 XM Edition. For details, please see the Minimum Profile section of the MicroStation Requirements, and the MicroStation V8i System Requirements and Hardware Recommendations.

Have the hardware requirements for MicroStation V8i
(SELECTseries 3) changed from that of MicroStation V8i, MicroStation V8i (SELECTseries 1), or MicroStation V8i (SELECTseries 2)? What are the requirements?

The requirements for MicroStation V8i (SELECTseries 3) are the same as the previous editions of MicroStation V8i. For details, please see the Minimum Profile section of the MicroStation Requirements, and the MicroStation V8i System Requirements and Hardware Recommendations.

Will MicroStation V8i (SELECTseries 3) performance be enhanced when running on a 64-bit operating system?

Yes. While MicroStation V8i (SELECTseries 3) is a 32-bit application, it takes advantage of AWE (Address Windowing Extensions) to use the extra memory. When a MicroStation session is running out of memory and has to start swapping, it uses AWE to swap to the extended memory instead of to disk, which can make a significant difference to the performance. An application must have the Lock Pages in Memory privilege to use AWE. In order to obtain this privilege, an administrator must add Lock Pages in Memory to the user’s User Rights Assignments. For more information on how to do this, see “User Rights” in the operating system help.

Additionally, the Luxology rendering engine is delivered in both 64-bit and 32-bit versions. The appropriate version will be installed automatically, depending on the operating System detected during installation. Both the 64-bit and 32-bit
versions will take full advantage of all available memory and processing power available to each operating system.

Will enabling hyper-threading on my workstation have any benefit?

Yes, while early attempts at hyper-threading on single core machines actually degraded MicroStation performance, the new generation of multi-core processors from Intel (Nehalem) actually yield 20% gain in rendering performance. Therefore users with single core processors should make sure hyper-threading is not enabled on their workstation and users with multi-core processors should enable hyper-threading to realize the performance gains.

Will MicroStation V8i (SELECTseries 3) take advantage of multi-core or multi-processor systems?

Yes, MicroStation V8i (SELECTseries 3) takes advantage of multi-core or multi-processor systems. MicroStation V8i
(SELECTseries 3) will perform graphics processing in a separate thread. Some of the functions in MicroStation that take advantage of this technology are:

  • Luxology rendering engine makes very efficient use of multiple cores with no limit on the number of cores or threads, and you will see linear performance gains as more cores are added.
  • QuickVision utilizes the multi-cores and multi-processors but this varies a lot depending on data set, but generally it reduces update time by about one third.  This processing only uses 2 processors. 
  • Some of the Pointools components gets a pretty big boost from using multiple processors.  

What are the benefits of running MicroStation V8i (SELECTseries 3) with a DirectX 11 compatible graphics card?

When running a graphics card that supports either DirectX 10 or DirectX 11, most users will see significant performance gains, particularly with display modes that include transparency, edges, or shadows. We see many examples where complex models displayed in hidden line, illustration, or shaded monochrome mode are 3 to 5 times faster with DirectX 11 than with DirectX 9. Even users that already have DirectX 11 capable hardware or that work with predominantly 2D models can generally boost display performance by upgrading to a faster graphics card. 

Is DirectX 9 and DirectX 10 supported by MicroStation V8i (SELECTseries 3) and will it run on video cards that support DirectX 9 and DirectX 10?

Yes, however, for new purchases, it is recommended that you choose a video card that supports DirectX 11.

Can MicroStation V8i (SELECTseries 3) be deployed in a virtualized environment?

MicroStation V8i (SELECTseries 3) has achieved Citrix Ready Verification and is fully supported operating with Citrix XenApp 5.0 64-bit on Microsoft Windows Server 2008, and Citrix XenApp 6.0 64-bit on Microsoft Windows Server 2008 R2. This will provide IT organizations and administrators more control over software deployments in their organizations. Users will benefit from standardized configurations and less disruptive upgrades.

Additional certifications may be added and supported following the initial commercial release. Please check the BE Communities Web site or contact Bentley Technical Support through the Service Ticket Manager for more information.

Will MicroStation BASIC macros work in MicroStation V8i (SELECTseries 3)?

MicroStation BASIC is supported in MicroStation V8i. However, MicroStation BASIC has not been enhanced and is likely to be unsupported in future versions. Bentley recommends migrating existing MicroStation BASIC code to Visual Basic or Visual Basic for Applications.

Will User Commands still run in MicroStation V8i
(SELECTseries 3)?

User Commands still run in MicroStation V8i (SELECTseries 3), but have been unsupported since the initial release of MicroStation V8i. It is anticipated that this will be the last release of MicroStation that will allow a User Command to run. For assistance on migrating from User Commands please check the BE Communities Web site or contact Bentley SELECT Support through the Service Ticket Manager for more information.

Will existing MDL applications still work in MicroStation V8i (SELECTseries 3)?

Most pure MDL applications that run on MicroStation V8 XM Edition and MicroStation V8i should run on MicroStation V8i (SELECTseries 3) without modification. There are some incompatibilities. These are noted in the MicroStation SDK ReadMe. If the application contains portions written in native code (compiled with Microsoft Visual C++ compiler), then the application should be recompiled with Visual Studio 2005 service pack 1.

Will existing Visual Basic applications still work in
MicroStation V8i (SELECTseries 3)?

Yes.

Which compiler does MicroStation V8i (SELECTseries 3)use?

MicroStation is compiled using Visual Studio 2005 service pack 1. We recommend that applications be compiled using the same compiler.

Can applications compiled with Visual Studio 2008 work in MicroStation V8i (SELECTseries 3)?

Running applications compiled with Visual Studio 2008 is not recommended. This is due to the possible incompatibilities and differences in the C runtime between the Visual Studio 2008 and Visual Studio 2005 compilers. For example, the way memory is allocated and freed can be different. Such issues can make it extremely difficult to debug problems.

Will future versions of MicroStation support  MicroStation Batch Print job set (.job) files?

MicroStation Batch Print will not be supported in future versions of MicroStation. The functionality in MicroStation Batch Print has been replaced by MicroStation Print Organizer. Existing MicroStation Batch Print job set (.job) files can be imported to MicroStation Print Organizer. For more information on MicroStation Print Organizer please refer to the MicroStation help.

What is the "Bentley continuous improvement program?" 

During product activation, you may have seen a new dialog that looks like this:

 

For information regarding the Bentley Continuous Program, click here.

Will future versions of MicroStation support Settings Manager configuration (.stg) files?

MicroStation Settings Manager will not be supported in future versions of MicroStation. The functionality in Settings Manager has been replaced with MicroStation Templates and Tasks. Existing MicroStation Settings Manager configuration files (.stg) can be imported into MicroStation V8i (SELECTseries 3) using the Customize tools. For more information on migrating existing Settings Manager configuration files please refer to the MicroStation help. Click this Blog post for more information.

Will future versions of MicroStation support  MicroStation Archiver (.mar) files?

MicroStation Archiver has been replaced by MicroStation Packager. MicroStation Archiver (.mar) files will not be supported in future versions of MicroStation. Existing MicroStation Archiver files can be extracted in MicroStation V8i (SELECTseries 3) and saved as MicroStation Packager (.pzip) files, when needed. For more information on MicroStation Packager please refer to the MicroStation help. Click this Blog post for more information.

Has the file format changed between MicroStation V8 XM Edition and MicroStation V8i (SELECTseries 3)? Can I use files created in MicroStation V8 XM Edition, MicroStation V8 2004 Edition, or earlier versions of MicroStation V8?

The MicroStation V8 file format is extended by MicroStation V8i (SELECTseries 3) in a backwards compatible way. That means that while there is some new information that is written to the file by MicroStation V8i (SELECTseries 3), that information is ignored by earlier editions of MicroStation V8, and files created and edited with MicroStation V8i (SELECTseries 3) can still be used in earlier versions. For example, MicroStation V8i (SELECTseries 3) allows the display of saved view boundaries. Those will not be displayed in earlier versions, but they will not be damaged either.

Where can I find the list of database versions supported by MicroStation V8i (SELECTseries 3)?

The database versions supported by MicroStation are subject to updating after the product release. You can search for MicroStation database support in Be Communities for the latest information.

Does MicroStation V8i (SELECTseries 3) support LIDAR point cloud data?

Yes, MicroStation V8i (SELECTseries 3) includes the Pointools Vortex™ engine which provides fast, efficient display and manipulation of point cloud data. Please refer to the MicroStation help for additional details.

Why does the ACS Icon face the same direction in all views?

New to MicroStation V8i is the ability to set an Auxiliary coordinate system for each view.  One reason for this change was to provide better control of the drawing planes in any given view.  By default, if a view does not have a specific ACS set, it will reside at the active depth of the view.

If this is not desired, it is possible to return the views ACS's to follow the Global ACS:

  1. Go to the ACS dialog (utilities > Auxiliary coordinates)
  2. Right click on the active ACS and choose "Reset to Global"
  3. Right click again and select "Set All Views"

What happened to the configuration variable MS_LEGACYDRAWORDER?

The variable has been replaced with an option in the Wireframe Display Style (Settings>Display Styles) called "Use File Order for Display". With this change, there is no longer a dependency to a variable to get the desired appearance.  This way you can give the file to someone else and it will always look the same.

Can I change file association for DGN and/or DWG files?

Yes, starting with MicroStation V8i, you can change file associations during the installation process. Select the "Advanced" option to get to the Product Features selection and under "File Association", you can change association of common MicroStation related products.

Alternatively, after installation, you can go back to the Product Features (Start > Settings > Control Panel > Add/Remove Programs > highlight application, select "Change") of the V8i application and remove/add file association.

Note: if you have problems changing file associations, please refer to this technote.

Why does key-in Go=$ report differently?

Starting in MicroStation V8i, the offset location of the Global Origin is now reported relative to Center of Design Plane (XY=0,0,0|uor).  This change was made to provide better information as to exactly where the Global Origin is.

When you key-in: GO=$, you will get the following message in the message center:

The Global Origin is offset Xvalue, Yvalue, Zvalue from the design plane center

Previous to MicroStation V8i, the location was reported from a location equal to the lower left corner of V7's design plane (This location was used in V8 to maintain the same value from V7 format files to V8 format files).  This change will not ettect how coordinate readouts report.

MicroStation crashes when trying to install using a custom path on Windows Vista.

There is a known problem with version 08.11.05.17. It will not install to a custom path from the executable file. The current workaround is:

  1. Execute MicroStation setup file.
  2. Select the option of extract only.
  3. Browse to extracted files and double click MicroStation.msi to install the product, all options should now work properly.

How do I change the default installation path?

The ability to change the installation path is under the Advanced option of the installer.

  1. Launch the MicroStation installation.
  2. Click Next on the first screen.
  3. On the second screen you will see the End-User License Agreement. After checking "I accept the terms in the License Agreement" two buttons should become available, Advanced and Install.
  • If you select Install, MicroStation is installed to the default directory:
            Machines with no prior MicroStation installation:
            MicroStation program directory: C:\Program Files\Bentley\
            MicroStation workspace directory: C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation\
            Machines with prior installation of MicroStation:
            MicroStation program directory: C:\Program Files\Bentley\MicroStation V8i\
            MicroStation workspace directory: C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation\
  • If you select the Advanced option you are given the oportunity to select your own installation path for both the program and the workspace.

Where is the font installer?

The font installer application has been removed from MicroStation V8i. We are currently developing a replacement that will be released as a standalone download. A previous version of MicroStation can be used as a workaround.

It should also be noted that we would like to generally encourage the use of TrueType fonts instead; when released, this updated utility may only be available through support, and may not be integrated into the product again.

How have fonts changed in MicroStation V8i (SELECTseries 3)?

Beginning with MicroStation V8i the MstnFontConfig.xml configuration file is used for the handling of fonts. This file has two sections: language-based font specifications and font details, and can be modified with any text or XML editor. The file is installed in …\Workspace\System\fonts. In addition, there are three new configuration variables for fonts. For more information, see MicroStation Help.

From the table of contents, go to What's New > New in V8i> Text Enhancements > Font Enhancements.

Why aren't my fonts available in the font picker (and other font-related questions)?

See the Fonts In MicroStation Wiki page.

What is an i-Model?  

What are the changes to DWG file format support in MicroStation V8i (SELECTseries 3)?

MicroStation V8i (SELECTseries 3) now includes the Autodesk® RealDWG™ libraries, which provide the highest levels of fidelity possible when working with DWG™ files. Due to this change MicroStation V8i (SELECTseries 3) has the same level of support that all applications based on Autodesk® RealDWG™ libraries will have as a baseline. MicroStation V8i (SELECTseries 3) also provides some unique benefits not available to other Autodesk® RealDWG™-based applications and will provide more in the future.

MicroStation V8i (SELECTseries 3) has these changes regarding DWG format support:

DWG files that are written to or saved by MicroStation V8i (SELECTseries 3) will not display the "Foreign DWG File" message when opened in AutoCAD®.

MicroStation V8i (SELECTseries 3) leverages Autodesk® and other third-party object enablers to display content stored in a DWG file that is created by an application that requires an object enabler. There are two types of object enabler "experiences" in MicroStation V8i (SELECTseries 3), depending on the object enablers that are loaded on the user’s PC.

When using an Autodesk Object Enabler:

Provides graphic display of AEC Objects in MicroStation, AutoCAD, and other RealDWG-based applications that support object enablers.

Is available for AutoCAD® Architecture, AutoCAD MEP, AutoCAD® Civil 3D®, and other Autodesk applications as well as from other third parties.

See the Autodesk web site for more information about its object enablers.

When using a Bentley Enhanced Object Enabler:

Provides graphics display of AEC Objects in MicroStation (like the Autodesk Object Enabler).

Provides a higher level of fidelity for viewing and interrogating AEC Objects when viewed in MicroStation V8i (SELECTseries 3).

The level of information depends on the object enabler, but typically delivers a much better user experience than standard Autodesk Object Enablers.

May include the access to business properties, and object data embedded in the design.

May be created and delivered by Bentley or other third parties that wish to provide a richer experience than an Autodesk Object Enabler may deliver.

The Autodesk RealDWG libraries in MicroStation V8i (SELECTseries 3) provide read-write support for DWG versions R14 through 2012.

Older versions of DWG files are supported for file open and read-only operations with this version of the Autodesk RealDWG libraries.

Older versions of DWG files may be saved as DWG versions R14 through 2010, as well as R12 DXF™.

These parameters are the same for all applications that use this version of Autodesk RealDWG, including AutoCAD.

There are a few capabilities that are available in MicroStation V8i and earlier editions that have not been replaced in MicroStation V8i (SELECTseries 3). They are listed below. Users that require these capabilities and are on SELECT may use the earlier versions for these capabilities if needed.

MicroStation V8i (SELECTseries 3) does not include the DWG Audit utility, but we are investigating the possibility of re-adding it in a future release.

MicroStation V8i (SELECTseries 3) does not include the DWG Recover utility, but we are investigating the possibility of re-adding it in a future release.

Does MicroStation V8i (SELECTseries 3) support versions of DWG prior to 2012?

Yes, it does. MicroStation V8i (SELECTseries 3) opens all DWG versions up to 2012.

Can I install previous versions of the Bentley Autodesk® RealDWG™ with MicroStation V8i (SELECTseries 3)?

Bentley Autodesk® RealDWG™ 2009 is installed as part of MicroStation V8i (SELECTseries 3) along with Bentley Autodesk® RealDWG™ 2014 for backward compatibility reasons. If you need to run a release 2009, 2012, or 2013 object enabler, you may download the object enabler and install it on MicroStation V8i (SELECTseries 3). You then need to set the configuration variable MS_REALDWG_VERSION to 2009, 2012, or 2013 to activate Bentley Autodesk® RealDWG™ 2009, 2012, or 2013 respectively.

If required, you may download and install the previous versions Bentley Autodesk® RealDWG™ 2012 or Bentley Autodesk® RealDWG™ 2013 from the Downloads/MySELECT CD area of SELECTservices Online. You cannot install RealDWG versions prior to 2009.

I have already installed Bentley Autodesk® RealDWG™ 2010 as part of a previous MicroStation V8i (SELECTseries) installation, can I use that?

No, MicroStation (SELECTseries 3) only works with Bentley Autodesk® RealDWG™ 2009, 2012, 2013, or 2014. Your previously installed Bentley Autodesk® RealDWG™ 2010 has no effect on MicroStation V8i (SELECTseries 3) and can be removed.

What should I consider when using file encryption and working with users of previous versions of  MicroStation?

If you are using MicroStation V8i (SELECTseries 3) to encrypt files, users of MicroStation V8i or MicroStation XM Edition will not be able to open the files. If you are using MicroStation V8i (SELECTseries 3) to publish i-models, users of earlier version of MicroStation will be able to open the i-models if you grant them the right to export data. You will not be able to open the i-models if you do not grant the export right.

What are the Bentley iWare Apps for interoperability?

The Bentley iWare Apps for interoperability are Bentley's free software serving infrastructure professionals. The following Bentley iWare Apps for interoperability are installed as part of the MicroStation V8i (SELECTseries 3) installation.

Bentley DGN Reader for Windows 7:

Preview DGNs and i-models and search for embedded information using Windows Explorer or Microsoft Outlook

Preview DGNs and i-models in Windows 7 View thumbnails in Windows applications

Search for text within DGNs and i-models i-model ODBC Driver for Windows 7

Access data within DGN files and i-models

The Bentley iWare Apps for interoperability can also be downloaded from http://www.bentley.com/en-us/free+software/.

What is the Bentley DGN Index Service?

The Bentley DGN Index Service is a shared indexing service that is used by the Project Explorer to retrieve data from DGN files. If enabled, it replaces the harvesting technique from previous versions of Project Explorer. The  performance of the indexing service is much better than the conventional harvesting technique. The Bentley DGN Index Service is installed as part of the MicroStation V8i (SELECTseries 3) installation.

MicroStation V8i SELECTseries 4 English ReadMe

$
0
0

MicroStation V8i SELECTseries 4 English ReadMe

MicroStation V8i SELECT series 4 [FAQ]

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):08.11.09.829
 Environment: N\A
 Area: FAQ
 Subarea: N\A
 Original Author:Bentley Technical Support Group
  

Which operating systems are supported?

  • Windows 10
  • Windows 10 (64-bit)
  • Windows 8.1
  • Windows 8.1 (64-bit)
  • Windows 8
  • Windows 8 (64-bit)
  • Windows 7
  • Windows 7 (64-bit)
  • Windows Server 2008 SP2, Standard and Enterprise editions (64-bit)
  • Windows Server 2008 R2 SP1, Standard and Enterprise editions (64-bit)
  • Windows Server 2012 (64 bit)
  • Windows Server 2012 R2 (64 bit)

Bentley does not support its software running on Microsoft operating systems versions that Microsoft has "retired". For more information on Microsoft's application retirement policy, click here. For similar information on Bentley products, refer to the Bentley Product Support article.

What are the minimum system requirements?

Processor: Intel® or AMD® processor 2.0 GHz or greater. We do not support MicroStation V8i (SELECTseries 4) on a CPU that does not support SSE2.

Memory: 512 MB minimum, 2 GB recommended. More memory almost always improves performance, particularly when working with larger models.

Hard Disk: 8 GB free disk space (which includes the 6.5 GB install footprint for a complete installation)

Video: See the graphics card manufacturer for latest information on DirectX drivers. 256 MB of video RAM or higher is recommended. If insufficient video RAM or no graphics card supported by DirectX can be found, MicroStation attempts to use software emulation. For optimal performance, graphics display color depth should be set to 24-bit or higher. When using a color depth setting of 16-bit, some inconsistencies will be noted. For more information on recommended workstation profiles for MicroStation V8i (SELECTseries 4), see MicroStation V8i System Requirements and Hardware Recommendations

Can I install this version to coexist with another version?

MicroStation V8i (SELECTseries 4) can be installed on the same system as MicroStation V8i (08.11.05.17) and MicroStation V8 XM Edition but will upgrade an existing installation of any of the MicroStation V8i SELECT series 1, 2 or 3 versions.

Are the Prerequisites available as a separate download?

The Prerequisites for Bentley Desktop Applications v08.11.09 are automatically downloaded and installed to your workstation while you install MicroStation V8i (SELECTseries 4). The Prerequisites for Bentley Desktop Applications needs to be installed on your system once, and only needs to be reinstalled if you are installing a later version of MicroStation that requires an updated prerequisite pack. The Prerequisites for Bentley Desktop Applications is also available from the Web downloads/MySELECT CD area of SELECTservices Online. The contents of the Prerequisites for Bentley Desktop Applications include:

Microsoft .NET Framework 4.5.1
Microsoft XML Parser (MSXML) 6 SP 1 (32-bit and 64-bit)
Microsoft Visual Basic for Applications core
Microsoft Visual Basic for Applications localized
DHTML Editing Control for Applications

What versions of Autodesk ® RealDWG™ are supported?

MicroStation V8i (SELECTseries 4) ships with Autodesk ® RealDWG™ 2016 which supports DWG versions 14 – 2016.

Which object enablers are supported?

Any object enablers that are compatible with Autodesk ® RealDWG™ 2016

What is the activation period for MicroStation V8i (SELECTseries 4)?

MicroStation will run without a license for 7 days as an evaluation period.  After being licensed, it must communicate with a license server at least every seven days to continue operation.  In fact, all Bentley desktop products are now standardized on a seven day activation period.  This ensures better, more accurate reporting and helps to make sure a company does not inadvertently exceed their license count.

For those customers running disconnected or mobile solutions the best option for uninterrupted operation is to check out a license.  A checked out license can run up to a year without connecting to a license server.

What is New & Changed in this version?

The following outline identifies new features and enhancements in this release of MicroStation V8i(SELECTseries 4).

For more information about what's new, see "What's New?" > "New in MicroStation V8i (SELECTseries 4)" in the online help. To open the help document in MicroStation select Help > Contents.

  • CONNECTED Users and CONNECTED Projects
    • Assign Projects to CONNECTED Projects
    • Publishing i-models and Printing PDF
  • Data Interoperability
    • Autodesk RealDWG 2016 Support
    • Acute3D File Support
    • IFC Version 4 Support
  • Dynamic Views
    • Create Drawing Dialog Enhancements
    • Plan Callout Enhancements
  • Hatching and Patterning
    • Annotation Scale Setting
  • i-models
    • Publish i-model(s) Dialog Enhancements
  • Printing
    • Support for Sharing Printed PDFs on the Cloud
  • Raster Manager
    • Bing Maps Support
  • RSS Reader 

What is the CONNECTION Client that is installed with this version?

By logging into the Bentley CONNECTION Client using your personal login it provides access to various advantages.

  • A complimentary Bentley Profile 
  • Access to personal LEARN material, paths and history
  • Space on the cloud to share files from desktop to mobile and other users
  • Accurate tracking of time spent against products and projects
  • Timely product related news, automatic product updates and notifications

Further details are provided within the Cloud Services Overview.

See Also

MicroStation V8i (SELECTseries 4) ReadMe

Product TechNotes and FAQs

External Links

Bentley LEARN Server

Comments or Corrections?

Bentley's Product Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section.

For questions or comments unrelated to this article please post a new discussion in this community's forum with a link to this Wiki.

MicroStation V8 XM Edition [FAQ]

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):V8 XM
 Environment: N/A
 Area: FAQ
 Subarea: N/A
 Original Author:Bentley Technical Support Group
  

 

Overview

This FAQ provides answers to frequently asked questions relating to upgrading to MicroStation V8 XM Edition from previous versions of MicroStation.

Have the hardware requirements for MicroStation V8 XM Edition changed from that of MicroStation V8 2004 Edition? What are the requirements?

The requirements for MicroStation V8 XM Edition have changed slightly from the requirements for MicroStation V8 2004 Edition. MicroStation V8 XM Edition requires a minimum of 256MB of RAM, although 512MB is recommended. More memory will almost always improve performance, particularly when working with larger models. It is also recommended that you have a graphics card and driver that supports DirectX 9.0 in order to best take advantage of MicroStation V8 XM Edition's new graphics capabilities. For more on MicroStation V8 XM Edition installation requirements please see the MicroStation V8 XM Edition Requirements. You can also test your workstation to see if it is optimized for MicroStation V8 XM Edition by using the free MicroStation V8 XM Graphics Benchmark application.

What Operating Systems are supported by MicroStation V8 XM Edition?

MicroStation V8 XM Edition supports the following Operating Systems: Microsoft Windows 2000 (SP3), Windows 2000 Server, Windows Server 2003, Windows Server 2003 x64, Windows XP Professional, Windows XP Professional x64 Edition and Windows XP Home Edition.

MicroStation V8 XM Edition will not run on older versions of Windows, including Windows 98 or Windows NT.

What is the MicroStation V8 XM Edition Software Prerequisite Pack and why do I need it?

The MicroStation V8 XM Edition Software Prerequisite Pack is a series of Microsoft packages that must be installed on your workstation prior to the installation of MicroStation V8 XM Edition.

A complete listing of the components of the MicroStation v8 XM Edition Software Prerequisite Pack can be found in the Installation Requirements.

If you are not sure that your workstation has all of these prerequisites, or if they are up to date, it is strongly recommended that you install the software prerequisite pack prior to the installation of MicroStation V8 XM Edition. The MicroStation V8 XM Edition Software Prerequisite Pack needs to be installed on your system once, and only needs to be reinstalled if you are installing a later version of MicroStation that requires an updated prerequisite pack. The MicroStation V8 XM Software Prerequisite Pack is available as a separate download from the Web downloads and MySELECT CD areas of SELECTservices.com.

Will MicroStation V8 XM Edition use my existing commercial MicroStation V8 2004 Edition licenses being managed by Bentley SELECT Server 2004 Edition?

No. MicroStation V8 XM Edition will require Bentley SELECT Server XM Edition and will not run with Bentley SELECT Server 2004 Edition (V8.5.2 and earlier). Bentley SELECT Server XM Edition can be obtained from the Downloads/MySELECT CD area of SELECTservices Online. Please note that you will need to obtain a new license file for Bentley SELECT Server XM Edition. Contact the Bentley Administration Center that services your area for information on upgrading your current Bentley SELECT Server 2004 Edition license file.

Where can I review the MicroStation V8 XM Edition End User Licensing Agreement?

For reference, a copy of the End User License Agreement named "EULA.pdf" is included in the "MicroStation" folder of the product installation. By default, this location is C:\ProgramFiles\Bentley\MicroStation.

Can I install MicroStation V8 XM Edition on the same workstation as MicroStation V8 2004 Edition?

Yes. The only restriction is that you do not install both versions into the same directory.

Has the file format changed between MicroStation V8 2004 Edition and MicroStation V8 XM Edition? Can I use files created in MicroStation V8 XM Edition in MicroStation V8 2004 Edition or earlier versions of MicroStation V8?

The MicroStation V8 file format is extended by MicroStation V8 XM Edition in a backwards compatible way. That means that while there is some new information that is written to the file by MicroStation XM, that information is ignored by earlier editions of MicroStation V8, and files created and edited with MicroStation XM can still be used in earlier versions. For example, MicroStation XM allows gradient fills and transparencies. Those will not be displayed by earlier versions, but they will not be damaged either.

Where can I find my .UPF (User Preference) file?

Data that was previously stored in the \Home directory, is now created dynamically upon MicroStation start-up in a folder created in CSIDL_LOCAL_APPDATA\Bentley\MicroStation\8.9\ (Typically C:\Documents and Settings\*user name*\Local Settings\Application Data\Bentley\MicroStation\8.9\) instead of being installed to C:\Program Files\Bentley\Home\. You can identify the corresponding folder for a particular MicroStation installation by consulting the DirectoryExplanation.txt file that is included in each folder. The DirectoryExplanation.txt file is parallel with the \prefs folder for that particular MicroStation installation. Please note that these files will not be removed with the MicroStation V8 XM Edition uninstall process. MicroStation V8 XM Edition also has a new command line switch that tells it to delete the user preferences file and all other "state" files. To do so, start MicroStation with the command line switch -RestoreDefaults.

Will existing MDL applications still work in MicroStation V8 XM Edition?

Most pure MDL applications that run on MicroStation V8 2004 Edition should run in MicroStation V8 XM Edition without modification. If the application contains portions that are written in native code (compiled with the Microsoft Visual C++ compiler), then those applications should be recompiled using Visual Studio Version 7.1. Generally, recompiling will be straightforward, although some changes might be required if use certain MicroStation API's such as the ability to set a hook function to be called as each element is drawn to the screen.

Will MicroStation BASIC macros work in MicroStation V8 XM Edition?

MicroStation BASIC is supported in MicroStation V8 XM Edition. However, MicroStation BASIC has not been enhanced and is likely to be unsupported in future versions. Bentley recommends migrating existing MicroStation BASIC code to Visual Basic or Visual Basic for Applications.

Where are Drafting Tools?

All the tools that were previously listed under "Drafting tools" in versions prior MicroStation V8 XM Edition, were either moved to another toolbox or were incorporated with other tools.

Place callout Leader, Place Leader, Place Callout Bubble is incorporated as options in the Placed Note tool.

Place Section Marker, Place Title Text, Place Arrow Marker, Place Detail Maker is in the toolbox "Detailing Symbols" (Tools > Annotation > Detailing Symbols).

See Also

MicroStation V8 XM supported databases 

FAQ - MicroStation

MicroStation Wiki

$
0
0

Below is a brief description on each Wiki section:

MicroStation CONNECT Edition Frequently Asked Questions

This is the Wiki where you can find information about the MicroStation CONNECT Edition

Microstation FAQ

This Wiki section contains links to the various MicroStation FAQ pages available for the different versions.

MicroStation Wiki

This is the “general” Wiki for all issues that are not associated with any of the “peer MicroStation Wiki’s”.

MicroStation PowerDraft Wiki

This is the Wiki where you can find information about MicroStation PowerDraft.

Bentley View Wiki

This is the Wiki where you can find information about Bentley View.


Administration Wiki

This is the Wiki for administrators and site managers to get information relating to workspaces, configurations, software distribution, etc.

Annotations Wiki

This is the Wiki for things relating to MicroStation’s text, tag, dimensioning, and detailing subsystems.

FileFormats Wiki

This is the Wiki for things related to Bentley product interoperability with non-DGN format files.

Printing Wiki

This is the Wiki for things related to MicroStation-based printing.

Programming Wiki

This is the Wiki where you can find information about developing with any MicroStation SDK and MicroStation VBA.

Visualization Wiki

This is the Wiki where you can find information about MicroStation Visualization.


Grayed out Cell Library "Create" button

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):V8 2004, XM, V8i
 Environment: N\A
 Area: Cells
 Subarea: N/A
 Original Author:Bentley Technical Support Group
  

Problem

When trying to create a cell the Create button on the Cell Library dialog is greyed out. 
A fence has been placed around the geometry and the cell origin has also been defined.
Why is the Create button still greyed out?

Solution

If a cell library has not been attached to your file then you would not be able to create a new cell.
Check the header of the Cell Library dialog to see if it says Cell Library: [NONE].


If this is the case:

1. Either create a new Cell Library (File > New) or attach an existing Cell Library (File > Attach).

2. The Create button should now be clickable, so you can create a new cell.

See Also

Product TechNotes and FAQs

External Links

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Bentley Connection Client

$
0
0

Whenever I start my computer, I see the Bentley Connection Client...

It always appears, whether or not I intend to use MicroStation CONNECT.

No one has yet explained what that dialog does.  When I sign-in, nothing happens.  If I don't sign-in, nothing happens.  When I dismiss the dialog it hovers around as a background Windows task, hogging 74MByte of memory.

It's an intrusive dialog with no apparent purpose.  It's annoying.  What would happen if I were to uninstall that Bentley client?

Fail to install MicroStation SS4.

$
0
0

I have tried on 2 machines.  1 with Windows 7 and the other with 10.  Both have MicroStation SS3 08.11.09.714 trying to install MicroStation SS4 08.11.09.829.  Both times get an error grading.  Error code is 1639.

Creating Contour Maps

$
0
0

I am attempting to generate contour maps from LiDAR data in Microstation V8i Select Series 4. Currently the process being used is to generate a .tin from a contour map downloaded from a DNR server. The problem with this is the maps are in meters and must be converted to feet, which isn't major, but generating the .tin from contours creates significant inaccuracy. I can use the raw LAS files, bare earth points, DEM, or hillshade files directly from the same server, but I do not know how to generate a .tin from these. Once I have the .tin, I know how to effectively generate contours, I just can't find the step from the other files to .tin. 

Summary:

How can I get from raw LAS, bare earth points, DEM, or hillshade to .tin?

Which of these file types should I use?

Replace Reference File in Multiple Drawings

$
0
0

Hello all,

This is my first time on here and I am in need of a solution to my problem.

Basically I've created approx. 1000 drawings. I want to replace one of the reference files in my drawings with out having to go in my drawings one by one.

Is this possible?

Thanks in advance.

Been away from Microstation since V8 in 2010. Learning V8i by trial and error. Any good tutorials for V8 to V8i? Would like my command window back. Working Units to Drawing Scale? Help please.

Open RSS Reader

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):08.11.09.829
 Environment: N\A
 Area: RSS Feeds
 Subarea: N\A
 Original Author:Leonard Jones, Bentley Technical Support Group
  

Background

Bentley RSS Reader is a feature to MicroStation which gives you the convenience of getting all the updates and news from Bentley product web sites and communities right inside your product with just few clicks.

Open RSS Reader

To load the RSS Reader select Help > RSS Reader

OR

Key-in: BENTLEYRSS OPENREADER

  

See Also


Share my Printed PDFs to the Cloud

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):08.11.09.829
 Environment: N\A
 Area: Printing
 Subarea: N\A
 Original Author:Leonard Jones, Bentley Technical Support Group
  

Share my Printed PDFs to the Cloud

Support for Sharing Printed PDFs on the Cloud has now been added to MicroStation V8i SELECT series 4. You can share your printed PDFs on the cloud. This enables sharing of your published content with other users.

In the Print Dialog, Tick the "Publish PDF to Personal Share" option.

  

File > Print in Print Organizer

See Also

Bentley Cloud Services Overview

Connect - Replace cell loses active level.

$
0
0

Seems like I posted this before but couldn't find it so forgive me if I already logged this.

When doing a global replace of a shared conventional cell using the active cell the cells loose their active level status and revert to level default.  

Both cells, existing and replacement were created on level default and therefore placed on the active level.

Corrections.  These are conventional cells not shared cells.  Share cells retain their level  Conventional ones do not.

Change the backup behavior to save to original DGN file folder

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):08.11.09.459
 Environment: N\A
 Area: Configuration
 Subarea: General
 Original Author:Bentley Technical Support Group
  

Problem

In V7 by default the backup file was saved to the same directory as the original DGN file.

In V8i the application behavior seems different as all DGN files are being backed up into the same folder. Is it possible to change the V8i backup behavior to V7-like? 

Solution

This can be achieved by defining the MS_BACKUP Variable to "$%$(_DGNDIR)'

See Also

Product TechNotes and FAQs

External Links

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

MicroStation CONNECT Edition Configuration Variables

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):10.00.00.25
 Environment: N/A
 Area: Configuration
 Subarea: General
 Original Author:Yvonne Lohse
  

Overview

This technical document provides a description of published configuration variables in MicroStation CONNECT Edition. MicroStation contains various configuration variables that are not identified in this document. Undocumented configuration variables should only be used in very specific situations (i.e. they are not intended for "general use").

Categories:

Cells

Colors

Data Files

Database

Design Applications

Design History

Distributed DGN

DWG/DXF (General)

DWG/DXF (Open-Specific)  ·

DWG/DXF (Close-Specific)  ·

Engineering Links

Extensions

Extensions (JT files)  

File Saving

Geographic Coordinates

Levels

Macro Recorder

Markup

OLE

Operation

Point Cloud

Primary search Paths  ·

Printing

Protection

Raster

Reference

Rendering/Images

Reports

Security

Seed Files

Spelling

Standards Checker

Symbology

System Environment

Tables

Tags

Temp and Backup Files

Translation - CGM

Translation - IGES

Translation - Step

VBA

Uncategorized Configuration Variables

Not listed or undocumented Variables

-

-




bottom

top

Cells

The following table lists the configuration variables that affect cells. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_CELLCell Library DirectoriesSearch path(s) for cell libraries.
MS_CELLLISTCell Library ListList of cell libraries to be searched for cells not found in the current library.
MS_CELLSELECTORDIRCell Selector DirectoryDirectory for Cell Selector button configuration (.csf) files.
MS_CELLSELECTORCell Selector FileDefault Cell Selector button configuration file.
MS_CELLOUTOutput Cell LibrariesDefault directory for newly created cell libraries.
MS_MENUMenu CellsCell library file containing menu cells.
MS_RESOLVESCNAMECONFLICTSShared Cell Name ConflictsControls how shared cell name conflicts are handled for operations like reference merge. If set to 0, there is no resolution. If set to 1, the default, MicroStation resolves the name conflicts on DWG shared cell instances; if set to 2, MicroStation resolves name conflicts for all non-anonymous shared cells.

top

Colors

The following table lists the configuration variables that affect Color. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_DEFCTBLDefault Color TableDefault color table if DGN file has none.
MS_RMENCTBLRight Menu Color TableDefault menu colors (dialogs, borders, etc.) for right screen — specifies a color table (.tbl) file.
MS_LMENCTBLLeft Menu Color TableDefault menu colors (dialogs, borders, etc.) for left screen — specifies a color table (.tbl) file.
MS_COLORBOOK_LIBRARIESColorbook Library ListDisplays the list of DGN files that are used as a source for color books.
MS_SYSTEM_COLORBOOKSSystem Color Books DirectorySets the directory name containing the system color books delivered with MicroStation.

top

Data Files

The following table lists the configuration variables that affect Data Files. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_CUSTOMSHEETSIZEDEFSheet Size DefinitionsDefines the location of the sheetsizes definition file that can be used when creating sheet models.
MS_CUSTOMSCALEDEFScales DefinitionsDefines the location of the scales definition file that can be used when creating models.
MS_CUSTOMUNITDEFUnit Definitions for UpgradingDefines the location of the unit definition file that can be used when upgrading pre-V8 files to V8 DGN files.
MS_HTMLDGNDIRHTML Template DirectoryDirectory containing template DGN files used to generate cell images for HTML documents.
MS_WMS_SERVERS_SEEDSeed file for MS_WMS_SERVERS fileIf the file specified by MS_WMS_SERVERS does not exist, the Map Editor creates it by copying the file specified by this configuration variable.
MS_WMS_SERVERSWeb Map Service ServersLists the servers for the Web Map Service dialogs.
MS_DATETIMEFORMATSStandard Date Time formatsProvides the list of formats available from the Fields Editor for Date/Time fields.
MS_SETTINGSSettings ResourceOpen settings file.
MS_SETTINGSOUTDIRSettings Output DirectoryDirectory for newly created settings files.
MS_SETTINGSDIRSettings DirectoryDirectory containing settings files.
MS_REMAP_CSVFILERemap CSV FileIf this variable points to a remapping comma separated value (CSV) file, the remap filter defaults to that file for the remapping during the Save As operation.
MS_BSILOG_CONFIG_FILELogging config fileLocation of the file that controls and configures diagnostic logging. The default is $(MS_DATA)BSILOG.CONFIG.XML.
MS_BSILOG_ENABLEEnable diagnostic loggingAllows the logging of diagnostic messages.

top

Database

The following table lists the configuration variables that affect database operations. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_UDLDIRUniversal Data Link directoryPoints to the directory that contains the Universal Data Link (UDL) files. The UDL files contain the connection strings to a particular data source.
MS_ORACLE_HOMEOracle HomeUsed to set the path to the Oracle client files required for connecting to the database server. If this variable is not set, MicroStation looks at the system registry and path to determine the Oracle Home directory.
MS_DBASEDatabase FilesSearch path(s) for database files.
MS_SERVERServer LoaderMDL application to load the database interface software.
MS_DBEXTDatabase ServerThe database interface "server" application.
MS_LINKTYPEDatabase LinkagesUser data linkage types recognized by the database interface software.

top

Design Applications

VariableShort nameDescription
MS_DGNAPPSDesign File Applications List of MDL applications to load automatically when a DGN file is opened.

top

Design History

MicroStation includes configuration variables to help set up all aspects of the design history.

The following table lists the configuration variables that affect Design History. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect, unless noted otherwise below.

VariableShort nameDescription
MS_DESIGN_HISTORY_COMMIT_ON_SAVECommit on saveSpecifies whether changes are committed to design history when the file is saved.
MS_DESIGN_HISTORY_COMMIT_ON_CLOSECommit before closeSpecifies whether changes are committed to design history before the file is closed.
MS_DESIGN_HISTORY_COMMIT_ON_MODEL_SWITCHCommit on model switchSpecifies whether changes are committed to design history when the model is switched.
MS_DESIGN_HISTORY_OWNERSHIP_WARNINGConfirm when taking ownershipSpecifies whether you are prompted to confirm that you will take ownership of all uncommitted changes. You must close and restart for this change to take effect.
MS_DESIGN_HISTORY_COLORSColorsSpecifies the symbology to use when identifying changed and unchanged elements. The value must be a list of up to six symbology descriptors, in the following order: added; deleted; changed; pre-changed; conflicts; background. A symbology descriptor is: {color,weight,style,transparency}, where color is a menu color index between 0 and 31, weight is a line weight between 0 and 31, style is a line style index between 0 and 7, and transparency is a value between 0 and 255. Use -1 for each aspect of element symbology that should not be changed. For example, {2,3,1,200}; {4,3,1,200}; {1,3,1,200}; {3,3,1,200}; {6,3,1,200}; {-1,-1,-1,-1} will draw a dotted hallo around affected elements in green, red, blue, cyan, or yellow without changing their symbology. The curly brackets may be omitted if only a color is specified. The default is: 2; 4; 1; 3; 6; 10 which means added elements are drawn in solid green, deleted in red, changed in blue, pre-changed in cyan, conflicts in yellow, and unchanged elements in medium gray.
MS_DESIGN_HISTORY_REVISION_NUMBER_FORMATRevision number display formatAllows you to change the appearance of the revision numbers . You must close and restart for this change to take effect.
MS_DESIGN_HISTORYDesign History capabilitiesAllows users to create, delete, commit, browse, add tags, change descriptions, change authors, combine, retire, set version format, set version, and automatically upgrade design history. You must close and restart for this change to take effect.
MS_DESIGN_HISTORY_COMMIT_DOC_PROPERTIESInclude document properties in design history?If set to 1 (the default), design history tracks changes to document properties such as Title, Author and Comment.

top

Distributed DGN

The following table lists the configuration variables that affect Distributed DGNs. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

Note: These configuration variables take effect only when the product is integrated with ProjectWise with Distributed DGN functionality enabled. Distributed DGN functionality is not available for production workflows.
 
VariableShort nameDescription
MS_DISTRIBUTED_DGN_AUTO_FOCUS_ON_NEW_CONFLICTSShould Conflicts dialog pop up?Specifies whether the Conflicts dialog opens when the Refresh Local Copy command detects a new conflict. The default is on.
MS_DISTRIBUTED_DGN_CONFLICT_BYConflicts scopeSpecifies how conflicts should be detected. MODEL detects conflicts within the same model. GG detects conflicts involving the same graphic group. Default is MODEL.

top

DWG/DXF (General)

MicroStation includes configuration variables to help open, edit, and reference AutoCAD DWG data. The following table lists the configuration variables that affect MicroStation's DWG operations.

Configuration VariableDescription
MS_ACADDIRDefines the directory containing AutoCAD. It is used to find the DWG support files, such as fonts.
When you first load the product, it reads the registry, determines whether AutoCAD or AutoCAD LT is installed on your computer, and if present, sets this configuration variable.
MS_BLOCKLISTDefines the list of DWG and DXF files available for insertion as cells.
You can use this configuration variable when you click on Display All Cells in MS_CELLLIST icon in the Cell Library dialog.
MS_DWG_BACKUPDefines the directory for the DWG backup (.bak) files. If not set, the backup files are placed in the same directory as the DWG file.
MS_DWG_COMMANDPREFIXDefines a character or string of characters that can be used as a shortcut to the AutoCAD key-in commands .
MS_DWG_CREATE_SPACE_FROM_EDFIf set to 1, any empty data field remains as a space.
MS_DWG_FEETUNIT_AS_ARCHENGIf set, when a DGN file with Working Units set to Feet-Inches, Format set to Master Units, and Units on the Save As DWG/DXF Options dialog set to Master Units, the resulting DWG file has Engineering or Architectural units in AutoCAD. (If not set, the units are Decimal or Fractional.)
For details, see Setting units in files that will be saved to DWG files..
MS_DWG_FIELD_2005FORMATTINGIf defined and set to 1, the product only generates field information that AutoCAD 2005 supports.
MS_DWG_LSTYLE_FONTPATHDetermines the location of the font file.
MS_DWG_LSTYLE_FONTNAMEDetermines the name of the font file, and therefore, the name of the font.
MS_DWG_MAX_ORPHANTAGS_PERSETSet the maximum number of tags per tagset for "orphan tags." An orphan tag is an attribute definition that is never instantiated in a block as it should in a DWG file. When opening a DWG file, all such “dangling” attribute definitions are collected into a tagset. For better performance, a tagset should be limited to a manageable size. Therefore, in the case of a large number of dangling attribute definitions, multiple tagsets are preferred rather than one large tagset. The default size is 100 per tagset.
MS_DWG_PGPFILEPoints to a PGP file that contains shortcuts, or aliases, for AutoCAD commands.
MS_DWG_PRE2004_COLOR_TABLESets the color table for DWG files in the product. In version 2004, AutoCAD began displaying indexed colors with a slightly different (generally lighter) colors. The product also uses these new colors unless this variable is set.
MS_DWGAUTOSAVEIf set to a positive number, specifies the number of seconds after the first change to the DWG or DXF file that auto-save occurs. When this time elapses, an Alert window appears that asks whether the changes should be saved. The saving time can be significant, so you can defer the saving by clicking Cancel. If set to zero, no auto-save is done while the file is open. The file is automatically saved on exit or when switching to a different file.
MS_DWGAUTOSAVE_NODIALOGIf set to a positive number, specifies the number of seconds after the first change to the DWG or DXF file that auto-save occurs. When this time elapses the Alert window is skipped and the file change is automatically saved.
MS_DWGDATAPoints to the directory where the following files are stored:
  • DwgSettings.rsc — resource file containing all of the DWG settings
  • Files (*.dws) containing saved settings for opening and saving DWG/DXF files.
  • DwgDisplayColors.tbl (Optional) — A color table that contains the fixed AutoCAD colors used for display to the screen.
  • DwgPlotColors.tbl (Optional) — A color table that contains the fixed AutoCAD colors used for plotting.
MS_DWGFONTPATHDefines the path to AutoCAD *.SHX fonts if AutoCAD is not installed on the system.
By default, the product first uses the value of the MS_ACADDIR configuration variable to find AutoCAD support files. If this is unavailable, the product uses individual variables, such as MS_DWGFONTPATH.
MS_DWGOMITUNIQUEEXTENSIONIf more than one file with the same name is present in the same directory, appends the extension to the output filename when saving the file.
For example, if the directory contains both sample.s01 and sample.s02, then the extension is included in the output filenames (sample_s01.dgn and sample_s02.dgn). If the directory does not include any files with duplicate names, then the extensions are be included in the output names. For example, if the directory contains only file sample.s02, this file is saved to sample.dwg.
MS_DWGPATFILEDefines the full path file name that contains AutoCAD pattern definitions.
MS_DWGREF_ALLOWMASTERCOLORSDefines how the product uses color tables for DWG or DXF files attached as references.
  • If MS_DWGREF_ALLOWMASTERCOLORS is set to 1, the color tables for DWG or DXF references are handled as they are for DGN references: they are controlled by the Use Color Table setting in the Preferences dialog Reference Category (File> Settings> User> Preferences). When Use Color Table is on, the elements in each reference are displayed using the reference's color table. When Use Color Table is off, the elements in each reference are displayed using the active design file's color table.
  • If MS_DWGREF_ALLOWMASTERCOLORS is not set to any value, DWG or DXF references are always displayed using the reference file's color table. In this case, the Use Color Table setting has no effect.
MS_DWGSEEDDefines the DWG seed file used when opening DWG files.
MS_DWGSEED_OVERRIDEDetermines whether a user can modify the DWG Seed File setting on the Save As DWG/DXF Options dialog.
When the variable is not set or set to 0, the first time that the dialog opens, the default DWG seed file is set by the MS_DWGSEED configuration variable. You can choose a different seed file
When the variable is set to 1, You can only use the DWG seed file identified by MS_DWGSEED. You cannot choose a different seed file.
When the variable is set to 2, the default DWG seed file is set by MS_DWGSEED at the beginning of each session. You can choose a different seed file during the session.
MS_DWGSETTINGSFILE

Points to the file that contains the settings for opening and saving DWG files.

MS_DWGSHEETMODELSEEDIdentifies the file containing the seed model for new sheet models in DWG files.
MS_DWGSHEETMODELSEEDNAMEIdentifies the seed model for new sheet models in DWG files.
MS_DWGSYSTEMDATA

Identifies the directory containing the DWG settings file Dwgsettings.rsc. Overrides the directory specified by MS_DWGDATA.
The display and plotting color tables (DwgDisplayColor.tbl and DwgPlotColors.tbl) can also be controlled by placing them in this directory.

MS_MERGE_DISPLAYEDLEVELSONLYModifies Copy Levels During Merge setting on the References tab of the Save As DWG/DXF Options dialog, Save As V8 Options dialog or Saved as V7 Options dialog.
When set (to 1), only those reference levels that are displayed in the selected view are merged into the output file.
If not set, and the Merge Displayed Levels Only setting is off (in the References tab), then all reference levels are merged into the output file.
MS_NO_DWG_BACKUPIf set, backup files (.bak) are not created when you edit a DWG or DXF file.
MS_TRANSEED_OVERRIDEDetermines whether a user can modify the DGN Seed File setting on the DWG Open Options dialog.
When the variable is not set or set to 0, the first time that the dialog opens, the default DGN Seed File is set by the MS_TRANSEED configuration variable. You can choose a different seed file.
When the variable is set to 1, You can only use the DGN seed file identified by MS_TRANSEED. You cannot choose a different seed file.
When the variable is set to 2, the default DGN seed fie is set by MS_TRANSEED at the beginning of each session. You can choose a different seed file during the session.
MS_WORKMODEDefines the workmode as either DGN or DWG.

top

DWG/DXF (Open-Specific)

MicroStation includes configuration variables to open AutoCAD DWG data. Valid values must be entered exactly as shown in the table. For example, “Region” Entity must be entered as a whole string.

Note: Many DWG/DXF open-specific configuration variables have an equivalent setting in the GUI. When set correctly they will override the values in the DWG settings GUI.

Configuration VariableDescription
MS_DWG_ALERT_DEC_FRC_SCI_UNITSWhen a DWG file is opened, an alert dialog opens to warn that Decimal/Fractional/Scientific units are not set to Design Center units. Valid values are ON (or no value) or OFF.
MS_DWG_ALERT_DESIGNCENTER_UNITSWhen a DWG file is opened, an alert dialog opens to warn that Design Center units are not set to a specific unit. Valid values are ON (or no value) or OFF.
MS_DWG_ALERT_ENG_ARCH_UNITSWhen a DWG file is opened, an alert dialog opens to warn that Architectural/Engineering units are not set to Inches. Valid values are ON (or no value) or OFF.
MS_DWG_ARCH_ENG_UNITSSets units to open DWG files that use Architectural or Engineering units. Valid values are:
Master Units
Sub Units
Design Center Units
a unit defined in file units.def
MS_DWG_AXISLOCK_FROM_ORTHOMODEIf DWG ORTHOMODE=1, sets the Axis Lock. Valid values are ON (or no value) or OFF.
MS_DWG_DEC_FRC_SCI_UNITSSets units to open DWG files that use Decimal, Fraction or Scientific units. Valid values are:
Master Units
Sub Units
Design Center Units
a unit defined in file units.def
MS_DWG_DESIGNBACKGROUND_COLORSets the background color for the default design model. Valid values are Red, Green, or Blue, where each of the three color indices is an integer between 0 and 255.
MS_DWG_DESIGNCENTER_UNITSSets units to open DWG files that use Design Center Units. Valid values are:
Master Units
Sub Units
a unit defined in file units.def
MS_DWG_DISCARD_INVALIDIf set, entities that are outside the DGN design plane are discarded and will not be written back to the DWG file on the next file save. If the variable is not set, the product ignores these entities. Typically these entities are not valid and will cause the AutoCAD Zoom Extents tool to perform poorly.
MS_DWG_FOREGROUNDCOLOR255RGBSets the RGB value to display DWG color index 255 as the foreground color, with red, green, and blue values separated by commas. For example, setting MS_DWG_FOREGROUNDCOLOR255RGB=255,255,255 will display DWG index color 255 as white. If this configuration variable is not set, a grayish color is displayed. This is a workaround for DWG's ambiguous index color 255, which serves both as a background color for wipeout fill and as a foreground color for other entities. The foreground definition is remapped by this configuration variable and the RGB value is saved as a named color "DWG Color 255" in a color book called "DWG Special Colors."
MS_DWG_GRAPHIC_GROUP_ATTRIBUTESSets blocks to Graphic Groups, that is, puts shared cell and attached tags into a graphic group. Valid values are ON (or no value) or OFF.
MS_DWG_LINEWEIGHT_MAPPINGMaps DWG line weights to DGN line weights. Valid values are 0=DWG weight1; 1=DWG weight2; 2=DWG weight3; and so forth to 31=DWG weight31, where DWG weights are the DWG line weight values in millimeters, for examples, 0.0, 0.13, 2.11.
MS_DWG_LWDEFAULTControls the width of the default line weight and is analogous to the AutoCAD registry variable LWDEFAULT. The default value is 0 for unweighted default lines. Valid LWDEFAULT values are From AutoCAD Registry, 0.00 mm, 0.05 mm, 0.09 mm, 0.13 mm, 0.15 mm, 0.18 mm, 0.20 mm, 0.25 mm, 0.30 mm, 0.35 mm, 0.40 mm, 0.50 mm, 0.53 mm, 0.60 mm, 0.70 mm, 0.80 mm, 0.90 mm, 1.00 mm, 1.06 mm, 1.20 mm, 1.40 mm, 1.58 mm, 2.00 mm, 2.11 mm. The Line weight index is also a valid alternative, that is, any integer from 0 through 211. A line weight index is an enumeration of line weight defined by DXF Group Code 370.
MS_DWG_MAX_DICTIONARYITEMS(Affects DWG files with many dictionary items.) A dictionary item is non-graphical data stored in the DWG file that often does not impact the visible elements. When opening a file, if the DWG file has a large number of these items, performance can be slow. To speed up the file opening process, you can ignore this items. If you need these dictionary items, you can opt to keep them in spite of poor performance. This variable sets the number of dictionary items you want to keep.
MS_DWG_MODELSPACESets the model space to 2D or 3D. Valid values are 2D or 3D.
MS_DWG_PAPERSPACESets the paper space to 2D or 3D. Valid values are 2D or 3D.
MS_DWG_PROXYSHOWControls the display of proxy objects within a DWG drawing. It is analogous to the AutoCAD registry setting PROXYSHOW. Valid values are:
From AutoCAD Registry
Do Not Show Proxy
Show Proxy Image
Show Proxy Box
An alternative is an integer value such as 0 – do not show graphics, 1 – show graphics, or 2 – show boundary box only. The default setting is 1.
MS_DWG_PROXY_VIEWSets a view to be displayed for a multi-view proxy. Valid values are:
Top
Front
Left
Isometric
MS_DWG_REFERENCE_CONVERTConverts reference files to DWG files. Valid values are ON (or no value) or OFF.
MS_DWG_REFERENCE_COPYLEVELSets the conditions to copy reference levels during merge: only if they are not in the target file, if they are overridden, or always copy. Valid values are If Not Found, If Overrides Exist, or Always.
MS_DWG_REFERENCE_COPYNESTEDCopies live nested reference attachments to the target file when merging. Valid values are ON (or no value) or OFF.
MS_DWG_REFERENCE_EXTERNALSaves external reference file attachments to be an Xref attachment (retained), merged, merged as a block, or omitted. Valid values are:
Retain
Merge
Merge To Cell
Omit
MS_DWG_REFERENCE_MASKEDSaves masked reference file attachments to be an Xref attachment (retained), merged, merged as a block, or omitted. Valid values are:
Retain
Merge
Merge To Cell
Omit
MS_DWG_REFERENCE_MERGE_DISPLAYEDLEVELSONLYMerges reference levels only if they are displayed. Valid values are ON (or no value) or OFF.
MS_DWG_REFERENCE_OPTIMIZEDCLIPOptimizes reference clipping when merged. Valid values are ON (or no value) or OFF.
MS_DWG_REFERENCE_SELFSaves self-referenced file attachments to be an Xref attachment (retained), merged, merged as a block, or omitted. Valid values are:
Retain
Merge
Merge To Cell
Omit
MS_DWG_RENDER_LIGHTSOURCE_OPENSets to use light source for rendering. Valid values are ON (or no value) or OFF.
MS_DWG_RENDER_MATERIAL_OPENSets to use materials for rendering. Valid values are ON (or no value) or OFF.

top

DWG/DXF (Close-Specific)

MicroStation includes configuration variables to save AutoCAD DWG data. Valid values must be entered exactly as shown in the table. For example, “Region” Entity must be entered as a whole string.

Note:Many DWG/DXF save-specific configuration variables have an equivalent setting in the GUI. When set correctly they will override the values in the DWG settings GUI.
 

Configuration VariableDescription
MS_DWG_2D_UNFILLED_3OR4SIDED_SHAPEConverts 2D unfilled triangles and quadrangles to polyline, face, polyface mesh, or region entities. Valid values are:
Face” Entity
Region” Entity
Polyface Mesh
Polyline
MS_DWG_2D_UNFILLED_5ORMORESIDED_SHAPEConverts 2D unfilled polygons to polyline, polyface mesh, or region entities. Valid values are:
Region” Entity
Polyface Mesh
Polyline
MS_DWG_2D_UNFILLED_COMPLEX_SHAPEConverts 2D unfilled complex shapes to polyline, polyface mesh, or region entities. Valid values are:
Region” Entity
Polyface Mesh
Polyline
MS_DWG_2D_UNFILLED_GROUPHOLEConverts 2D unfilled group hole elements to polyface mesh or region entities. Valid values are:
“Region” Entity
Polyface Mesh
MS_DWG_3D_UNFILLED_3OR4SIDED_SHAPEConverts 3D unfilled triangles and quadrangles to polyline, face, polyface mesh, or region entities. Valid values are:
“Face” Entity
“Region” Entity
Polyface Mesh
Polyline
MS_DWG_3D_UNFILLED_5ORMORESIDED_SHAPEConverts 3D unfilled polygons to polyline, polyface mesh, or region entities. Valid values are:
Region” Entity
Polyface Mesh
Polyline
MS_DWG_3D_UNFILLED_COMPLEX_SHAPEConverts 3D unfilled complex shapes to polyline, polyface mesh, or region entities. Valid values are:
Region” Entity
Polyface Mesh
Polyline
MS_DWG_3D_UNFILLED_GROUPHOLEConverts 3D unfilled group hole elements to polyface mesh or region entities. Valid values are:
Region” Entity
Polyface Mesh
MS_DWG_ACS_TO_UCSConverts ACS to UCS. Valid values are ON (or no value) or OFF.
MS_DWG_BLOCKDEF_ON_LAYER0Saves the block definitions on layer “0.” Valid values are ON (or no value) or OFF.
MS_DWG_BLOCKNAMES_FROM_TRIFORMA_PARTSSets the block names from Building parts. Valid values are ON (or no value) or OFF.
MS_DWG_BYBLOCK_COLORSets the block definitions to use the color BYBLOCK. Valid values are ON (or no value) or OFF.
MS_DWG_BYBLOCK_LINETYPESets the block definitions to use line type BYBLOCK. Valid values are ON (or no value) or OFF.
MS_DWG_BYBLOCK_WEIGHTSets the block definitions to use line weight BYBLOCK. Valid values are ON (or no value) or OFF.
MS_DWG_CONSTRUCTION_CLASSSets the elements of the construction class to “Construction” layer, “Defpoints” layer, element’s own layer, invisible, or omits them. Valid values are:
Save To “Construction” Layer
Save To “Defpoints” Layer
Save
Save As Invisible
Omit
MS_DWG_CONVERT_RSC_FONTSConverts and creates SHX files from RSC fonts. Valid values are ON (or no value) or OFF.
MS_DWG_CREATE_SEPARATE_SHEETSWhen a DGN file containing sheet models is saved to DWG, the sheets are usually saved to separate layouts within the DWG file. If this variable is set, the sheets are saved to separate DWG files with the file name created by appending the model name to the original file name. Valid values are ON (or no value) or OFF.
MS_DWG_CURVED_SOLIDSURFACEConverts curved solids and surfaces to wireframe, polyface mesh or ACIS entities. Valid values are:
Wireframe
Polyface Mesh
ACIS Entity
MS_DWG_CURVESConverts curves to spline curves or polyline curves. Valid values are:
Spline Entity
Polyline
MS_DWG_DROP_LABELLINESWhen present, a label line dimension will be dropped to single line text when saved to DWG. By default, a label line will become an mtext. If a label line's text positions are important, dropping them to a single line may be desired. Set this variable to any value to turn it on. It is off by default.
MS_DWG_DROP_UNSUPPORTED_DIMENSIONSDrops dimensions that are not supported by DWG file format. Valid values are ON (or no value) or OFF.
MS_DWG_DROP_UNSUPPORTED_LSDrops line styles that are not supported by DWG file format. The most possible custom line styles DWG format allows are those with characters in them. Any other types are incompatible. Valid values are ON (or no value) or OFF.
MS_DWG_EMPTY_EDF_TO_SPACEConverts blank enter data fields to spaces. Valid values are ON (or no value) or OFF.
MS_DWG_FARREFDEPENDENCYIf set to 0 (the default), DWG named groups work as they do in DWG, that is, elements from a reference file are not supported by group. This is a DWG limitation. If set to 1, you can work around that limitation, that is, elements in reference files can be selected and saved in named groups. However, these groups still will not work in AutoCAD. If these groups and elements are edited in AutoCAD, they may not function anymore when the DWG file is reopened in the product.
MS_DWG_FILE_CODEPAGESets the DWG file codepage. Valid values are 1252 (English) , 1251 (Cyrillic), 1253 (Greek), 1254 (Turkish), 1255 (Hebrew), 1256 (Arabic), 1257 (Baltic), 1258 (Vietnam), 874 (Thai), 932 (Japanese), 936 (Simplified Chinese), 949 (Korean), or 950 (Traditional Chinese).
MS_DWG_FILLED_3OR4SIDED_SHAPEConverts filled triangles and quadrangles to solid, polyface mesh, region or hatch entities. Valid values are:
“Solid” Entity
“Region” Entity
Hatch” Entity
Polyface Mesh
MS_DWG_FILLED_5ORMORESIDED_SHAPEConverts filled polygons to polyface mesh, region or hatch entities. Valid values are:
Region” Entity
“Hatch” Entity
Polyface Mesh
MS_DWG_FILLED_COMPLEX_SHAPEConverts filled complex shapes to polyline, region or hatch entities. Valid values are:
“Region” Entity
Hatch” Entity
Polyline
MS_DWG_FLAT_SOLIDSURFACEConverts flat solids and surfaces to wireframe, polyface mesh or ACIS entities. Valid values are:
Wireframe
Polyface Mesh
ACIS Entity
MS_DWG_FORCE_POSITIVE_ARCSFor arcs, changes clockwise orientation to counter clockwise. Valid values are ON (or no value) or OFF.
MS_DWG_FORCE_ZERO_ZCOORDINATESets the z-coordinate of an element to have a zero value. Valid values are ON (or no value) or OFF.
MS_DWG_INDEXCOLOR_TO_TRUECOLORConverts index color to true color. Valid values are ON (or no value) or OFF.
MS_DWG_LEADER_HOOKLINEIf set, an inline elbow displays on notes that did not have an elbow when first created.
The product allows a note to be placed without an inline elbow (a hook line in AutoCAD) when the inline toggle is unchecked, but AutoCAD does not. This type of note (for instance, a leader without a hook line) saved to DWG will retain correct graphical presentation, and will operate properly in AutoCAD. However, the audit tool will generate an error (annotation ID not null). The audit error can be resolved by setting this configuration variable to 1. However, the original graphical presentation will be lost (the hook line will appear).
MS_DWG_LEVEL_DISPLAYSets the view number from which the level display will be used for the layer’s on/off status. Valid values is a number from 0 through 8.
MS_DWG_LEVELSYMBOLOGY_OVERRIDEOverrides the element symbology from the level symbology. Valid values are ON (or no value) or OFF.
MS_DWG_LINEARPATTERN_CLASSSets the elements of the linear pattern class to “Linear Patterned” layer, “Defpoints” layer, element's own layer, invisible, or omits them. Valid values are:
Save To “Linear Patterned” Layer
Save To “Defpoints” Layer
Save
Save As Invisible
Omit
MS_DWG_LINECODE_SCALEScales the line code. Valid value is a positive real number.
MS_DWG_LOGICALNAME_TO_XREFNAMESaves the reference attachment logical name as the block name of an Xref file. Valid values are ON (or no value) or OFF.
MS_DWG_NONDEF_DESIGNMODEL_ATTACHMENTSMerges the attachments of a non-default design model or merges them as block references. Valid values are:
Merge
Merge To Cell
Omit
MS_DWG_NONDEFAULT_DESIGNMODELSaves non-default design models to separate files, layout models (paper space), or ignore them if their attachments are not merged. Valid values are:
Create Separate Files
Create Paper Space
Ignore If Not Merged
MS_DWG_NONPLANAR_POLYLINESConverts a nearly planar line string to a 2D or 3D polyline. A nearly planar line string is strictly non-planar, but its vertex deviation is small enough to be treated as planar such that it is allowed to become a 2D polyline. Valid values are ON (or no value) or OFF.
MS_DWG_ONE_BLOCK_FOR_DUP_CELLSCreates one block definition for all type-2 cells that are found to be the same. Valid values are ON (or no value) or OFF.
MS_DWG_OVERLAY_FOR_REFERENCESCreates overlays for reference attachments (no live esting). Valid values are ON (or no value) or OFF.
MS_DWG_PATTERN_CLASSSets elements of pattern class to “Pattern” layer, “Defpoints” layer, element's own layer, invisible, or omits them. Valid values are:
Save To “Pattern” Layer
Save To “Defpoints” Layer
Save
Save As Invisible
Omit
MS_DWG_PFACE_MESH_ANGLESets an angular tolerance for polyface mesh conversion. Valid value is a real value in degrees between 0 and 90.
MS_DWG_PLANARPOLYLINESConverts a planar line string to a 2D or 3D polyline. A planar line string has all its vertices lined up to form a unique plane. They do not have to be on an orthogonal plane; they can be on any plane in space. Valid values are:
3D Polyline
Polyline
MS_DWG_REFERENCE_CONVERTConverts reference files to DWG files. Valid values are ON (or no value) or OFF.
MS_DWG_REFERENCE_COPYLEVELSets the conditions to copy reference levels during merge: only if they are not in the target file, if they are overridden, or always copy. Valid values are:
If Not Found
If Overrides Exist
Always
MS_DWG_REFERENCE_COPYNESTEDCopies live nested reference attachments to the target file when merging. Valid values are ON (or no value) or OFF.
MS_DWG_REFERENCE_EXTERNALSaves external reference file attachments to be an Xref attachment (retained), merged, merged as a block, or omitted. Valid values are:
Retain
Merge
Merge To Cell
Omit
MS_DWG_REFERENCE_MASKEDSaves masked reference file attachments to be an Xref attachment (retained), merged, merged as a block, or omitted. Valid values are:
Retain
Merge
Merge To Cell
Omit
MS_DWG_REFERENCE_MERGE_DISPLAYEDLEVELSONLYMerges reference levels only if they are displayed. Valid values are ON (or no value) or OFF.
MS_DWG_REFERENCE_OPTIMIZEDCLIPOptimizes reference clipping when merged. Valid values are ON (or no value) or OFF.
MS_DWG_REFERENCE_SELFSaves self-referenced file attachments to be an Xref attachment (retained), merged, merged as a block, or omitted. Valid values are:
Retain
Merge
Merge To Cell
Omit
MS_DWG_RENDER_LIGHTSOURCE_SAVESaves rendering light sources. Valid values are ON (or no value) or OFF.
MS_DWG_RENDER_MATERIAL_SAVESaves rendering materials. Valid values are ON (or no value) or OFF.
MS_DWG_SAVE_DIMENSION_SETTINGSSaves active dimension settings, such as the one listed as Style-none in dimension style dialog. Valid values are ON (or no value) or OFF.
MS_DWG_SAVE_FILE_SETTINGSSaves file settings such that non-DWG settings can round-trip back. Valid values are ON (or no value) or OFF.
MS_DWG_SAVE_FRONTBACK_CLIPSSaves front-back clippings. Valid values are ON (or no value) or OFF.
MS_DWG_SAVE_REFERENCE_PATHIndicates whether/how to save paths for reference attachments. Valid values are:
When saving to same directory
Relative to Master File
Never
MS_DWG_SAVE_UNITSSets the file units to be saved. Valid values are:
Master Units
Sub Units
Arch./Engineering
a unit defined in file units.def
MS_DWG_SCALE_BLOCKSScales the block definitions. Valid values are ON (or no value) or OFF.
MS_DWG_SHEETBACKGROUND_COLORSets the background color for sheet models. Valid values are Red, Green, Blue, where each of these color values is an integer between 0 and 255.
MS_DWG_SHX_OUTPUT_PATHSets the path to place converted SHX files. Valid value is a path or folder name.
MS_DWG_SOURCEVIEWGROUPUsed to specify a view group name, rather than using the active view group, to save the level display on/off status per view to DWG's global layer display. Because DWG does not support per-view level display, if multiple view groups (for example, the default design model and sheet models) use different per-view level display, only one can be saved as the global layer display for all models.
When this configuration variable is not set, the active view group determines the global layer display status. When it is set with a valid view group name, that view group determines the global layer display status. When it is set with an invalid view group name, the first view group that points to a sheet model in the file determines the global layer display status. This can be useful if you are saving files in a batch, and each file has only one sheet model which is not always the active model.
This configuration variable takes effect only if MS_DWG_LEVEL_DISPLAY is set.
MS_DWG_TEXTSTYLE_NAME_TEMPLATESets a text string template to convert text style name. Valid value is a text string that may contain a place holder %s for the font name.
MS_DWG_VERSIONSets DWG version to be saved. Valid values are 11, 12,13, 14, 2000, 2000i, 2002, 2004, 2005, 2006, 2007, 2008, 2009.
MS_DWG_VPORT_LAYER_FROM_CLIPSets the layer of viewport entity from the clipping element.
Viewport entities are represented as reference attachments in the product – the viewport level is extracted from the reference attachment. If no level is set for the reference attachment then by default the viewport is assigned to layer 0 . However, if this variable is set and a clip element is present, then the viewport layer is extracted from the clip element.
MS_DWG_VPORT_MAP_LOCATE_OFF_TO_LOCKEDIf set, the Display locked status of a viewport entity is mapped to the Locate setting of the reference attachments that represent this viewport. In this case, a viewport with Display locked off will have Locate turned off – and changing the Locate status of the reference attachment will change the Display Locked status of the viewport.
MS_DWG_VPFREEZESets the Viewport Freeze per View Level Display option.
  • 0 - Viewports & Global layers
  • 1 - Viewports Only
  • 2 - Force Global Layer display
MS_DWGINSERTLAYERSpecifies the layer to which normal (unshared) cells and reference attachments are assigned when saving the open DGN file in DWG format. If this configuration variable is not defined, layer 0 is used. Valid values are ON (or no value) and OFF.
MS_DWGSAVEAPPLICATIONDATALinkage data and type 66 application elements can be saved from DGN to DWG. If set, the applications are stored as XRECORDS and the linkages as XDATA. Valid values are ON (or no value) and OFF. The default is off.
MS_DXF_PRECISIONSets the number of decimal places for real numbers when saving file to DXF. Valid value is an integer number between 1 and 16.

top

Engineering Links

MicroStation includes configuration variables to help set up all aspects of the design history.

The following table lists the configuration variables that affect Design History. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_WEBLIB_HISTORYWeblib historyHistory file for the Weblib shared library.
MS_BOOKMARKS_IMAGEImage bookmarksBookmark file for remote images.
MS_BOOKMARKS_RSCResource bookmarksBookmark file for remote resource files.
MS_BOOKMARKS_ARCHIVEArchive bookmarksBookmark file for remote archives.
MS_BOOKMARKS_CELLCell library bookmarksBookmark file for remote cell libraries.
MS_BOOKMARKS_DGNDGN bookmarksBookmark file for remote DGN files.
MS_WEBKIOSKMODEKiosk modeSet to 1 to turn on kiosk mode.
MS_WEBTYPESFILESpecial filetype handlingSpecifies a file that contains special handling instructions for various file types.
MS_WEBFILES_DIRWeblib local storageDirectory in which copies of remote files are stored.
MS_WEBDOWNLOADDIRDownload directorySets the directory in which WWW downloads are stored.
MS_BROWSERMAKECHILDWINDOWReparent browserWhen set to 1, the current browser is reparented inside of the main window, allowing the viewer to always be seen.
MS_USEEXTERNALBROWSERExternal browser nameSets an external browser.

top

Extensions

The following table lists the configuration variables that affect extensions. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableDescription
EC_EXTENSION_ASSEMBLIESUsed for internal implementation. Do not modify.
MS_ACISDirectory containing the ACIS subsystem.
MS_APPSearch path(s) of applications started from “TSK” statements.
MS_BATCHPLT_SPECSSets the location of the batchplt.spc file, which contains the print specifications used by Print Organizer.
MS_BUTTONMENUDefines the file name for the default mouse button menu. The default name is "default.btnmenu" located in the MS_DATA directory. When you create or modify a button menu, the default button menu acts as a seed for modification.
MS_CLRUICULTUREUsed for internal implementation. Do not modify.
MS_CUSTOMIZE_REPORT_STYLESHEETDefines the file name and location for HTML reports on templates and customizations. The default style sheet is named “customizereport.xsl” and is stored in..\Default\Data\folder of MicroStation's program directory.
MS_DATA_PDFL Used for internal implementation only. Do not modify.
MS_DGNTEXTEDITORFAVORITESYMBOLSDefines the file path where the favorite symbol preferences are stored.
MS_DGNTEXTEDITORFAVORITESYMBOLSSEEDDefines the file path that, if exists, and if MS_DGNTEXTEDITORFAVORITESYMBOLS does not, it will be copied once to seed the favorite symbol preferences.
MS_DGNTEXTEDITORPREFDefines the file path where the text editor preferences are stored.
MS_DGNTEXTEDITORPREFSEEDDefines the file path that, if exists, and if MS_DGNTEXTEDITORPREF does not, it will be copied once to seed the text editor preferences.
MS_DOCKINGPREFDefines the location of the file that stores docking preferences such as which dialogs are docked, where they are docked, and the size of the docking areas.
MS_DRAGDROPTYPESDefines location and file name for the file extensions associations. This is accessed through File > Tools > File Associate. The default file name is dragdrop.txt, which will be created in the %LOCALAPPDATA%\Bentley\<product_name>\<product_version>\folder.
MS_ECREPOSITORY_PROPERTYENABLER_SKIPPED_ECSCHEMASUsed to remove certain item types from appearing in the Explorer dialog Items tab and Advanced Search dialog. The list is delimited by semicolons and the ECSchema names must be fully qualified with their version number, for example, “MySchema.01.00;BentleyPlant.05.00”. There is rarely a need for users to change it.
MS_EXPLORERSETTINGSSEEDXML file containing default user Explorer settings. This file is used to define Explorer settings if the file defined by MS_EXPLORER_SETTINGS is not found.
MS_EXPLORER_SETTINGSXML file containing user Explorer settings.
MS_GPSDEVICESSpecifies the GPS devices supported by MicroStation. It should not be changed by users.
MS_GROUPPANELPREFDefines the location of the file that stores the saved state of group panels in various dialogs. These include dialogs such as View Attributes, and stores the open state of the groups, as well as any custom settings that the dialog can associate with the groups.
MS_HANDLER_LOADUsed to control element handlers. This variable should not be changed by users.
MS_KEYPAIRLISTDigital signature KeyPair file list.
MS_LUXOLOGYPoints to the directory where the DLLs related to Luxology are stored.
MS_MDLSTUB_LOADList of MDL Applications that will be stub-loaded, which means their resources are loaded but the code portion of the application is not yet loaded.
MS_POINTCLOUD_APPSLoads any specified MDL applications along with the PointCloud Handler whenever a point cloud is attached in a model. To load the MDL application every time you attach a point cloud, add the name of the MDL application to this variable.
MS_POINTOOLSPoints to the directory where the DLLs related to Pointools are stored.
MS_POSITIONMAPPING_CONFIGURATIONIf set to 1, displays the Position Mapping category in the Preferences dialog.
MS_PROCESSEXCEPTIONLOGMicroStation exception.log and minidump.dmp management.
MS_PRODUCTCODEGUIDUsed for internal implementation. Do not modify.
MS_PROPERTYENABLER_APPSLists the applications to be loaded that are required for displaying properties in the Properties dialog.
MS_PUBLISH_EXTENSIONSASSEMBLIESUsed for internal implementation. Do not modify.
MS_RASTER_DEF_DIRIf absent, there is no Effect.
If present, defines the default directory to which the Attach Raster Reference menu will point to (Default raster file open directory).
MS_REALDWG_APPSLists the adapters for cooperative object enablers that will be loaded into the product when it starts.
MS_SELECTBYDefines the directory for the selectby.rsc file to be written to and read from. The selectby.rsc is used by the Select by Attributes tool to save and retrieve sets of selection criteria. The default setting is MS_SELECTBY=$(_USTN_HOMEROOT).
MS_SELECTSERVICESHOMEURL of Bentley SELECTservices homepage.
MS_SHAREDCONTENTDIRDefines the location of the visualization shared content directory.
MS_SKETCHUP_IMAGEStores the texture images that are embedded in the SketchUp files when the SketchUp file is saved as a DGN file.
MS_SYMBOLPROVIDER_APPSAllows developers to register a managed assembly as an application that provides additional symbols for use in named expressions.
MS_SYSFONTDIRDirectory containing the system fonts.
MS_TASKMAPFILES Used for internal implementation only.
MS_TEMPLATEEXTENDER_APPSUsed to make terrain model properties available in the Element Templates dialog.
MS_XATTRIBUTE_HANDLER_LOADUsed to control terrain model elements. This variable should not be changed by users.
MSDIR_INSTALLEDDirectory where MicroStation is installed. This configuration variable cannot be modified.
PWDIRThis variable appears only if MicroStation is integrated with ProjectWise and it points to the location of the ProjectWise working directory.

top

Extensions (JT files)

The following table lists the configuration variables that appear in the Configuration dialog’s Extensions category only when you have a JT file open.

VariableDescription
JTEXPORT_USING_POINTIf set to -1, selects the Min. Line Length check box. Variable only appears when a JT file has been exported.
TEXPORT_USING_ANGLEIf set to -1, selects the Angle Tolerance check box. Variable only appears when a JT file has been exported.
JTEXPORT_USING_CHORDIf set to -1, selects the Chord Tolerance check box. Variable only appears when a JT file has been exported.
JTEXPORT_NESTING_LEVELUsed to set the Reference Nesting Level. Variable only appears when a JT file has been exported.
JTVERSIONUsed to set the JT version. Variable only appears when a JT file has been exported.
JTEXPORT_BREPBy default, JT Interface exports solid and surface data as a kind of mesh data. If this configuration variable is set, the solids and surfaces are exported as B-rep data. Variable only appears when a JT file has been exported.
JTEXPORT_2D_CURVEIf set to 1, selects the Export 2D Elements check box. Variable only appears when a JT file has been exported.
JTEXPORT_USED_FACETIf set to 1, selects the Use MicroStationFacet check box. Variable only appears when a JT file has been exported.
JTEXPORT_SEWINGIf set to 1, will stitch adjoining Smart Surfaces and reduce the faceting, thus reducing the file size. It is suggested not to use this configuration variable unless the file contains mainly surface geometry, as it can have a lengthy processing time. Variable only appears when a JT file has been exported.
JTEXPORT_SIMPLIFYIf set to 1, will decimate existing meshes, thus reducing the file size. The level of detail will be lower than the original subject, so it is suggested to only use this configuration variable with meshes with very small facets. Variable only appears when a JT file has been exported.
JTEXPORT_BSURFACEIf set to 1, selects the Mesh as Set check box. Variable only appears when a JT file has been exported.
JTEXPORT_WITHOUT_PRIMITIVEIf set to 1, selects the Facet Primitives check box. Variable only appears when a JT file has been exported.
JTEXPORT_WITHOUT_INSTANCEIf set to 1, selects the No Instance check box. Variable only appears when a JT file has been exported.
JTEXPORT_POINT_TOLERANCEUsed to set a value for Min. Line Length. Variable only appears when a JT file has been exported.
JTEXPORT_ANGLE_TOLERANCEUsed to set a value for Angle Tolerance. Variable only appears when a JT file has been exported.
JTEXPORT_CHORD_TOLERANCEUsed to set a value for Chord Tolerance. Variable only appears when a JT file has been exported.

top

File Saving

VariableShort nameDescription
MS_DGNAUTOSAVE Design File Auto-Save If set to 0 or a negative number, auto-save is disabled for all file types. If set to a positive number, auto-save is enabled for all file types. The specified positive number applies when editing V8 format design files. It determines the number of seconds of user inactivity that should elapse before MicroStation auto-saves. 
MS_V7AUTOSAVEV7 Design File Auto-Save If set to a positive number, specifies the number of seconds after the first change to the V7 design file that auto-save occurs. When this time elapses, an Alert window appears that asks you whether the changes should be saved. The saving time can be significant, so you can defer the saving by clicking Cancel in the Alert window. If set to zero, auto-save is not done while the file is open. The file is automatically saved on exit or when switching to a different file.
MS_V7AUTOSAVE_NODIALOG V7 Auto-Save DialogIf set to a positive number, specifies the number of seconds after the first change to the V7 design file that auto-save occurs. When this time elapses the Alert window is skipped and the file change is auto-saved.
MS_V7BACKUPV8 V7 create backup in V8 formatAutomatically creates a backup of a V7 file in the V8 format. If set to true, a file is created in the same directory with the extension .v8.
MS_DWGAUTOSAVE DWG/DXF File Auto-Save See DWG- and DXF-related configuration variables.
MS_DWGAUTOSAVE_NODIALOG DWG/DXF Auto-Save DialogSee DWG- and DXF-related configuration variables.

top

Geographic Coordinates

The following table lists the configuration variables that affect geographic coordinates. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableDescription
MS_GEOCOORDINATE_DATADirectory where MicroStation GeoCoordinate data is installed.
MS_GEOCOORDINATE_FAVORITESFILESDefines the file name and location for quick access to geographic coordinate systems. The contents of this file appear in the Favorites folder on the Select Geographic Coordinate System dialog’s Library tab. You can define multiple files by separating them with semicolons.
MS_GEOCOORDINATE_REFSETTINGSDirectory where MicroStation stores the default reference reprojection settings. There is rarely a need for users to change it.
MS_GEOCOORDINATE_REPROJECTIONSETTINGSDirectory where MicroStation stores the reprojection settings. There is rarely a need for users to change it.
MS_GEOCOORDINATE_USERLIBRARIESThis configuration variable is string of the form “LibraryPath1[ShortName1];LibraryPath2[ShortName2]”, where LibraryPath<n> is the file name of the library, and [ShortName<n>] optionally specifies the identifier that appears in the Select Geographic Coordinate System dialog.
If no directory is specified in LibraryPath, the directory specified by the MS_GEOCOORDINATE_DATA configuration variable is used.

top

Levels

MicroStation includes configuration variables to help set up all aspects of the level system.

The following table lists the configuration variables that affect Levels. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_LEVEL_DISPLAY_FORMATLevel Display FormatSpecifies the formatting that the level name uses when the level lists display, including in PDF plots. If N, the default, the level name is used. If D, the level description is used; if C, the level code is used. More than one value can be specified.
MS_LEVEL_EDIT_NESTED_ATTACHMENT_LEVELSEdit Nested Attachment LevelsIf set, lets you edit the attributes of levels in nested reference attachments.
MS_LEVEL_ALLOW_LIBRARY_LEVEL_EDITEdit Unused Library LevelsAllows you to edit library levels when it is not yet used in master-file. If not set, then a library level can be edited only when if it is used. If set then a library level that is not yet copied into the master-file can be edited. On editing, the library level will be copied into the master-file.
MS_LEVEL_LOAD_ATTACHMENT_FILTERSLoad Attachment Level FiltersIf defined, then level-filters of reference attachments are loaded.
MS_LEVEL_EDIT_ATTRIBUTE_LISTControl Level Attributes EditControls which level attributes can be edited or overridden (instead of using operating system privileges for the entire level library). The attributes to be edited can be one or more of the following as a comma separated list: Override Symbology (OverrideColor, OverrideStyle, OverrideWeight, OverrideMaterial), ByLevel Symbology (ByLevelColor, ByLevelStyle, ByLevelWeight, ByLevelMaterial), GlobalDisplay, GlobalFreeze, DisplayPriority, Transparency, Lock, and Plot. Each attribute accepts a "Library" or "Reference" prefix. Without the prefix, the attribute will be editable for both references and library levels.
MS_LEVEL_SYNC_ATTRIBUTE_LISTControl Level Attributes SynchAffects the DGNLIB UPDATE LEVELS CUSTOM and REFERENCE SYNCHRONIZE LEVELS CUSTOM key-ins. This variable controls the list of level attributes that will sync when any of the above key-ins is executed. The attributes can be one or more of the following as a comma separated list: OverrideSymbology, OverrideColor, OverrideStyle, OverrideWeight, OverrideMaterial, ByLevelSymbology, ByLevelColor, ByLevelStyle, ByLevelWeight, ByLevelMaterial, GlobalDisplay, GlobalFreeze, DisplayPriority, Transparency, Lock, and Plot. Each attribute accepts a "Library" or "Reference" prefix. Without the prefix, the attribute will be editable for both references and library levels.
MS_LEVEL_SYNCH_BYLEVELSynch Symbology to ByLevel on Level ChangeIf set, when you open a different model or view group, the active color, line style, and line weight are set to ByLevel.
The cases in which you open a different model or view group include:
  • opening a different file
  • opening the Models dialog and double-clicking a different model
  • exchanging a reference
  • selecting a different view group from the View Groups window
  • clicking the Previous Model or Next Model icons in the View Groups window
MS_LEVEL_AUTO_SYNC_ATTRIBUTE_LISTLevel Attribute Auto Synch.This variable controls the list of level attributes that will automatically synchronize when a file is opened. The attributes can be one or more of the following as a comma separated list: OverrideSymbology, OverrideColor, OverrideStyle, OverrideWeight, OverrideMaterial, ByLevelSymbology, ByLevelColor, ByLevelStyle, ByLevelWeight, ByLevelMaterial, GlobalDisplay, GlobalFreeze, DisplayPriority, Transparency, Lock, and Plot. Each of the above attributes can take a "Reference" or "Library" prefix. If the prefix is not used, both reference and level library levels will be synchronized.
MS_LEVEL_SEED_LEVEL_NAMESeed Level NameCan be set to the name of a seed level. This can be a level in the master file, or a level in a DGNLib file. If the variable is not set, the default level is the seed level. When a new level is create, it takes the attributes of the seed level.
MS_LEVEL_CREATE_FROM_SEED_ATTRIBUTE_LISTSeed Level Attributes to useControls the set of attributes of the seed level that are copied to the new level. Attributes can be one or more of the following attributes as a comma separated list: OverrideSymbology, OverrideColor, OverrideStyle, OverrideWeight, OverrideMaterial, ByLevelSymbology, ByLevelColor, ByLevelStyle, ByLevelWeight, ByLevelMaterial, GlobalDisplay, GlobalFreeze, DisplayPriority, Transparency, Lock, and Plot.
MS_UPDATE_KEEP_UNUSED_LIBRARY_LEVELSKeep Unused Library LevelsIf not set or set to 0, then unused library levels will be deleted when keying in DGNLIB UPDATE LEVELS. If set to 1, keying in DGNLIB UPDATE LEVELS will not delete all unused library levels. If set to 2, keying in DGNLIB UPDATE LEVELS will delete only unused library levels that are not synchronized with the open DGN file.
MS_LEVEL_PICKER_WIDTHAttributes Level Picker WidthSets the width, in pixels, of the level picker in the Attributes toolbox.
MS_REF_REATTACH_LEVEL_SYNC_ATTRIBUTE_LISTRef. Reattach Level AttributesSpecifies the list of level attributes that will sync when a reference is reattached. The attributes can be one or more of the following as a comma separated list: OverrideSymbology, OverrideColor, OverrideStyle, OverrideWeight, ByLevelSymbology, ByLevelColor, ByLevelStyle, ByLevelWeight, GlobalDisplay, GlobalFreeze, DisplayPriority, Transparency, and Plot.
MS_LEVEL_LIB_DIRLevel Library PathDefines the default directory to look for when exporting levels or importing levels to/from a CSV, DGN, or DGNLib file.
MS_V7TOV8_CSVNAMEV7 to V8 Level CSV FileDefines the .csv file, which controls how levels are mapped when a V7 design file is upgraded to a V8 DGN file.
MS_V7_LEVEL_NAME_PREFIXV7 to V8 Level Name PrefixDefines the prefix to apply to unnamed levels when a V7 design file is upgraded to a V8 DGN file.
MS_V7TOV8_DELETE_UNUSED_LEVELSV7 to V8 Delete Unused LevelsIf set to 1, then all unused levels are deleted when a V7 design file is upgraded to a V8 DGN file. This variable is ignored if the V7 to V8 Level CSV File variable is set.

top

Macro Recorder

The following table lists the configuration variablesthat affect the Bentley Macro Recorder. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_MACROMacrosDefines the search path for macros.
MS_MACRONEWFILEDIRECTORYMacrosDefines the default path where new macros will be saved.

top

Markup

There are configuration variables available to specify markup-related directory paths, page layout and resolution.

VariableShort NameDescription
MS_MARKUP_HIDE_AUDIT_COMMENTSHide Markup Audit CommentsWhen set to True, audit comments do not display in the Comment section of the Markups dialog. However, user comments continue to display.
MS_MARKUPVIEWRESOLUTIONMarkup View ResolutionSets the resolution of the Markup View window, which is used to view a markup. Resolution can be set between 200 and 1200; default is 500.
MS_MARKUPSHEETSEEDNAMEMarkup Template SheetSpecifies the default page layout size. The default is Letter (Landscape).
MS_MARKUPSHEETSEEDMarkup Template FileSets the directory path for the location of the template file (Page Layout File) when creating markup sheets.
MS_MARKUPSETTINGSMarkup Customization SettingsSets the location of the file that controls the settings for markups. The default is $(MS_DATA)MarkupConfig.XML.
MS_MARKUPPATHMarkup PathSets the directory path for the location where the markups are saved.

top

OLE

VariableShort nameDescription
MS_OLE_RETAIN_CONTROL_SIZERetain display size of objectIf set to 1, the display size of the OLE object is retained. If set to 0 or not set (the default), the OLE object is resized according to the size reported by OLE server.
MS_OLESERVE_EMBED_REFFILESEmbed ReferencesIf set, references are embedded along with the master DGN file.

top

Operation

The following table lists the configuration variables that affect Operation. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_APPMENApplication MenusLocation of application and sidebar menus.
MS_AUTORESTORESTATUSBARAuto-restore Status BarIf set to 1, the status bar is restored to its default appearance whenever the pointer is moved within.
MS_AUTOUPDATETEXTITEMSSLOWERAutoUpdate speed for Text itemsSlows down the AutoUpdate timer for text items. If set to 1, and if MS_AUTOUPDATETEXTITEMSSUPPORT is set to 1, text items are automatically synchronized with their values at a slower rate.
MS_AUTOUPDATETEXTITEMSSUPPORTAutoUpdate feature for Text itemsTurns the AutoUpdate feature on for text items on those dialogs and tool settings that want this feature. "Text items" are text controls or text input fields on dialogs and tool settings windows. If set to 1, text items are automatically synchronized with their values without focusing out. For example, while placing a circle, in the Place Circle tool settings window, if you enter a value in the Diameter text field, the cursor displays the circle with that diameter. If you change the diameter in the text field, the size of the circle changes to the new value automatically.
MS_COMMONITEMDIALOGCommon Item Dialog from MicrosoftBy default, the newer Common Item Dialog from Microsoft is used for most file open/save dialogs. If the older Microsoft file dialogs are preferred at all times, set this variable to 0.
MS_COMPRESS_OPTIONSCompress Options SelectionsSpecifies file compression options. If set, the specified options override the selections in the Compress Options dialog.
MS_CURSORPROMPTCursor PromptIf set to 1, displays a Cursor Prompt window that follows the mouse. The cursor prompt shows the message displayed in the lower left field of the Status Bar. It guides you step by step as you perform an operation with a tool.
MS_DEFAULT_MAINTASKPATHDefault Main TaskOverrides the default Main task. The Main task is now driven by 'Main Task' definitions in DGNLIB's. To upgrade, migrate your existing toolbox definition to a Main task, and set this configuration appropriately.
MS_DISABLE_FILE_ICONSDisable File Open IconsIf set, the Show File Icons check box is not shown in the File Open, New, and Open dialogs. Also, the setting is turned off thereby preventing the display of file list icons. The effect is not evident until you restart MicroStation.
MS_DISABLE_FILE_THUMBNAILDisable File Open ThumbnailIf set, thumbnail images of files are not displayed in the File Open and Open dialogs.
MS_FILEHISTORYFile HistoryIf set, MicroStation saves the last four files and directories for each file type.
MS_FKEYMNUFunction Key MenuDefines the file name for the default function key menu. The default name is "funckey.mnu" located in the MS_DATA directory. When you create or modify a function key menu, the default function key menu acts as a seed for modification.
MS_FULLPATHINTITLEBARFull Path in Title BarIf set, the full file specification of the open file, including path, is displayed in the MicroStation application window title bar.
MS_GRAYGROUPHEADERBACKGROUNDGray Color for Group HeadersBy default, the background color of selected Group Headers is blue. "Group Headers" are headers of groups/sections in dialogs like Explorer dialog and Properties dialog. If set to 1, a gray color is used.
MS_GROUPPOPUPFADEKEYTIPSRibbon Group Popup Fade KeyTipsNot used.
MS_GROUPPOPUPFALLBACKWORKFLOW_2DFall-back Workflow for pop-up group processing.Defines the workflow to use when the pop-up group path starts with a "*" and the active workflow does not contain the specified group and the active model is 2D.
MS_GROUPPOPUPFALLBACKWORKFLOW_3DFall-back Workflow for pop-up group processing.Defines the workflow to use when the pop-up group path starts with a "*" and the active workflow does not contain the specified group and the active model is to be treated as 3D.
MS_IDLETIMEOUTExit MicroStation When IdleIf set, specifies the number of minutes of inactivity to wait before exiting an active session of MicroStation. (“Active session” means that a DGN file is open.) The minimum value is 30 minutes.
MS_IMMEDIATEUPDATEWindow Immediate UpdateIf set, view windows will immediately update when other windows are moved or resized over them.
MS_INPUT_CONFIGXMLDefault Touch Gesture ConfigurationDirectory containing the inputconfiguration.xml file, which is used to store gesture assignments.
MS_KEYBOARDSHORTCUTSUser Keyboard ShortcutsXML file containing user keyboard shortcuts.
MS_KEYBOARDSHORTCUTSEXPANDKeyboard Shortcuts User OrderIf set to 1, the parent nodes will be expanded when the Keyboard Shortcuts dialog is opened. A value of 0 is the default.
MS_KEYBOARDSHORTCUTSSEEDDefault Keyboard ShortcutsXML file containing default keyboard shortcuts. This file is used to define keyboard shortcuts if the file defined by MS_KEYBOARDSHORTCUTS is not found.
MS_KEYBOARDSHORTCUTSUSERORDERKeyboard Shortcuts User OrderIf set to 1 (the default), the order of the Keyboard Shortcuts in the menu will be the order set by the user.
MS_LEGACYTOOLMAPLISTPath to files that contain Tool Mapping dataDefines list of Tool Map XML files that specify mapping of tools from MicroStationV8i to the current version.
MS_LIBRARY_SAVEDVIEW_FILTERSaved Views Library FilterSpecifies a set of saved views to exclude from the user interface. The filter is applied only to views found in libraries. For filter syntax and string expressions, see Defining and Deleting Filters.
MS_MAINMENUDOCKINGBESIDEAllow Docking Beside Main MenuIf set to 0 or not set (default), the main menu bar spans the entire width of the application window. If set to a value other than zero, toolboxes and dockable dialogs can be docked along the main menu bar.
MS_NO_VIEW_ANIMATIONDisable Tile/Cascade AnimationIf on, the animation of view tile and cascade is disabled.
MS_OPENDWGAECOpen DWG AEC filesControls the behavior when opening DWG AEC files of an older version:
  • Value = 1 - The file is opened for editing and the AEC objects are upgraded to the current version.
  • Value = 2 - The file is opened as read-only.
  • Value = null - If not set at all or set to any other value, the Alert window opens.
MS_OPENV7Open V7 FilesControls MicroStation's behavior when opening V7-format design files. If not set or set to 0, the file opens with an alert dialog that provides an option to upgrade the file to V8 DGN format. If set to 1, the file is upgraded to V8 DGN format and opened. If set to 2, the file is opened in read-only mode. If set to 3, the file is opened in V7 workmode.
MS_POPUPDIALOGCLOSEDELAYPopup Dialog Close DelaySpecifies the time, in milliseconds, to wait before closing a pop-up dialog. The valid range is 0-120 (0-2 seconds). The default value is 30 (0.5 seconds).
MS_READONLYRead OnlyIf set, the active DGN file is read-only.
MS_RIBBONCOMPONENTPROVIDERSRibbon Component Providers AddIn ListList of managed addins that provide their own ribbon content. For example, Baseribbon.cfg file contains an entry for Bentley.Macros.UI.dll. Adding this provides support for the "Macros" ribbon group.
MS_RIBBONDIRBase Path for Ribbon DefinitionsBase path where ribbon definitions are located. This path is not used directly but is typically used to define MS_RIBBONRSC, MS_RIBBONXML.
MS_RIBBONPREFSRibbon Preferences FileSpecifies the name of the file containing the current state of the ribbon, such as the active workflow, active tab, and setting for ribbon search.
MS_RIBBONPREFSSEEDRibbon Preferences Seed FileSpecifies the seed file for the ribbon preferences file, if not defined for MS_RIBBONPREFS. The file specified by MS_RIBBONPREFSSEED is only used to create the file specified by MS_RIBBONPREFS when that file is not present. This typically only happens when the product is first loaded or when a user has used the command line option -restoredefaults.
MS_RIBBONRSCLISTRibbon Resource File ListSpecifies a list of RSC files containing ribbon components definitions.
MS_RIBBONXMLRibbon XML File ListSpecifies a list of XML files containing ribbon components definitions.
MS_RIBBON_MAXBUTTONLABELCHARSMaximum characters for a ribbon labelSpecifies the maximum number of characters to display for a ribbon button label. If not set, the default value is 24. The minimum value is 20. The maximum value is 128.
MS_RIBBON_NUMEXPANDEDTASKGROUPSNumber of Expanded groups on Active Task tabSpecifies the number of expanded groups in a task tab. Once this limit is hit then all other tasks are placed in an Overflow group.
MS_SAVEMENUAttached MenusFile containing information about attached menus.
MS_SOURCENAME_PROPERTYSave the SOURCE file propertyIf set, the SOURCE file property can be set to the name of the source file. By default, only the name and extension of the source file are saved. Set to 0 to disable the SOURCE property. Set to FULL to save the full path of the source file.
MS_TOOLSETTINGSIGNORETITLEFORWIDTHTool Settings Ignore Title when Determining WidthIs set to 1, the title of the tool settings is ignored when determining the width of the tool settings window.
MS_UPDATESPLITBUTTONLABELTOSELECTEDUpdate Split Button Label to SelectedIf set to 1, enables updating the label of a split button to match the selected child item. By default, only the image and tooltip are updated. If this option is enabled, the split button, as well as the ribbon groups, will grow and shrink based on the size of the label.
MS_VIEWAUTORESIZEView Resize BehaviorIf set to 1, the view windows are resized proportionally when the main window is resized or when the dialogs are docked or undocked.
If set to 0, the view window resizes only when the main window border encroaches the view window border.
MS_VIEWTOOLBOX2DView window toolbox for 2DOverrides for the View window toolboxes for 2D. The value can be the title of a system toolbox or user-defined toolbox.
MS_VIEWTOOLBOX3DView window toolbox for 3DOverrides for the View window toolboxes for 3D. The value can be the title of a system toolbox or user-defined toolbox.
MS_WORKMODEWork ModeWorkmode activates/disables certain functions in order to produce a more compatible design at the end. Setting this variable to DWG will disable some creation tools that may result in elements that are incompatible with the DWG file format. Setting it to DGN (default) will gain full functional capacity in creating elements. You must restart MicroStation to see the effect of a changed value.
MS_WORKSPACEOPTSWorkspace Options(Applicable only to the old File Open dialog (MicroStation Manager)) If set to 0 (default), the Workspace options are displayed on the File Open dialog. If set to 1, the Workspace options are displayed but disabled. If set to 2, the Workspace options are hidden and the dialog box is resized.

top

Point Cloud

VariableShort nameDescription
MS_POINTCLOUD_LAS_NBIT_COLORPoint Cloud LAS File Color treatment If defined and set to 8, will treat color as 8 bits. If set to 16, will treat color as 16 bits
If undefined or set to any other value; will try to auto detect number of bits per color channel. 

top

Primary search Paths

The following table lists the configuration variables that affect Primary Search Paths. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
DWGRDL_DIRDWG Redline LocationLocation and/or extension of the DWG redline file. Defaults to the name of the open DWG file with “_redline” inserted before “.dwg.” in the same directory as the open DWG file.
MS_ADDINPATHAddInsSearch path for managed AddIn assemblies that are used outside of MicroStation's application base or configured privatePath.
MS_ADDIN_DEPENDENCYPATHAddIn DependenciesSearch path for managed assemblies that are used by AddIns outside of MicroStation's application base or configured privatePath. Directories should not be listed here and in MS_ADDINPATH.
MS_DEFDesign FilesSearch path(s) for DGN files.
MS_DGNLIBLISTDGN Library ListList of DGN library files that are used to find Levels, Line Styles, Text Styles, Dimension Styles, Multiline Styles, Element Templates, Text Favorites, Table Styles, Report Definitions, Drawing Seeds, Drawing Boundaries, Display Styles, Display Rules, Page Layouts, Saved Views, and Item Types for your current session.
MS_DGNLIBLIST_LINKSDGN Library ListList of DGN library files that are used to find Sheet Indexes and Link Sets for your current session.
MS_DGNLIBLIST_PRINTINGDGN Library ListList of DGN library files that are used to find Print Styles for your current session.
MS_DGNLIBLIST_RENDERDGN Library ListList of DGN library files that are used to find Rendering Setups, Materials, and Lights for your current session.
MS_DISPLAYSTYLE_LIBLISTDisplay Style Library Include FilterSearch path for library files to list display styles. This configuration variable should point only to those files that are specified in the MS_DGNLIBLIST configuration variable. If this configuration variable is not defined, the display styles in all the files pointed by MS_DGNLIBLIST are listed.
MS_ECFRAMEWORK_SCHEMASECSchema Search PathStores list of directories in which MicroStation searches for EC Schemas. This variable should not be changed by users.
MS_FILTER_LIB_DIRFilter Library PathDirectory containing filter data files.
MS_GUIDGNLIBLISTUser Interface DGN Library ListDirectories containing DGN library files that store tool, toolbox, task, menu, and icon customizations.
MS_ICONLIBRARYLISTIcon Library ListDirectories containing .dll files for icons.
MS_ICONPATHIcon PathDirectories containing files for icons.
MS_ICONRSCLISTIcon Resource File ListDirectories containing .rsc files for icons.
MS_LIBRARY_PATHLibrary PathSearch path for dynamic link libraries.
MS_LINFILELISTLIN File PathDirectory containing linestyle files.
MS_MDLMDL ApplicationsSearch path(s) for MDL applications or external programs loaded by MDL applications.
MS_MDLAPPSVisible MDL ApplicationsSearch path(s) for MDL applications displayed in the Applications dialog.
MS_PERSONALDGNLIBUsers Personal DGNLibSearch path for DGNLib files that store ribbon customizations.
MS_RFDIRReferencesSearch path(s) for references.
MS_RSRCPATHResource FilesSearch path(s) for resource files loaded by MDL applications.
MS_SAVEDVIEW_EXCLUDELIBSSaved Views Library Exclude FilterThe saved views in the library files pointed by this configuration variable are not displayed in the Saved Views dialog. This configuration variable should point only to those files that are specified in the MS_DGNLIBLIST configuration variable. If this configuration variable is not defined, the saved views of all the files pointed by MS_DGNLIBLIST are displayed in the Saved Views dialog.
MS_SEED_LINKSET_PATHLink Set Seed File PathSearch path for seed link set file.
RDL_DIRRedline LocationLocation and/or extension of the redline file. Defaults to the name of the open DGN file but with the suffix “.rdl,” instead of “.dgn,” in the same directory as the open DGN file.

top

Printing

MicroStation includes configuration variables to help set up all aspects of the printing process.

The following table lists the configuration variables that affect the printing operations. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_PLTCFG_PATHPrinter Driver Config PathSpecifies the search path for printer driver configuration (.pltcfg or .plt) files. This path is also used to locate dependent files such as PostScript prolog files, which are no longer constrained to the same directory as the selected .pltcfg or .plt files. They can be stored anywhere in MS_PLTCFG_PATH. If the MS_PLTCFG_PATH configuration variable is defined, the first directory in its value is used as the initial directory in the Select Printer Driver Configuration File dialog. Otherwise, the most recently used directory for printer driver configuration files is used.
MS_DEFAULT_PLTCFG_FILEDefault Printer ConfigurationName of printer driver configuration (.pltcfg or .plt) file that loads, rather than last one used. This variable replaces the old variable MS_PLOTDLG_DEF_PLTFILE. The old variable is still honored if MS_DEFAULT_PLTCFG_FILE is not defined.
MS_PLT_SYSPRT_PLTFILEDefault Windows Printer DriverName of printer driver configuration (.pltcfg or .plt) file that is used when Windows driver is selected.
MS_PLT_PDF_PLTFILEDefault PDF Printer NameName of the printer driver configuration (.pltcfg or .plt) file that is used when the PDF driver is selected.
MS_PLT_SYSPRT_DEFAULT_PRINTERDefault Windows Printer NameName of printer that is used when a default system printer opens.
MS_PLT_SYSPRT_DEFAULT_FORMDefault Windows Form NameName of form that is used when a default system printer opens.
MS_PLT_SYSPRT_DEFAULT_TRAYDefault Windows Tray NameName of tray that is used when a default system printer opens.
MS_PLTFILESPrint Output DirectoryThe print output directory specified by this configuration variable is now given priority over the most recently used print output directory. If this configuration variable is defined, the most recently used directory is always ignored when the Print dialog brings up the Save Print As dialog for saving a print output file.
MS_PRINTDEF_PATHPrint Definition Search PathSpecifies the search path for print definition (.pset or .ini) files.
MS_PENTABLEPen Table Search PathSearch path for pen tables.
MS_PENTABLE_EDITORPen Table EditorIf set to HIDE_MENU_ITEM, removes the print dialog Edit Pen Table menu item.
MS_DESIGNSCRIPT_EDITORDesign Script EditorFully qualified name of a text editor to use when the print dialog's Edit Design Script menu item is activated. For example, set the value to "notepad.exe" (without the quote marks) to use the Windows notepad text editor. If this variable is not defined, notepad is used. If set to HIDE_MENU_ITEM, removes the print dialog Edit Design Script menu item.
MS_DESIGNSCRIPT_PATHDesign Script Search PathSearch path for design scripts.
MS_PLT_PREVIEW_USABLEAREACOLORPreview Usable Area ColorSpecifies the color of the usable area rectangle in the preview window.
MS_PLT_PREVIEW_PLOTBOXCOLORPreview Plot Rectangle ColorSpecifies the color of the print bounding box rectangle in the preview window.
MS_PLT_PREVIEW_PLOTFENCECOLORPreview Plot Fence ColorSpecifies the color of the print fence shape in the preview window.
MS_PLTDLG_UNLOADONCLOSEUnload Plot Dialog on CloseControls the load/unload of the Plot dialog on closing.
MS_PLTDLG_CLOSE_AFTER_PLOTClose Print Dialog After PlotIf set to 1, the Print dialog closes automatically after a print job is performed successfully.
MS_PLT_ENABLE_SCALE_CLIPPINGEnable Scale ClippingIf set to 0, does not reduce the plot fence or sheet size to accommodate the specified scale factor.
MS_PLT_ENABLE_PRESERVE_SCALEEnable Preserve ScaleIf set to 0, does not preserve the current plot scale when a new view, fence or paper size is selected.
MS_PLT_ENABLE_AUTO_ROTATEEnable Automatic RotationIf set to 0, does not manipulate the plot rotation in order to achieve the best fit.
MS_PLT_ENABLE_AUTO_ORIENTEnable Automatic OrientationIf set to 0, does not manipulate the paper orientation in order to achieve the best fit.
MS_PLTDLG_AREA_PRIORITYPrint Area PriorityIf set to 1, sheet definitions in the model take priority over the active fence.
MS_PLT_FORM_SCALE_PRIORITYForm Scale PriorityIf set to 1, the default form scale is reapplied whenever the paper size changes.
MS_PLT_SET_LAYOUT_FROM_SHEETHonor Sheet Layout InfoIf set to 0, the Print dialog layout is not automatically set when a sheet definition is loaded and the current print area is Sheet.
MS_PLT_SET_PLOT_STYLE_TABLE_FROM_SHEETHonor Sheet Plot Style TableIf set to 0, plot style tables specified in the sheet definition are not attached to the plot.
MS_PLT_MAX_ON_NEW_AREAMaximize on New Print AreaIf set to 1, the print size is maximized automatically when the print area changes.
MS_PLTDLG_AUTO_FIT_VIEWAutomatically Fit ViewControls the setting for the print area mode.
MS_PLTDLG_SHOW_BASIC_LAYOUT_CONTROLSBasic Layout ControlsIf set to 1, the Print dialog's Rotation field and Mirror option menu are hidden. The orthogonal print Rotation option menu is displayed instead.
MS_PLTDLG_ALLOW_FORM_SIZE_EDITAllow Form Size EditsIf set to 1, the size of the selected form may be modified via the Print dialog.
MS_PLTDLG_SHOW_PRINT_STATUSShow Print Status DialogIf on, a print status dialog opens when a job is being printed. You can cancel the print job.
MS_PLTDLG_THUMBNAIL_PREVIEW_TIMEOUTThumbnail Preview TimeoutControls how long the thumbnail preview in the Print dialog paints before stopping to allow the rest of the dialog to refresh. The default is 10 seconds.
MS_PLTDLG_SHOW_ACCURATE_PREVIEW_ROTATIONPreview Accurate RotationIf set to 1, the Preview dialog displays the plot in its current rotation.
MS_PLTDLG_SET_UNITS_FROM_SHEETSet Units From SheetIf set to 0, the Print dialog's units are not automatically set from the sheet definition when the current print area is Sheet.
MS_PLTDLG_KEEPVIEWFLAGSONFENCECHANGEKeep View Flags on New FenceWhen a new fence is placed, controls the setting for resetting or preserving current print attributes.
MS_PLOTDLG_DEF_PENTABLEDefault Pen TableDefines the default pen table that is loaded.
MS_PLTDLG_SETUPSYSPRT_ENABLE_PRINTEnable Setup Sysprinter PrintControls the print behavior of the Configure Windows Printer icon.
MS_PLTDLG_ENABLE_SAVE_CONFIGEnable Save ConfigurationDisables the Print dialog Save Configuration menu items.
MS_PLTDLG_DISABLE_PREFERENCES_DIALOGDisable Plot Dialog PreferencesIf set to 1, the Preferences menu item is not displayed on the Settings menu.
MS_PLT_SCALE_METHODScale MethodDetermines how the print scale displays in the Print dialog.
MS_PENTABLE_IMPORTEMPTYSECTIONSImport Empty Pen Table SectionDuring AutoCAD plot style table imports, ignores pen table sections that have no effect. If set to 1, empty sections are created.
MS_PENTABLE_DISABLECOLORPen Table Disable ColorControls the color of a disabled section in a pen table; default is medium gray.
MS_PENTABLE_SLOTNUM_MATCH_APPLIES_TO_CHILDPen Table Slot Number MatchControls how the pen table reference slot number match applies to the parent reference and its children.
MS_PENTABLE_SEARCH_LEVEL_LIBRARIESPen Table Search Level LibsIf set to 0, level libraries are not included when searching for level names defined in the pen table.
MS_PENTABLE_IMPORTCTB_NOPENMAPPen Table Import Pen MapsWhen importing CTB files, allows the proper color-to-width resymbolization of multi-colored elements.
MS_PLTFILE_EDITORPrinter Configuration EditorControls which editor is used when you select File> Edit Printer Driver Configuration in the Print dialog.
MS_PLT_INVERT_WHITE_COLORSInvert White-to-Black ColorsAllows you to override the colors that are automatically inverted from white to black.
MS_PLT_ABBREVIATE_BORDER_FILENAMEAbbreviate Border FilenameIf set to 0, the filenames included in the plot border text are not abbreviated.
MS_PLT_AUTOAREA_RESULT_LIMITMaximum print definitionsDefines the maximum number of print definitions to be created when searching for multiple shapes or cells. The default limit is 500.
MS_PLT_UPDATE_FIELDSUpdate Fields when PrintingControls when fields are updated prior to printing or previewing. If set to 0 or undefined, fields are not updated prior to either printing or previewing. If set to 1, fields are updated prior to printing. If set to 2, fields are updated prior to both printing and previewing.
MS_PLT_ENGINE_CMDLINE_ARGS Engine Command-Line ArgumentsSpecifies custom command line arguments used by Print Organizer when invoking its background process. If this variable is undefined and MS_CONFIG is defined, then the background process is invoked with the command line argument -wc"$(MS_CONFIG)"
MS_PLT_ENABLE_VARIABLE_DEFINITION_MODEUse Variable Print DefinitionsIf set to 0, Print Organizer creates fixed print definitions. If set to 1, Print Organizer creates variable print definitions.
MS_PRINTERLIST_SYSPRINTERSPrinter List System PrinterIf set to 0, Windows printer names are not included in the print dialog printer list.
MS_PRINTERLIST_VISIBILITYPrinter List VisibilityControls the behavior of the printer driver configuration file selection list. By default, most .pltcfg files and all .plt files in the MS_PLTCFG_PATH search path are listed. Only .pltcfg files with Visible=0 properties are excluded. The display label property is used to identify .pltcfg files, if defined. Otherwise the file name is used. Legacy .plt files are always identified by file name.
This variable may be used to control the .pltcfg visibility test. For example, a value of '2-4,6' will result in only .pltcfg files with Visible property values of 2,3,4, and 6 to be included in the list. All .plt files are considered to have a Visible property of 1, as are .pltcfg files that do not explicitly define a Visible property.
There are two reserved values:
  • "0": Do not search for printer driver configuration files. Selection can only be performed using a file picker dialog. All files are identified by file name only.
  • "-1": Search for printer driver configuration files, but do not read their Display Label or Visible properties. All files are identified by file name only. This setting may be helpful if the time required to build the list is a concern.
MS_PRINTORGANIZER_OPEN_DGN_READWRITEOpen Designs Read-WriteIf set to 1, the Print Organizer background process opens design files in read-write mode. Certain print workflows may depend on the design file being writeable.

top

Protection

MicroStation includes configuration variablesto help set up all aspects of the file protection.

The following table lists the configuration variables that affect Protection. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_PROTECTION_ENABLEEnable file protection
  • Set to 0 to disable file protection (default)
  • Set to 1 to enable password or certificate protection
  • Set to 2 to enable password protection
  • Set to 3 to enable certificate protection
MS_PROTECTION_V8_COMPATIBILITYLimit encryption strength
  • Set to 0 to use stronger encryption, producing protected files that previous versions cannot open (default)
  • Set to 1 to enable previous versions to open protected files and create licenses
MS_PROTECTION_LICENSE_ENABLEControl license creation
  • Set to 0 to disable license creation
  • Set to 1 to enable password licenses
  • Set to 2 to enable certificate licenses
  • Set to 4 to enable Everyone licenses
  • Set to 7 to enable all types of licenses (default)

Add individual values together to enable two or more license types.

MS_PROTECTION_PASSWORD_MIXEDPassword letters and numbersA password containing a mixture of letters and numbers.
MS_PROTECTION_PASSWORD_MINIMUMMinimum length of passwordSets the minimum length of a file protection password. The default is 5.
MS_PROTECTION_NOENCRYPT_THUMBNAILDo not encrypt file thumbnailThe thumbnail is an image of the last used view of the design file. The image is displayed by Windows File Explorer and File Open dialog.
MS_PROTECTION_NOENCRYPT_PROPERTIESDo not encrypt file propertiesSet to 1, tells the Protect command to leave file properties unencrypted or set to 0 to allow Protect encrypt file properties.

top

Raster

MicroStation includes configuration variablesto help set up all aspects of the rasters.

The following table lists the configuration variables that affect Raster files. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_RASTER_IMG_STRETCHSet contrast stretch filteringSpecifies a contrast stretch filtering to be applied to any Erdas IMG file whose detected pixel type is grayscale 8 bits, RBG 24 bits or RGBA 32 bits. Possible values are as follows :
1 or 0
Where
0 : No contrast stretch is applied.
1 : A contrast stretch filtering is applied before displaying the image.
MS_RASTER_IMG_CHANNELSSet band to channel mapping for IMG file formatSets the band number to use for Red, Green, Blue and Alpha channels when a file whose format is IMG is attached. The ‘0’ value can be set for the Alpha channel if none is required. When this variable is defined, all attached Erdas IMG rasters will use the same band order. The default value is: MS_RASTER_IMG_CHANNELS 1 2 3 4.
MS_RASTER_DISABLE_IPPCONNECTIONDisable default server portIf undefined, the default socket server port 1924 is used.
If defined, the socket port 1924 is ignored.
MS_RASTER_VIEWSAVEASDWGDefine view for DWG file

When exporting to DWG, controls whether the raster is displayed.
If set to 0 or undefined, the raster is displayed in View 1.
If set to 1 to 8, the raster is displayed in the specified view.
If set to 9, the raster is displayed in at least one view.
If set to 10, the raster is displayed in all views.

MS_RASTER_COMMONGEOREFFILEFORMATS Set default 'Common Geo Ref Raster Formats' file filter for the Open dialogSets the extension(s) of the file formats to use as the default "Common Geo Ref Raster Formats" file filter for the Open dialogs. Use a semicolon to separate file extensions. Do not add a semicolon to the end of the list. For example: *.hmr;*.iTiff;*.tiff
MS_RASTER_COMMONFILEFORMATSSet default 'Common Raster Formats' file filter for the Open dialogSets the extension(s) of the file formats to use as the default “Common Raster Formats” file filter for the Open dialogs. Use a semicolon to separate file extensions. Do not add a semicolon to the end of the list. For example: *.hmr;*.iTiff;*.tiff
MS_RASTER_TIFFINVERTInvert monochrome tiffIf defined and set to a non-zero value, inverts the foreground/background color allocation of monochrome tiff files when the raster is attached.
MS_RASTER_SAVEAUTOSet Automatic Save modeEnables Raster Manager Automatic Save mode when closing a DGN or detaching a raster.
If undefined or set to 0, Save Auto is off.
If set to 1, Save Auto is enabled and the user will not be prompted to update the raster for changes made to the location info of the file.
MS_RASTER_NOSHARINGCreating .sharing.tmp filesManages the automatic creation of .sharing.tmp files for concurrent access of the same raster file by various instances of MicroStation. If undefined or set to 0, .sharing.tmp files are generated.
If set to 1, .sharing.tmp file generation is off.
MS_RASTER_NO_DETACH_CONFIRMDisplay alert dialog upon rasterIf set to 0, displays an alert dialog asking to confirm the raster detachment. If undefined or set to 1, does not display the alert dialog.
MS_RASTER_EPSGTABLE_PATHSet path to EPSG tableEnables geotiff positioning using the location parameters found in ASCII files provided on request.
The required ASCII files are:
  • CoordSysData.txt
  • ProjectionData.txt
  • UnitsData.txt

If undefined or set to 0, hard-coded tables are used.
If set to 1, ASCII files are used.

MS_RASTER_DEFAULTSISTERSet default sister fileIf set to 0 or 1, HGR is the default sister file.
If set to 2, WorldFile is the default sister file.
MS_RASTER_DEFAULTSCALESet default scaleIf undefined, or if defined and set to 1, a non-georeferenced raster that is attached without the use of the Place Interactively check box is assigned a scale of 1. The pixel size is derived from the scale and DPI.
If defined and set to a value greater than 1, a non-georeferenced raster that is attached without the use of the Place Interactively check box is assigned a scale equal to the value of MS_RASTER_DEFAULTSCALE. The pixel size is derived from the scale and DPI.
MS_RASTER_1BIT_WORKMODEHarmonize monochrome raster displayIf defined and set to 1, harmonizes monochrome raster display so they are handled like raster reference attachments.
If undefined or set to 0, has no effect.
MS_RASTER_DEFAULT_LEVELSet default display levelDefines the level for raster elements when upgrading to MicroStation V8i. The value is the LevelName.
MS_RASTER_TRANSPARENCYSet transparencyIf defined and set to 1, Raster Manager sets the background transparency value, as specified in the Raster Manager Transparency dialog. Possible values are 0 to 255, where 255 is 100% transparency.
If undefined or set to 0, has no effect.

top

Reference

MicroStation includes configuration variables to help set up all aspects of the references.

The following table lists the configuration variables that affect reference files. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_DISALLOWFULLREFPATHDisallow Full Ref PathIf set, the product does not save the full path to references. By default, the product stores both an abbreviated (portable) path and the full path to references.
MS_NEST_COLORADJUSTMENTNested Reference Color AdjustmentIf set to any value, the nested reference color adjustments at each level are multiplied by this value. If not set, the color adjustment for the top level reference controls the color adjustment for all nested references.
MS_REF_DEFAULTATTACHDIRECTORYDefault Attachment DirectoryIf set, the Attach Reference dialog defaults to this directory, rather than the directory of the last attached reference.
MS_REF_DEFAULTSETTINGSDefault Attachment SettingsControls the default settings for reference attachments. This variable is set to a comma-separated list of key=value pairs — for example: snap=1,locate=0,trueScale=1,scaleLineStyles=0.
Recognized keys and values include: display=0|1, snap=0|1, locate=0|1, treatAsElement=0|1, attachMethod=coincident|world|geoReprojected|geoAECTransform, useLights=0|1, saveRelativePath=0|1, scaleLineStyles=0|1, ignoreWhenNesting=0|1, displayRasterRefs=0|1, displayBoundary=0|1, newLevelDisplay=fromconfig|always|never, nestMode=live|copy|none, nestDepth=<value>,nestOverrides=allow|always|never, useAnnotationScale=0|1, synchWithSavedView=none|volume|allsettings, levelControlDisplay=0|1, plotAs3D=0|1.
Also, to store the complete path to V7 files for newly attached references, set the variable to completepathv7=1.
MS_REF_DONTHILITEFORMANIPHiliting References for Manipulation

By default, the product highlights all elements in a reference file when the reference is manipulated. If this variable is set to any value, this highlighting is disabled. Disabling speeds up the reference manipulations but makes it more difficult to see which references are being manipulated.

MS_REF_ENABLE_LEGACY_VISEDGEEnable Visible Edges "Legacy" OptionIf set to 1, the Legacy option for the reference Visible Edges drop-down is displayed. The Cached option replaces the "Legacy" (True Hidden Line) option and provides superior performance and accuracy.
MS_REF_MASTERFILELAST_DESIGNDesign Model Update SequenceControls the default update sequence of references and master model in the design model. If 0, the default, the master design model is visible on top of the references.
MS_REF_MASTERFILELAST_DRAWINGDrawing Model Update SequenceControls the default update sequence of references and master model in the drawing model. If 1, the default, the references are visible on top of the master drawing model.
MS_REF_MASTERFILELAST_SHEETSheet Model Update SequenceControls the default update sequence of references and master model in the sheet model. If 1, the default, the references are visible on top of the master sheet model.
MS_REF_NEWLEVELDISPLAYNew Level DisplayIf set, the product displays newly created levels in references. By default, when new levels are created in a model that is referenced by another model, the new levels are not displayed when the referencing model is opened. Newly created models are considered until "Save settings" is performed. This functionality only works when both the master file and referenced files are in the V8 file format.
MS_REF_NO_CVE_LOADDisable loading of CVE ReferencesIf set to 1, any cached reference will not be loaded. This effectively overrides cached reference to use the "Cache Synch: Never (Disconnected)" option.

Setting MS_REF_NO_CVE_LOAD can reduce the time to open large data sets. However, element properties are not available and certain annotation tools may not be available for the unloaded/disconnected cached references.

The following configuration variables affect reference files but they do not appear in the Configuration Variables dialog.

VariableShort nameDescription
MS_REF_NOMISSINGREPORT(not applicable)If set, the Message Center window does not display a message if references are not located.
MS_REF_NOSURVEYFOOTCHECK(not applicable)If set, hides the alert window that opens when you attach a reference with working units set to US Survey Feet to a model whose working units are set to Feet (International Feet), or vice-versa.

top

Rendering / Images

The following table lists the configuration variables that affect rendering and images. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_LOCAL_MATERIALSLocal Material SettingServes the same function as the Copy Materials Locally On Use toggle in the Settings menu of the Material Editor dialog.

If set to 1, materials are made local on use and the DGN file defaults to a local table if one does not exist already (as it would if Copy Materials On Use was enabled).

If set to zero, or undefined, then localization of used materials is controlled by the Copy Materials Locally On Use toggle.

Local material support is new as of the V8 XM Edition and is not supported by earlier versions.

MS_MTBLMaterial TablesSearch path(s) for material tables.
MS_MATERIALMaterial PalettesSearch path(s) for material palettes.
MS_PATTERNPattern MapsSearch path(s) for pattern maps.
MS_BUMPBump MapsSearch path(s) for bump maps.
MS_IMAGEImagesSearch path(s) for images.
MS_IMAGEOUTImage OutputDirectory in which image files created with Drawing> Utilities> Image> Save Image and Drawing> Utilities> Image> Capture are stored.
MS_SHADOWMAPShadow MapsDirectory where shadow maps are stored.
MS_LIGHTINGIES Lighting FilesDirectory where IES lighting data will be stored.
MS_LIGHTLISTPre-defined Light SourcesDirectory that lists the location of predefined lights.
MS_RENDERLOGRendering statistics logFile in which rendering statistics are logged.
MS_SHARED_DR_DIRDistributed Rendering DirectoryWorking directory for shared rendering files.
MS_IMAGE_EDITORImage EditorDefault program to be used to edit an image file. The program is activated by double-clicking in the preview area of the Map Editor dialog.
MS_MATERIAL_PREVIEW_BACKGROUNDMaterial Preview BackgroundImage to be used for the background of material previews in the Material Editor.
MS_FILTEREDCODECSFiltered DirectShow CodecsList of codecs that should not display when exporting a movie from the animator.
MS_RENDERV7MATERIALSV7 Material CompatibilityIf set to 1, materials are rendered as they were in V7. Most affected are translucency, transparency, specularity, and diffuse as applied to pattern maps.
MS_DISABLE_RPCBROWSERDisable RPC Thumbnail BrowserIf set to 1, the RPC Thumbnail Browser is disabled.
MS_RPCDIRRPC Search PathSets the directory in which to search for RPC files.




top

Reports

VariableShort nameDescription
MS_REPORT_OUTPUT Report Output Default output directory where report results will be exported.

top

Security

The following table lists the configuration variables that affect Security. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_SECURITY_LEVELSecurity levelSecurity level for loading and running applications.
MS_SECURITY_SPCSoftware Publishing CertsList of a wildcard expressions indicating where MicroStation can find the files that contain public copies of software publishing certificates that were used to digitally sign the applications that can be loaded in MEDIUM security level. These files normally have the ".cer" extension. They contain information about certificates and public keys. They do not contain private keys. For example, "c:\mycerts\*.cer". The default is "$(_USTN_SITE)SPC\*.cer". (MS_SECURITY_SPC).

top

Seed Files

The following table lists the configuration variables that affect Seed Files. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_BUTTONMENUSEEDButton Assignment Seed FileSeed file containing default button assignments. This file is used to define button assignments if the file defined by MS_BUTTONMENU is not found.
MS_CELL_SEEDFILECell Library Seed FileSeed file used when creating or upgrading cell libraries.
MS_DESIGNMODELSEEDDesign Model Seed FileName of file containing the seed model for the new design models.
MS_DESIGNMODELSEEDNAMEDesign Model SeedName of seed model for new design models.
MS_DESIGNSEEDDefault Design File SeedDefault seed file.
MS_DOCKINGPREFSEEDDialog Docking Preference SeedName of seed file used to create user docking preference file.
MS_DRAWINGMODELSEEDDrawing Model Seed FileName of file containing the seed model for the new drawing models.
MS_DRAWINGMODELSEEDNAMEDrawing Model SeedName of seed model for new drawing models.
MS_DWGSEEDDWG Seed FileSee DWG- and DXF-related configuration variables.
MS_DWGSEED_OVERRIDEDWG Seed File OverrideSee DWG- and DXF-related configuration variables.
MS_DWGSHEETMODELSEEDDWG Sheet Model Seed FileSee DWG- and DXF-related configuration variables.
MS_DWGSHEETMODELSEEDNAMEDWG Sheet Model SeedSee DWG- and DXF-related configuration variables.
MS_FKEYMNUSEEDFunction Key Assignments Seed FileSeed file containing default function key assignments. This file is used to define function key assignments if the file defined by MS_FKEYMNU is not found.
MS_GROUPPANELPREFSEEDGroup Panel Preference SeedName of seed file used to create group panel preference file.
MS_INPUT_CONFIGXMLSEEDTouch Gesture Assignments Seed FileSeed file containing default touch gesture assignments. This file is used to define touch gesture assignments if the file defined by MS_INPUT_CONFIGXML is not found.
MS_PERSONALDGNLIBSEEDPersonal DGNLib SeedSearch path for the default seed file used for creating personal.dgnlib file.
MS_SEED_LINKSET_FILE_NAMELink Set Seed FileName of the file containing the seed link set.
MS_SEED_LINKSET_NAMELink Set NameName of the seed link set.
MS_SEEDFILESSeed File LocationSearch path(s) for all seed files.
MS_SHEETMODELSEEDSheet Model Seed FileName of file containing seed model for new sheet models.
MS_SHEETMODELSEEDNAMESheet Model SeedName of seed model for new sheet
MS_SHEETSEEDDrawing Sheet Seed FileSeed file used when creating drawing sheets.
MS_TASKDIALOGPREFSEEDTask Navigation Dialog Preference SeeedPath of an XML file for default task navigation dialog preferences.
MS_TRANSEEDDefault Translation SeedDefault seed file for DWG, CGM, IGES, OBJ, and 3DS translations.
MS_TRANSEED_OVERRIDETranslation Seed OverrideDetermines whether a user can modify the DGN Seed File setting on the DWG Open Options dialog.
When the variable is not set or set to 0, the first time that the dialog opens, the default DGN Seed File is set by the MS_TRANSEED configuration variable. The user can choose a different seed file.
When the variable is set to 1, the user can only use the DGN seed file identified by MS_TRANSEED. The user cannot choose a different seed file.
When the variable is set to 2, the default DGN seed fie is set by MS_TRANSEED at the beginning of each session. The user can choose a different seed file during the session.
MS_USERPREFSEEDUser Preference SeedName of seed file used to create user preference resource file.
MS_VIEWGROUPSEEDView Group Seed FileName of file containing seed view group for models without a view group.
MS_VIEWGROUPSEEDNAMEView Group SeedName of seed view group for models without a view group.

top

Spelling

The following table lists the configuration variables that affect spelling. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

Configuration VariableShort nameDescription
MS_SPELLINGUSERDICTIONARYSpelling User DictionarySpecifies the user dictionary.
MS_SPELLINGDICTIONARYPATHSpelling DictionariesSpecifies the directory to search for core dictionaries.
MS_SPELLING_CUSTOM_AFFIX_FILE(not applicable)Specifies the directory to search for the .aff file of user dictionary.
MS_SPELLING_CUSTOM_WORD_FILE(not applicable)Specifies the directory to search for the .dic file of user dictionary.

top

Standards Checker

The following table lists the configuration variables that affect the Standards Checker. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_STANDARDSCHECKER_SETTINGSFILERequired Standards Checker Settings FileSets the *.dgnlib file used for standards checking. If this variable is set, the specified file is always used for standards checking.
MS_STANDARDSCHECKER_SETTINGSNAMERequired Standards Checker NameSets the name of the settings to use (within the file specified by MS_STANDARDSCHECKER_SETTINGSFILE). If this variable is set, you cannot select different named settings.
MS_STANDARDSCHECKER_OUTStandards Checker Report DirectoryDefault directory for standards checker reports.
MS_STANDARDSCHECKER_STYLESHEETStandards Checker Style SheetIf this variable is set, it specifies the XML style sheet that is used to view the Standards Checker XML report. This variable can be either a file or a URI (Universal Resource Identifier) that can be used by the browser to locate the style sheet. If this variable is not set, the XML style sheet in $(MS_DATA)standardschecker.xsl is used.
MS_STANDARDSCHECKER_APPSStandards Checker ApplicationsThe list of MDL applications that are loaded when the Standards Checker utility is started.

top

Symbology

VariableShort nameDescription
MS_FONTCONFIGFILEFont Configuration File PathSpecifies the full path of the font configuration file. Default path is “$(MS_SYSFONTDIR)/MstnFontConfig.xml”.
MS_FONTPATHFont DirectoriesPath or list of paths that contain RSC, SHX, or TrueType font files.
MS_SYMBRSRC Symbology ResourcesList of symbology resource files — last one in list has highest priority.

top

System Environment

VariableShort nameDescription
MS_CONFIG Main Configuration FileMain MicroStation configuration file — sets up all configuration variables.
RSC_COMP Resource Compiler Command Line Text string to be inserted at the beginning of the command line by the resource compiler (used to specify where to search for include files).
MDL_COMP MDL Compiler Command Line Text string to be inserted at the beginning of the command line by the resource compiler (used to specify where to search for include files).
BMAKE_OPT Extended MallocCommand line options for BMAKE. Used to search for bmake include (.mki) files.
MS_DEBUGMDLHEAP Table Input If set (to the base name of an MDL application or “ALL), use extended malloc for debugging.

top

Tables

VariableShort nameDescription
MS_TABLE_INPUT Table Input Default directory where the Excel workbooks and .csv files that will be used as data sources for tables are stored.

top

Tags

The following table lists the configuration variables that affect tags. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_TAGOUTPUTTag OutputOutput directory for tag data.
MS_TAGREPORTSTag ReportsOutput directory for tag reports.
MS_TAGTEMPLATESTag TemplatesDirectory containing tag report templates.

top

Temp and Backup Files

VariableShort nameDescription
MS_DWG_BACKUP Directory for DWG backup filesSee DWG- and DXF-related Configuration Variables.
MS_NO_DWG_BACKUP Turn off DWG .bak files See DWG- and DXF-related Configuration Variables.
MS_BACKUP  Backup Files  Default directory for backup files. 
MS_TMP Temporary Files Directory for temporary files created and deleted by MicroStation.
MS_SCR  Scratch FilesDirectory for scratch files created by MicroStation

top

Translation - CGM

The following table lists the configuration variables that affect CGM Translation. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_CGMINCGM Input DirectoryInput directory for CGM translations.
MS_CGMOUTCGM Output DirectoryOutput directory for CGM translations.
MS_CGMLOGCGM Log FilesOutput directory for CGM log files.
MS_CGMTABLESCGM Configuration TablesDirectory containing the CGM translation tables.
MS_CGMINSETCGMIN Settings FileSettings file for the CGMIN application.
MS_CGMOUTSETCGMOUT Settings FileSettings file for the CGMOUT application.

top

Translation - IGES

The following table lists the configuration variables that affect CGM Translation. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_CGMINCGM Input DirectoryInput directory for CGM translations.
MS_CGMOUTCGM Output DirectoryOutput directory for CGM translations.
MS_CGMLOGCGM Log FilesOutput directory for CGM log files.
MS_CGMTABLESCGM Configuration TablesDirectory containing the CGM translation tables.
MS_CGMINSETCGMIN Settings FileSettings file for the CGMIN application.
MS_CGMOUTSETCGMOUT Settings FileSettings file for the CGMOUT application.

top

Translation - Step

The following table lists the configuration variables that affect Step Translation. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_STEPOUTStep Output Directory.Output directory for Step translations.
MS_STEPLOGStep Log Files.Output directory for Step log files.
MS_ROSEDBRose database directory.

Rose database directory

top

VBA

The following table lists the configuration variables that affect Visual Basic for Applications. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect.

VariableShort nameDescription
MS_VBASAVEONRUNAutomatically save VBA projectsIf set to 1, automatically saves modified VBA projects every time it starts running a VBA program.
MS_VBAAUTOLOADPROJECTSNames of standard projectsNames of the projects that are opened when the VBA dialog is opened.
MS_VBASEARCHDIRECTORIESDirectories to search for VBA projectsDirectories that are searched when opening an existing VBA project.
MS_VBANEWPROJECTDIRECTORYDirectory for new projectsDirectory that is used when a new project is created.

top

Uncategorized Configuration Variables

The following table lists the configuration variables that are uncategorized. Each configuration variable expects a valid value. An invalid value will not override a setting. You do not need to close and restart in order for the configuration variable change to take effect, unless noted.

VariableDescription
MSDIRThe root installation directory.
MSLOCALSpecifies the base directory path for where the required writable portions (that is, local for a network installation) are installed.
MS_80TRUETYPESCALEIf set to 1, TrueType fonts using nonstandard TrueType definitions will display as they did prior to V8.
MS_ALWAYSRELATIVEREFPATHIf set (to any value), always turns on the Save Relative Path check box and disables it so that it cannot be turned off. It will save relative paths whenever possible.
MS_ANNOTATIONSCALEPROPAGATIONControls the propagation of a model's annotation scale.
If set to NEVER, the annotation scale will not be propagated , which is not recommended. If undefined or set to any other value, the annotation scale will be automatically propagated.
We recommend that you use a single annotation scale for all annotations in a model. When you attach a model containing annotations to another model, the Use Active Annotation Scale setting allows you to automatically scale all reference annotations to the same scale as the master model. If your reference model has annotations of different scales, those annotations that do not match their model's annotation scale may face display, selecting, and printing problems. There may also be a performance slowdown.
MS_ARCHIVESearch path for archive files.
MS_ARCHIVECLASSSearch path for archive class files.
MS_AUTO_UPDATE_FIELDSControls the rules for updating fields in the active model. If set to ALWAYS, the fields are always kept up to date. If set to NEVER, the fields are never updated. If not set or set to FOLLOWMODELFLAG, the model's Auto-Update Fields property determines if fields are updated for that model.
MS_BASICEXT_LOADList of MDL applications that implement extensions to the BASIC language (MS_BASIC_LOAD).
MS_CMDTABLE_LOADList of MDL applications that will have their key-in tables auto-loaded.
MS_CMDWINDRSCCommand Window resource file. Default is used if undefined.
MS_CODESETMDL application for handling multi-byte character sets.
MS_DATADirectory for data files created or used.
MS_DBOLEDBDATEFORMATSee Setting Up the Database Interface
MS_DEFCHARTRANDefault character translation table.
MS_DEFAULTSHEETRGBAllows you to specify a different background color, which is used when you create the first sheet model. Expects an RGB triplet separated by commas.
MS_DEFAULTDRAWINGRGBAllows you to specify a different background color, which is used when you create the first drawing model. Expects an RGB triplet separated by commas.
MS_DESIGNFILTERDefault file filter for the File Open, Open, and Save As dialogs. If MS_DESIGNFILTER is not defined, the default filter is "*.dgn".
MS_DETAILINGSYMBOLSTYLE_REQUIREDSETTINGSAllows you to customize the validation rules of detailing symbol styles.
MS_DGNAPPSList of all design file MDL applications.
MS_DGNINDEXER_PORTIf set, the application uses this port to connect to the remote DGN Indexing servers. The default value is 4000.
MS_DGNOUTDirectory containing DGN files created as a result of "on the fly" translation from other file formats.
MS_DIMLEGACYPOINTORDERIf set to 1, the dimensioning tools use the legacy data point sequence for placing linear and angular dimensions (StartPoint – ExtensionPoint – EndPoint).
MS_DISABLEWINDOWGHOSTINGIf set to 1 or ON, disables the window ghosting mechanism in the Windows OS. Windows creates a ghost window for the application's windows when it determines that an application has been unresponsive for at least five seconds. Several features, such as Print/Plot and Image Save, may require a long span of continuous processing time, resulting in the activation of these ghost windows and the associated undesirable side effects in the user interface. Turning off the window ghosting for the process prevents these undesirable effects.
MS_DISALLOWRELATIVEREFPATHWhen set to 1, you cannot save a relative path for a reference. The Save Relative Path check box is removed from the Attach Reference dialog.
MS_DRAWINGDIRSpecifies the default folder path that should open when you click the Browse Drawing File or Create New Drawing File icons in the Create Drawing dialog.
MS_DWG_XREF_DEFAULTTREATASELEMENT_OFFWhen this variable is not set, DWG’s xReference attachments are treated as elements, just as they are in AutoCAD. When it is set to 1, the attachments are not be treated as elements.
MS_ELEVPROP_AS_ZAllows you to assign elevation attributes as Z values during SHP, MIF/MID, or TAB file Import/Open/Attachment. This is accomplished by setting the value to one or more property names that you used to indicate elevation in your SHP, MIF/MID, or TAB files. For example, if you have a SHP, MIF/MID, or TAB file that uses a property called "ELEVATION" to contain elevation data, you would set:
MS_ELEVPROP_AS_Z=ELEVATION
If you have an additional SHP, MIF/MID, or TAB file that uses a property called "HEIGHT" to contain elevation data , you can use a vertical "|" delimiter to specify two elevation attributes as follows:
MS_ELEVPROP_AS_Z=ELEVATION|HEIGHT
MS_GUIHANDIdentifies auxiliary handlers.
MS_HELPLOAD_APPLICATIONDetermines which application help is based on. Current options are HTMLHelp (default), or StaticWeb. StaticWeb refers to static HTML pages on a web site.
MS_HELPLOAD_SERVERSpecifies the root location of the help content. Defaults to $(USTN_DOCUMENTATIONROOT), but can be set to a file server or URL. This variable does not determine if you are using uncompiled HTMLHelp content. If you set this variable, the value of MS_HELPLOAD_SERVER should be the location containing the product directory.
MS_HELPPATHPath to help resource files.
MS_INITAPPSList of initial start-up MDL applications.
MS_LEVEL_DO_NOT_SYNCHRONIZE_ATTACHMENT_LEVELS_TO_DGNLIBIf set to 1, the reference attachment levels are not synchronized to the attached library.
MS_MEASURE_AREA_UNIT2If set to 1, the unit of measurement in the Area or Volume fields is displayed as unit2. For example, m2 for Square meters and m3 for Cubic meters. If not set, it is displayed as Sq.unit or Cu.unit. For example, Sq.m for Square meters and Cu.m for Cubic meters.
MS_NO_POSITION_MAPPING_HINTSIf set to 1, the keyboard navigational aids will not display when <Esc> is clicked.
MS_NOTEAUTOUPDATEControls the list of settings that will be propagated to existing notes when a dimension style is saved. To propagate all settings, set to All. To control individual settings, list attributes in a comma-separated list.
MS_OLDUSERLICENSEFile that contains old user license information. Required for when installing a product upgrade.
MS_OLEDBMAXDATASee Setting Up the Database Interface
MS_OPENDESIGNFILEFILTERInitial file filter list for the File Open and Open dialogs.
MS_OPENREFFILEFILTERInitial file filter for the Attach Reference File dialog.
MS_ORACLEPREFETCHSpecifies the number of rows pre-fetched from the database, maximum 65535. For example if MS_ORACLEPREFETCH is set to 1000, there will be 1000 rows of data returned to the client and cached. If this configuration variable is not set, one row is pre-fetched. Setting MS_ORACLEPREFETCH can result in improved query performance over high latency networks, such as Wide Area Networks (WANs).
MS_PLOTBORDER_TIME_FORMATChanges the date and time format for printed outputs from Windows Regional Settings to another format. Set to v7.0 to use the v7.0 format.
MS_REFCOLORTABLEIf defined and set to 1, always uses the reference's color table. If defined and set to any value other than 1, never uses the reference's color table. If not defined, uses the user preference to determine whether or not to use the reference's color table. You need to close and restart in order for this configuration variable change to take effect
MS_RIGHTLOGICKBIf set to 1, keyboard input is right to left.
MS_RSRCMain resource file. Typically set to "ustation.rsc."
MS_SESSION_DEBUGUsed to start session debug prior to the loading of the database server. By setting this configuration variable, you can receive immediate debug information from the consumer DLL. MS_SESSION_DEBUG can be used with all the database servers. A value of 1 enables receipt of debug information from the database server and the corresponding DLL — ORACLE, ODBC, or OLEDB. A value of 0 enables receipt of debug information only from the DLL.
MS_SHEETDIRSpecifies the default folder path that should open when you click the Browse Sheet File or Create New Sheet File icons in the Create Drawing dialog.
MS_SIGNATURE_DISPLAY_UNVERIFIEDControls how an unverified digital signature is crossed out. Value is color weight style strikeout where:
color = a number, specifying the menu color identifier number
weight = a number specifying the line weight of the annotation
style = a number specifying the style
strikeout = how to strike out the signature
  • "X" Draw an X over the signature
  • "—" Draw a line through the middle of the signature

The default is a heavy solid red X over the signature. This is represented by 4 7 0 X
To draw a heavy solid blue line through the signature, use the following: 1 7 0 —.

MS_SIGNATURE_DELETE_REQUIRES_PRIVATE_KEYIf set, you may not delete a digital signature unless you possess the private key that was used to create the signature. The default is 0.
MS_SIGNATURE_SHOW_FULL_NAMEIf on, displays the full subject and issuer name from the signer's certificate in the Properties balloon for a digital signature element.
MS_SMARTSOLIDSpecifies the directory path for the SmartSolid subsystem.
MS_SNAP_TANGENT_POINT_DEFAULT_MODEThe snap mode used to compute the location of a perpendicular or tangent point snap. Applies only when perpendicular or tangent point is the default snap mode. Possible values are:
b - bisector
i - intersection
k - keypoint
m - midpoint
m1 - multisnap1
m2 - multisnap2
m3 - multisnap3
The default is 'k' (keypoint).
MS_TEXT_AUTOSTACKFRACTIONS_ALIGNMENTSets the alignment for stacked fractions, when the Fractions advanced text style setting is on. Values are:
1 = Top
2 = Center (Normal for DWG files. The default if the configuration variable is not defined.)
3 = Bottom
MS_TEXT_AUTOSTACKFRACTIONS_TYPESets the type for stacked fractions, when the Fractions advanced text style setting is on. Values are:
1 = Normal
2 = Diagonal (Normal for DWG files. The default if the configuration variable is not defined.)
Normal Center
MS_TEXT_STACKFRACTIONS_SCALEThe value is the percentage scale factor for stacked fractions. (70 is normal for DWG files, and is the default if this configuration variable is not defined.)
MS_THUMBNAILIf this variable is not defined, the product looks for a saved view called "Preview," and if found uses that saved view's settings (model, orientation, render mode, etc.) to create the thumbnail. If the variable is defined, the product takes whatever the variable is set to and looks for a saved view of the same name. If the specified saved view name cannot be found, then the system creates/updates the thumbnail image using the view that was active at the last time you selected File> Save Settings.
The latter also occurs if the variable is not defined and if the saved view called "Preview" does not exist in any design, drawing, or sheet model in the DGN file. If this variable is set to "NONE," then no new thumbnail is generated. If a thumbnail already exists in the DGN file, setting this variable to "NONE" does not remove what already exists in the DGN file; it simply does not update what already exists.
MS_USERLICENSEFile containing user license information.
MS_USERPREFUser preference resource file.
MS_USERPREF_APPSSet by application configuration files to add user preferences to standard dialogs.
MS_VISEDGES_OMIT_EDGES_BETWEEN_PLANAR_FACESIf set to 1, the interior edges between adjacent planar faces will be omitted even if the Remove Smooth Edges check box is off. This may be desirable for meshes imported from external formats that do not correctly display the interior edges between mesh faces.
MS_VISEDGES_PRESERVE_UPDATE_SEQUENCEIf set to 1, when you export the visible edges, the references are displayed in the sequence set in the Update Sequence dialog.
MS_VIEWATTRIBUTES_PLUGINASSEMBLIESList of assemblies to search in for View Attributes dialog plug-in groups.
PZIP_OUTSpecifies default directory for creation of Packager files.

top

Not listed or undocumented Configuration Variables

VariableDescription
MS_TASKNAVIGATION_CONFIGURATIONWhen this variable is set to 1 the Task Navigation Category is displayed in Preferences Dialog. This preference category is hidden by default.
MS_CULTUREThe configuration variable MS_CULTURE allows you to select the language of installed language packs to be used.
If the configuration variable MS_CULTURE is set, the language selection from Preferences dialog is dimmed.
-
-
-
-
-
-
-
-
-
-
-
-
-
-

top

See Also

How to create a list of all CONNECT Edition Configuration Variables

How to export CONNECT Edition configuration variable values to a text file

MicroStation V8i Variables

Product TechNotes and FAQs

External Links

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Renamed configuration file (CFG) still loading

$
0
0

  
 Applies To 
  
 Product(s):MicroStation
 Version(s):08.11.09.459
 Environment: N\A
 Area: Configuration
 Subarea: General
 Original Author:Bentley Technical Support Group
  

Problem

One of the application configuration files extensions has been renamed from ".cfg"
to ".cfg_ignore" but it is still being loaded.

Solution

When MicroStation loads configuration files it searches for the first
three characters of the file extension, thus ".cfg_ignore" will be loaded.
Rename the extension completely (i.e. to ".cf_") for MicroStation to ignore the file.

See Also

Product TechNotes and FAQs

External Links

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Viewing all 5174 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>