For all changes see the Release Notes section on the Community home page.
Date when discovered YYYY/MM/DD |
From version |
Product |
Description |
Fixed in version |
2019/08 |
21.FP4 |
NP Road |
3D results might look strange when using boundary to Centerline multiple times on both sides of the road. |
21.FP4b |
2019/08/12 |
21 |
NP Road |
Quantity report with limitation with from-to chainage fails when using the summary function or “No sectioning”. |
21.FP4b |
2019/06/06 |
21.FP4 |
NP Road |
Errors in the conversion file for intersection task gives wrong/or lacking result features: * Not all breaklines are produced * Result surfaces missing attributes
All surface geometry and the extent of the intersection is still correct, but missing some lines. The main challenge for the user will be wrong textures and presentations (Default, Basic3D, Sketch). |
NP21.FP4a |
2018/05/09 |
21 |
GUDB |
Not supported in NP21. |
21.FP4 |
2018/11/02 |
21 |
NP GeoSuite |
If an import task for a GeoSuite projects is edited and finds a new method for a Borehole sometimes it ends up with errors in validation and with two identical methods. Way around is then to delete the existing method/object and then to revalidate. |
21.FP4 |
2018/05/09 |
21 |
NP Road |
Buildtime for road models are more timeconsuming than before. NP21.FP2: Faster than previous versions of NP21. NP21.FP3: Even faster with regards to Finish/Cancel buttons. NP21.FP4: Further improvements on step 3, especially for bigger roadmodels. We consider the calculation time as acceptable. |
21.FP4 |
2019/01/28 |
21 |
NP Road |
Quantity report crashing in situations where the 3D-results are not created or solids are selected to not be included in the roadmodel build. |
21.FP4 |
2019/03/12 |
21.FP3 |
NP Road |
Drawing Longitudinal Profile to CAD from non-reserved tasks causes issues. * AutoCAD crashes. * Roadtask is not able to build afterwards, even after reservation.
Temporary solution 1 (recommended): Extract the roadmodel via PARAM-file or roadmodel files and create a new task.
Temporary solution 2 (recommended): Disconnect the local dataset and download a fresh dataset. Reserve the task and continue with the work.
Temporary solution 3 (for advanced users): Requires reservation of the task (IMPORTANT). - On your local dataset, find the project files and the roadmodel files for the task with the error. - Delete the *.$$i-file. - Check the read-only on the *.DMI-file. - Release the read-only on the DMI-file by unchecking the checkbox. |
NP21.FP3b |
2019/02/14 |
21 |
NP Road |
Quantity report can show very large or small values if the boundary or boundary alignments start/end in the same chainage as the start/end chainage of the road model. |
NP21.FP3b |
2019/02/12 |
21 |
NP Road |
Apply-button in dialogs or building cross-sections from the Cross-section Viewer will lead to crash when a 3D Presentation with transparency for the active road is in use. Temporary solution: Close the 3D Presentation. |
NP21.FP3b |
2018/11/20 |
21 |
NP Road |
Combination of viewing 3D Presentation with transparency for the active road task being build may lead to a crash in some situations. Temporary solution: Don't show the 3D Presentation when building the road task. NP21.FP3: Partly fixed for NP21.FP3. |
NP21.FP3b |