Printing custom line styles with Print Organizer

We utilize custom line styles in our workspace i.e. a "w" inserted in a line for waterline. When we print this sheet using the standard print option and our pdf plt driver, it shows up correctly. I am new to Print Organizer so hang in there with me. I have put our pdf plt driver as the Printer driver configuration file. I don't know if this is correct or not. The bottom line is I am not able to see our custom line style when I use the Print Organizer. Any help would be most appreciated.
Parents
  • Are you running ustation.exe with customized command-line arguments, or using another technique to run MicroStation in a non-standard manner?

          
    .

  • Andrew Edge:
    Are you running ustation.exe with customized command-line arguments, or using another technique to run MicroStation in a non-standard manner?
    Can you explain this in further detail? In customized do you mean a customized project config etc? We are running custom configs.
  • Hi Jeff,

    The TR for the Font issue is 8000493285, this issue goes back as far XM.

    My TR for the Linestyle issue was related to and older TR192355, (Support via Larry Abla)

    I did not file a TR for the workspace isssue since it was discovered by others here in this post.

    I am currently waiting for the SS1 release of Inroads before I install the SS1 release of Microstation.

    Bob
  • The solution we found was to make Geopak and similar applications to only load when a drawing is opened. We changed MS_DGNAPPS to _USTN_FIRSTDGNAPPS in the geopak.cfg.

    Geopak will still open and Print Organizer will work on the same machine.

    [MAIN]
    %if !defined (GPK_START)
    # MS_DGNAPPS < $(SUITE_INSTALLDIR)bin/gpkstart.ma #Comment out this line
    _USTN_FIRSTDGNAPPS < gpkstart.ma #Add this line

    MS_LIBRARY_PATH < $(SUITE_INSTALLDIR)bin/

     

    Jason

  • Andrew,

    I am running MicroStation 08.11.07.469 (priority build) Select Series 2 and the command line arguments (-wr) still don't work with Print Organizer. The custom line styles will only print correctly in Print Organizer when I remove the command line argument and customize mslocal.cfg. Please let me know if Bentley is still working on this. I am also running GeoPAK Site. Thanks.

  • Can someone give us an update on the Print Organizer vs. command line arguments issue? Thanks.

  • I have been working with Larry Abla (Bentley - Plotting Support) on the issue of fonts and line styles from the custom workspace not showing up correctly when using Print Organizer. I am runing a priority build of MicroStation V8i (SS2) - version 08.11.07.480 (which resolved a different "glitch" in Print Organizer).

    Ticket # 7000049358 is for this issue.

    We also use the command line qualifier "-wr" to redirect our workspaces to the local server (in each local office).

    This version of MicroStation now has a Printing - Configuration Variable called:

    "Engine Command-Line Arguments" (MS_PLT_ENGINE_CMDLINE_ARGS)

    We have this working with using a Command Line qualifier - as long as you use a Mapped Drive Letter, i.e.:

    MS_PLT_ENGINE_CMDLINE_ARGS = -wrM:\network_workspace_location\   (M:\ is the mapped drive letter)

    Our problem is now that we need to use a UNC address (instead of a Mapped Drive Letter) - and this is currently not working/not supported. The inability to use a UNC for this variable is a known issue: TR 328514

    The current work-arounds are: use a mapped drive, set a local system environment variable in Windows or modify the local mslocal.cfg file - which we would prefer not to do any of these at this time.

    We are also running GEOPAK V8i (SS2) - version 08.11.07.536 and InRoads V8i (SS2) - version 08.11.07.615 - and these versions no longer appear to be causing an issue with Print Organizer.

Reply
  • I have been working with Larry Abla (Bentley - Plotting Support) on the issue of fonts and line styles from the custom workspace not showing up correctly when using Print Organizer. I am runing a priority build of MicroStation V8i (SS2) - version 08.11.07.480 (which resolved a different "glitch" in Print Organizer).

    Ticket # 7000049358 is for this issue.

    We also use the command line qualifier "-wr" to redirect our workspaces to the local server (in each local office).

    This version of MicroStation now has a Printing - Configuration Variable called:

    "Engine Command-Line Arguments" (MS_PLT_ENGINE_CMDLINE_ARGS)

    We have this working with using a Command Line qualifier - as long as you use a Mapped Drive Letter, i.e.:

    MS_PLT_ENGINE_CMDLINE_ARGS = -wrM:\network_workspace_location\   (M:\ is the mapped drive letter)

    Our problem is now that we need to use a UNC address (instead of a Mapped Drive Letter) - and this is currently not working/not supported. The inability to use a UNC for this variable is a known issue: TR 328514

    The current work-arounds are: use a mapped drive, set a local system environment variable in Windows or modify the local mslocal.cfg file - which we would prefer not to do any of these at this time.

    We are also running GEOPAK V8i (SS2) - version 08.11.07.536 and InRoads V8i (SS2) - version 08.11.07.615 - and these versions no longer appear to be causing an issue with Print Organizer.

Children
  • This TR is fixed in 8.11.9.xx versions of MicroStation according to the TR notes.  With the newer version, there is now no need to specify the -wr option via MS_PLT_ENGINE_CMDLINE_ARGS. Print Organizer will automatically pick up the -wr that is present in the active MicroStation's command line and pass it to the worker.

    The -wr is picked on if:

    - MS_PLT_ENGINE_CMDLINE_ARGS is undefined (meaning user has not explicitly defined his own set of args) and if

    - MS_CONFIG is not defined (meaning there is no user specified “–wc” on the command line of the active MicroStation.)

    - the active MicroStation is not in PW integration mode