MIcrostation Connect Edition Update 14, HOW IS IT?

I would like to hear from anyone that has updated to CU14.

I am looking to go there but would like to hear some reviews from users that have ventured into it. 

Thanks.

Parents
  • Well it's still pretty buggy, esp. for a revision 14. If you're coming off v8i, you'll likely have a lot of minor issues/annoyances. If you're simply upgrading from a previous Connect ,you'll only see minor differences.

    I always recommend upgrading to the latest version, it's a better long term strategy. I have adjusted many of my work methods to better utilize Connect, many find this painful, I believe it's necessary with any software.

    Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley

  • I do agree with Jan, and BUG reporting is seemingly "left to others" in a lot of situations.
    We are all guilty of being too "busy" to report bugs and just find a workaround that suits us, then this becomes a permanent workflow.

    Agree that for a Release 14, there are many, many bugs. Bentley seemingly solve one, and they create 2 new bugs. It certainly feels like that, if I am not actively monitoring this effect.

    DO report all crashes using the crash reporting (when Microstation offers me a dialogue to. Occasionally, it crashes with no warning, and seemingly not reproducible - save often as even the autosave feature of MS is not infallible)

    All in all, getting there.

    I will say, the latest update (14.2?) has slowed the REFERENCE tasks down, to try to get a handle on the number of crashes this feature (been around since early days so, why break it Bentley?) throws up?
    Just have to get used to it until they figure out exactly how to fix this new bug set without slowing down the actions.
    One of those "things" we learn to live with....unless we all get "noisy" and start complaining.

    Greg Smith

    Microstation 10.17.01.058

    Opinions expressed are my own and not necessarily those of my employer

  • Another possibility is "poor' geometry step files don't import well into MS-CE at all and when we get a 3D dwg file created in inventor or solid works they can be extremely slow.  Normally they have a bunch of errors or warnings on open.  A step in helping to correct this is opening the dwg files in autocad first that seems to correct some of the missing data in the translation then microstation can deal with it better.  The other thing we have to do is convert those dwg files into dgn files.  Lastly make sure your not using a bunch of old data/cells that are ACIS solids.  Every time it's reference the software has to do a conversion to parasolid.

  • No change in any configuration between U5 through U14.
    Why the sudden change?
    Only one factor has changed, the product.

    However, on reflection, there is ONE factor that is in play. We use "Container" files for REFERENCES, then internally REFERENCE to DRAWING and then SHEET. So nesting level is maximum of 3.
    But one REFERENCE file in play is a CONTAINER file in its own right. This raises the nesting to 4, with external files.

    While this is SOP and entirely within the capability of Microstation, I'll break this out to single level and see if the timing improves.
    If it does, then this pinpoints an issue that wasn't before?

    Edit: Yep, that was the culprit. Now to question why this is such a problem in U14... I'll log a fault, but the files in question, while in use in previous releases, are third party and it may be difficult to determine exact issue affecting U14.

    Greg Smith

    Microstation 10.17.01.058

    Opinions expressed are my own and not necessarily those of my employer

  • Observing with 2D files, as well as 3D files. But yes, I will look into this when I have a chance.

    Some of the ELEMENTS in the core REFERENCES we use date back to V5 ! But what can one do here?
    To export everything out and back in in an attempt to "clean up" the elements is a hiding to nothing.

    Greg Smith

    Microstation 10.17.01.058

    Opinions expressed are my own and not necessarily those of my employer

  • Run a batch process on your older files with the key-in "Convert AcisToParasolid All" that has worked okay for me.  That said... I saved a backup of the old geometry before doing running it just in case it destroyed or corrupted the old data.

  • 0 AcisBodies converted.
    But did highlight that I have NEVER opened these 3rd party files in CONNECT EDITION, so selected current Workspace.
    THX.

    Greg Smith

    Microstation 10.17.01.058

    Opinions expressed are my own and not necessarily those of my employer

Reply Children
No Data