I trying to setup a schedule for Openroads Designer software updates with my IT staff, but I no idea when the updates will be released.
Thank you. I guess i will just have to keep checking the software downloads.
Mike
A release was expected before end of 2019 but has been delayed. It should come soon.
jpln said:A release was expected before end of 2019 but has been delayed. It should come soon.
Thanks for the update!
It would be nice to have newer ORD version soon, because my experience (what I see or hear from my customers) is that ORD is far the worst piece of software that Bentley have ever produced. Many people complain MicroStation CE is slow crappy buggy and not usable software, but in fact it works fine ... ok, sometimes much slower than V8i, but for DGN only mid size project it's good enough. On the other hand, ORD typically crashes a few times per hour, halts for a second without any reason from time to time etc.
With regards,
Jan
P.S. My second wish, in addition to bug fixing, is to abandon confusing non standard naming. Where all other product teams use simple and clear <product> Update <X>, why civil marketing decided to use Release <something> Refresh <something> naming, that as I found out do not understand even their colleagues from other teams?
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
I agree that naming is sometime confusing. However, using same numbering than MicroStation could also confuse. OpenRoads U14 that includes a U12 platform (MicroStation). To my point of view, 2019-R1, 2019-R2, ... is not so bad. With some exception when 2019-R3 is released in 2020.
OpenRoads stability is greatly improving from version to version. 2019-R2 is quite good from my experience. Part also because of knowing better and better what OpenRoads doesn't like.
jpln said:I agree that naming is sometime confusing.
I have to say it's always confusing. It's subjective and personal opinion, but when I ask my customers for e.g. MicroStation or OpenCities version, they usually know it, but when we are discussing ORD issues, they typically do not. It's too long and not intuitive.
jpln said:However, using same numbering than MicroStation could also confuse.
My experience is that it's not so big issue, because whereas product name is important for user, internal platform version is something that typically CAD admins and developers take care about.
Regards,
To some degree I agree with you regarding stability but what is our main pain on the job which we have been working on for over a year is that we have number of files which to open takes 5-10 minutes, we have corridors which take to process even 30 minutes (the corridors are up to 4km long per DGN), and we experienced files which don't open at all or open with an error. So the time we gained at the beginning of the job is now wasted by unpredictable behavior of the software.
I have contacted Krzysztof offline and we are looking at some of the performance issues.
Simon Pegg
Bentley Civil Support
Krzysztof, do you think my 315km rail line is overly optimistic? ;-)
I've cut it into smaller sections but even 40km doesn't work. The annotation locks up, and the profile is so slow it is unusable.
There is a saying in English, "Biting off more than one can chew".
Maybe Jan is right...?
Neville du Plessis
Rail Design
Neville, stay with SS2
I do not recall the recommended "limit" but even Civil 3D recommends avoiding overly long corridors - breaking them up into smaller segments to avoid issues.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Krzysztof, I wish we could, but Bentley does not support SS2 anymore. So we run into any problems in the future ..... what then? My opinion is that Bentley should have continued to keep SS2 Windows 10 compliant. So if one does not migrate to ORD the problems in future only gets worse.