[ORD Any version] Workspace Issues - Legacy MicroStation Settings

We have a WIP Workspace that is currently in limbo due to COVID-19 budgetary impacts. It originated as our Ss4 workspace and was migrated with Chuck Lawson's assistance as part of our DOT Amp process. During the migration process, we tested using as many of our legacy settings as possible with the hope that migrating a project from our Ss4 workspace to CONNECT would be as painless as possible. We did see a number of issues that were troubling, but they did not seem insurmountable. 

Recent posts in this newsgroup have made me want to revisit those concerns. Here are some of the issues we found:

  • The DGN Preview files, used by the Annotation Group Manager are defined using a different resolution than our legacy files. We have been using 1000 per US Survey Foot. The preview DGN files use 10000 per US Survey Feet. This effects the preview graphics causing them to be scaled 10 times too big. With Chuck's help, we created replacement files but although they allowed us to setup our annotion needs, it was not 100% without issues. For example, many of the distances in the preview windows for annotating arcs spirals and lines were off by the factor of ten. The resulting annotations the tools created had correct values, so we accepted this as tolerable. However, every upgrade of the software requires us to replace those preview DGN files on every PC once the update is finished. This is just one extra step that requires Admin privileges to accomplish. And, if we have consultants working for more than one client, this complicates things for them in ways that we feel are unacceptable. 
    • I tried a different approach on how to modify the preview DGN files:
      1. Set the resolution to match our seed files
      2. Use the transform geometry tool to scale the graphics by 0.1
      3. For files with profiles, this appears to require two transform operations - one for the plan graphics and one for the profile. The profile was visible during the plan transform and appeared to scale, but the indicators of the plan geometry (linear, spiral & arc colors and cardinal lines, indicated the profile was still 10 times too large. The second transform while the profile model was active restored the appearances. Still trying to work out the proper settings for getting the profile annotation groups to display.
  • A quick test of taking one of our seed files and making it match the resolution of the preview corrected the preview issues, but basically broke all of our annotations as the text was now 10 times to big.
  • Our Text Styles are defined in decimal inches, mimicking the traditional Leroy/Kroy Lettering guides. This was possible due to the units, sheet sizes & scales.def files we have been using since migrating to V8. Files that originate outside of our agency often exhibit issues related to this.One of these is annotation scale - the drawing scale will report as custom since their scale definition does not line up with ours. We are very concerned with the impact to our users and existing projects if we have to change this.

Has anyone else found that they had to make impactful changes to their default settings and how has that impacted ongoing projects.

  • That sounds horrible! That's just one more thing I am sincerely worried about.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

  • Are you talking about taking MicroStation Workstation template files and adjusting them to work within ORD? It seems like it may be best to rebuild your workspaces from training or default templates instead, because the amount of unsolvable (for me anyway) errors I got trying to adapt a MicroStation workspace into ORD was too much. 

    I had all manner of painful issues with ORD crashing constantly, even with the most minute of tasks like selecting a complex element. Even when it wasn't crashing, it would regularly take 5 minutes plus just to select a simple element. I tried all sorts of things myself and eventually found that I had to just start completely fresh work from a default training workspace. Any mingling of MicroStation workspace settings with ORD workspaces seemed to cause a nightmare amount of errors and crashes in ORD.

    Granted I haven't anywhere near the experience you clearly have, nor training (because what forward thinking organization invests in that, right?) but even when I tried troubleshooting some of the issues I was getting with one of the Bentley support gurus, he recommended I just switch to a training workspace and go from there, and it solved the bulk of my problems.

  • Giles/ Chuck/ Mary:

    It has been my experience that developing all workspaces in ORD and then using them within MicroStation works quite well. Doing the opposite- as you have described Giles- could create a wide variety of issues; issues too many to mention here without writing a thesis. I routinely test MicroStation proper whenever I make major changes in ORD, and MicroStation continues to work quite fine. If I can find some time, Chuck, I will try to address the issues as you have listed them.

    Mark

    Mark Anthony Plum
    Chief Technology Officer

    1601 N.W. Expressway, Suite 400
    Oklahoma City, OK  73118
      
  • Thank you, Mark, that's very valuable info. ORD seems to be too messily stitched a Frankenstein's monster to pull much into it - it's less than the sum of it's parts, at least in terms of stability. Kid gloves leaves it bruised and battered, so I'm not that surprised to hear that approach works much better.

  • We expect to have to migrate a ORD Workspace to function in plain CONNECT. Our Highway Division is the 800 lb gorilla - we drive the CAD System, with our workspace enhanced to fit others needs. But if someone does not use InRoads (legacy) or Open Roads Designer (still not implemented), they still use our workspace for MicroStation. We are hoping that any legacy projects can be brought forward into CONNECT (ORD or MicroStation) with minimal issues. My post was prompted by other discussions that seemed to indicate that this might not be possible and that can be a big problem. At a DOT, projects are routinely shelved due to changing priorities, politics, funding and many other reasons. When one is brought off the shelf, management does not expect a complete redo, but anticipates that it can be picked up and used as-is. If recommended and possible required settings make that impossible, I need to know as does my management.  


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996