Good morning Community,
sometimes we've got problems with triangulation in InRoads in our company, it throws the message "Triangulation halted. ..." and I know that it's a known issue descriped in http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/triangulation-halted.aspx. But unfortunately we're not able to solve the issue as it's descriped in the article. The problem occurs irregular and there seems to be no visible problem with our geometries in the DesignFile.
Some testdata you'll find attached. I uploaded a DesignFile which is the source of the DTM I attached as well. Furthermore I added some screenshots of my DTM import options and the error message itself (for both configurations listed below).
What I tried so far is altering tolerances in InRoads Project Options, copying a part of the DTM that's corrupted into a new surface, importing the geometries in different ways (selection, by level or fence), using the extended data check option for triangulation and using the Resolve Crossing Segments feature. But all in all it was not successful, the error still occurs.
In my current version of InRoads the error message points to the location where the issue occurs, but in later versions it just says "No point found" and that's it - without any hints - that's really unsatisfying.
I tried to test in the following two setups:
Configuration 1: Intel Xeon CPU 5160 Microsoft Windows XP SP3 Microstation SS2 08.11.07.443, InRoads 08.08.00.46, Regional setting: Germany (but with . as decimal separator) all files are stored locally
Configuration 2: Intel Core i7 3770 Microsoft Windows 7 SP1 Microstation SS3 08.11.09.357 InRoads SS2 08.11.07.566 Regional setting: Germany (but with . as decimal separator) all files are stored locallyI hope someone may provide a solution for that issue, since we need the DTM in our business process.
Thank you in advance,
Maik Schulze
Thank you all for the testing, importing by level worked for my test data in my set of configuration but the other options like single element or fence are still failing. Defining the blue lines as contures doesn't matter for that issue, the error is still there.
I'll call Bentley InRoads Support again if the issue occurs again.
But does anyone know an option to get the detailed error description in InRoads SS2 like it appeared in former versions? In the past we had the chance to spot the point of the issue since coordinates have been displayed. Now it tells me "No point found". The messages I mean are attached to my initial post.
Thank you all for support!
Maik