How to Generate MSDebug Files for MicroStation and OpenRoads

Slow commands, long pauses, or erratic behavior in Bentley MicroStation CONNECT or OpenRoads usually point to one of four causes: configuration loading issues, network latency, ProjectWise, or bad workspace variables. One of the fastest ways to see what is really happening under the hood is to generate an MSDebug file.

An MSDebug file shows every configuration file that loads, the order they load, every variable that gets set, and where it came from. When MicroStation or OpenRoads feels slow or unpredictable, this file helps you pinpoint the cause instead of guessing.

How to create an MSDebug file

Method 1: Using the MicroStation or OpenRoads shortcut

  1. Right click the desktop shortcut for MicroStation or OpenRoads and choose Properties.
  2. In the Shortcut tab, go to the Target field. Add a space at the end, then type -debug.
  3. Select OK.
  4. Launch MicroStation or OpenRoads using that shortcut.
  5. A text window will open and report that the MSDebug.txt file was created in the same folder as the application executable.
  6. Close the text window.
  7. Remove -debug from the shortcut once the file is generated.
Context menu showing options for a desktop shortcut, with 'Properties' highlighted.
Screenshot of the properties window for MicroStation CONNECT Edition, showing the target location and command line for debugging.

Method 2: From a Command Prompt

  1. Open Command Prompt.
  2. Run:
    “C:\Program Files\Bentley\MicroStation\MicroStation.exe” -debug
    or for OpenRoads:
    “C:\Program Files\Bentley\OpenRoads Designer\OpenRoadsDesigner.exe” -debug
  3. A text window will confirm that MSDebug.txt was created.
  4. Close the window.

What to look for in the MSDebug file

The MSDebug file is long, but a few areas are especially useful when troubleshooting performance:

Screenshot showing the output of a configuration file processing in MicroStation CONNECT, displaying various system parameters and file paths.

Workspace load order
See which configuration files are being loaded and in what order. Conflicting workspaces, old workspace paths, or legacy ProjectWise integration remnants often add delays.

Network paths
If any configuration file points to a network location, expect slower startup and occasional freezing. Cloud synced folders, redirected profiles, or DFS paths can amplify this.

Bad variable overrides
Variables like MS_DEF, MS_RFDIR, MS_CELL, MS_SEED, MS_DGNLIBLIST, or MS_MDLAPPS pointing to invalid or unreachable locations can cause multi second delays.

Third party add ons
The file shows which MDL, .NET, or workspace extensions are loading. One outdated add on can stall everything.

ProjectWise integration checks
If ProjectWise is installed or partially removed, the MSDebug output will reveal whether integration hooks are still active. This is a common cause of random hangs when the ProjectWise client is outdated.

Other performance checks
These are issues we see often on current MicroStation CONNECT and OpenRoads deployments:

1. GPU driver mismatch
MicroStation and OpenRoads are sensitive to driver versions. Update to the latest certified GPU driver for your card.

2. Windows graphics settings
Force MicroStation/OpenRoads to use the discrete GPU if on a laptop with hybrid graphics.

3. Corrupt user preference files
Resetting MicroStation’s user preferences often clears odd pauses.
Delete or rename:
C:\Users\%username%\AppData\Local\Bentley\MicroStation\10.0.0\prefs

4. Slow antivirus real time scanning
Excluding MicroStation program folders and workspace directories can reduce file open delays.

5. Network file latency
Working from a remote server increases file open times. Testing locally can confirm if this is the bottleneck.

6. Oversized or legacy DGNLIBs
Large DGNLIBs or ones migrated through many versions can slow startup and level display operations.

The MSDebug file gives support a full map of your configuration, without guessing.

Leave a Reply