Is there an OpenRoads Designer Version release schedule?

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.

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,

  Jan

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...?

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, stay with SS2

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. 

Neville, 

I think the whole Rail Alignment Geometry could be kept in one dgn file, But i would split the corridor model up into multiple section and separate dgns, probably start with 25-50km sections varying the sections depending on what the corridor crosses and interfaces with.

Neville, are you familiar with these techniques: https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/30090/video-corridor-processing-optimization-tips-and-techniques ? In my case, narrowing down the existing terrain has significantly improved processing time.