Charles Meuser's Communities Activities

Sheet Numbering - Adding External Sheets

Charles Meuser — Mon, 16 May 2022 18:07:09 GMT

We're looking at taking advantage of the sheet numbering functionality in MS and ORD and doing a little testing. I wanted to reach out to the community and see how others are handling the sheet numbering when other "external" sheets are part of the final document.

In our workflow, we sometimes have external, non-CAD, generated data that's intermingled throughout the contract document, sometimes in the middle, sometimes at the end. Creating folders and subfolders within the sheet index does help with the renumbering of our sheets that follow any of those external docs, at least that's how I conceptually see it working.

Aside from creating blank sheet placeholders, how is everyone else handling these situations?

Thanks

Chuck

MS CE Update 16 (10.16.03.11)

ORD CE21-R2 Update 10 (10.10.21.04)

OpenRoads Designer 2022 Release 1 "-wr X:/Configuration" switch issue

Charles Meuser — Thu, 29 Sep 2022 12:14:46 GMT

Just testing the ORD 2022 R1 within our environment and am running into a similar issue I had with MS R17 (which is now fixed in 17.1) where the command line switch "-wr<drive letter>/Configuration isn't recognized.

Is anyone else seeing similar results?

I am not a huge fan of the managed configurations since it can't be pushed out to the entire staff.

Where and how is the variable _USTN_WORKSETDGNWS defined?

caddcop — Thu, 13 May 2021 14:53:09 GMT

I am trying to configure ORD CE for ProjectWise.

Our folder structure does not support worksets under workspaces but there a videos on how to configure that. I have been successful in making out projects work as worksets and associating them with a workspace. However, my efforts to enable the sheet index (and whatever else a DGNWS file provides)have failed. I have defined a common location for the Workset CFG files and location where the DGNWS file should be created using _USTN_WORKSETSDGNWSROOT.

But I cannot figure out how to define _USTN_WORKSETDGNWS in PW. According to its description, it should be the full path file name of the DGNWS file. But in my PW Managed Workspace, it is being defined to the Workset name only and according to the Configuration Dialog box, it is being set at a System Level, While most of my workset variables at reported to be correctly set to Workset Level.

I discovered that if I list the Configuration Variables using the Show Configuration Variables command of the dialog box and compare its list to the Summary of Variables from an MSDEBUG.TXT file, there are a number of assignments that are missing. Particularly glaring is the _USTN_WORKSETDGNWS assignment. In fact, I have searched every CFG I could find and do not see it listed anywhere.

If it is automatically generated, are there rules and conditions that can effect its assignment? I need to figure out why I cannot get the variable and its operational purpose to function in Project Wise.

Longer File Opening and Batch Printing Times with Connect Products on a Network drive

Charles Meuser — Mon, 19 Apr 2021 13:52:29 GMT

Is anyone still experiencing longer than expected file opening and batch printing (via print Organizer) times using any of the Connect products with the Configuration environment and project files being stored on a network environment?

Both our workspace (configuration) environment and the project files exist on the same NAS storage device and organized on separate drive letters. I have even gone as far as placing the workspace/configuration environment locally on a device and the project files being the only files stored on NAS storage. The results are similar if not the same.

Is anyone else experiencing these similar issues?

MS Connect:10.15.02.11

OpenRoads Connect:10.09.00.91

Thanks

Chuck

Ask A Question II

Mon, 19 Apr 2021 13:52:31 GMT

Ask 10 questions in a forum.

Where can we get an update on a defect dealing with dgnws files and their locations?

SteveMeyer — Mon, 08 Jun 2020 15:16:58 GMT

We have a defect filed (Defect 1094694) for allowing a dgnws to reside in the main CAD folder in a given project rather than one huge directory with all cfg and dgnws files where all users would have read/write access. How do we find out on the progress of such a Defect ticket?

ConfigurationSetup.cfg being changed

Kevin van Haaren — Thu, 04 Jun 2020 16:49:52 GMT

My testing is with OpenRoads Designer 10.08.01.33 (2020 Release 2 Update 8) but I believe this is more a MicroStation Connect issue (I have not tested in MicroStation Connect).

default ConfigurationSetup.cfg as below:

[General]
_USTN_CUSTOM_CONFIGURATION=C:/ProgramData/Bentley/OpenRoads Designer CE/Configuration/

[SetConfiguration]
%if !defined (_USTN_USER_CONFIGURATION)
%if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))
_USTN_CONFIGURATION = $(_USTN_CUSTOM_CONFIGURATION)
%endif
%endif

Open a file with one of the installed workspace/workset.

Now change _USTN_CUSTOM_CONFIGURATION (I changed to C:/CADDLib/Connect/ which is an internal location for us)

Open ORD again, when the backstage workspace/workset selector is open check ConfigurationSetup.cfg and (if you have the same problem as us) you'll see the line _USTN_CONFIGURATION has been hard-coded to the _USTN_CUSTOM_CONFIGURATION.

[General]
_USTN_CUSTOM_CONFIGURATION=C:/CADDLib/Connect/

[SetConfiguration]
%if !defined (_USTN_USER_CONFIGURATION)
%if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))
_USTN_CONFIGURATION = C:/CADDLib/Connect/
%endif
%endif

I can also trigger this by setting _USTN_CONFIGURATION in a different file (for example WorkspaceSetup.cfg), i admit this would be a kind of dumb thing to do but it does trigger it.

Important part seems to be you have to open a file using the one _USTN_CONFIGURATION, then exit, modify _USTN_CONFIGURATION and open ORD again. At that point the _USTN_CONFIGURATION is re-rewritten. If at this point you change _USTN_CONFIGURATION back to _USTN_CONFIGURATION = $(_USTN_CUSTOM_CONFIGURATION) it won't be changed again until you change _USTN_CUSTOM_CONFIGURATION in ConfigurationSetup.cfg (or _USTN_CONFIGURATION in a different cfg file)

This is kind of killing me at the moment because we actually need to change the _USTN_CUSTOM_CONFIGURATION for a particular client and flipping back and forth is going to be necessary. My normal ConfigurationSetup.cfg has logic for detecting this and setting the correct one, but when it does the value is then hard-coded into the configurationSetup.cfg.

msconfig.cfg/PCF files for OneDrive

Boney Yim — Wed, 24 Jul 2019 06:28:00 GMT

Need help on how to control the following directory:

C:\Users\byim\Documents\OneDrive

Since BYIM is changing depending on who logs on to the OneDrive, it is difficult set up Microstation msconfig.cfg and PCF files so that these will always work regardless who logs on.

Thanks!

Connect products while Work from Home

Charles Meuser — Mon, 10 Aug 2020 13:19:45 GMT

I am curious what everyone is doing who don't use ProjectWise and still have their staff working from home and from the office using MicroStation & OpenRoads Connect edition with a networked workspace. Currently, we have the majority of the staff WFM (Working From Home) and a couple who are in the office. The WFH staff access the corporate network over VPN.

We have the products configured to look to a specific network location for Configuration (i.e. J:/Configuration/) in ConfigurationSetup.cfg that is pushed to each users C:\ProgramData\Bentley\<PRODUCT NAME>\Configuration folder by IT using AD/Group Policy.

The staff who are working in the office have no issues however, the WFH staff experience extreme latency in file access and general operation when in a file while on the VPN. Some of the WFH staff occasionally go to the office. To help with some latency, I have setup a BAT file that copies the network version of the environment to the WFH folks local workstations (C:/)

Aside from manually copying a local version of ConfigurationSetup.cfg that points to the local Configuration folder, what else can be done?

Is anyone else working in a similar situation and what are you doing to help with the latency issues?

Thanks in advance

Chuck

[CONNECT (ORD)] Using _USTN_CUSTOM_CONFIGURATION to Retain Local Workspaces/Worksets and Provide Network Custom Workspace/Workset

caddcop — Wed, 29 Jul 2020 14:19:40 GMT

We went through the AMP program with ChucK L and with his assistance, create a local workspace/workset. I was able to copy this to a network share and get it up and running, as a custom configuration while preserving the delivered examples.

Now, as we are continuing to refine our workspace, we wanted to move the Workspace to a new location and leave the worksets under their original location (at least for now). Everything I have tried to get the new location for the workspace has failed. Currently, the custom configuration option is now gone from the workspace menu. I was very experienced with CFG file processing in prior versions but CONNECT has thrown me for a loop. When I look at the contents of some of the CONNECT CFG files and try to follow along with their logic, I see many things that appear to make zero sense.

is there some type of follow the bouncing ball explanation of what occurs in these files and what makes the Example Configuration and Custom Configuration both display and what minimum files must exist where for this to work?

Print Organizer - Nested Reference Not Printing

Charles Meuser — Thu, 28 May 2020 12:59:42 GMT

We have a project using MicroStation Connect Edition and used OpenRoads for drawing production to create plan & cross sections to specific project folders. I have a workset file that defines the locations of the corridor files and the master compile file that the named boundaries were created in. Our folder structure is as shown in the image below.

The projects base reference files, corridors, etc.. all are stored in the ..02 Draw/01 Production folder, The cross section sheet files are stored in the ..02 Draw/03 Plans/Cross Sections folder.

When I create a PSET, and preview a cross section sheet, the sheet & drawing model contents show up fine, the nested reference of the model does not appear. If the cross section files are in the ..02 Draw/01 Production folder, then the model appears in the sections. I am having similar issues with the plan sheets as well.

If it were an issue with the workset config, I feel like none of the nested references would show up when opening the plan or cross section files. The line character length of each of the file paths is less than 100 characters.

We've used nested references in previous versions of MicroStation hundreds of times with no issues at all.

Any insight is greatly appreciated.

MicroStation Connect Edition Update 13 - Version 10.13.01.01

Ask A Question I

Mon, 27 Apr 2020 08:09:06 GMT

Ask a question in a forum.