Trimble
PDF Export RSS - Latest News


KNOWN ISSUES

We will here list errors that is considered to be unfortunate for the user.
For the full list of changes, see our Release Notes.

For errors in the roadmodel calculations go to errormessage

Check the Archive for closed cases older than one year.

ACTIVE CASES

KNOWN ISSUES IN NOVAPOINT 19 / 20 / 21
Date
YYYY/MM/DD
From
version
Description Fixed in
version
2017/10/09 ALL Sight distance calculaton gives error about Cross-section calculation insufficient for roads build shorter than 100m.
Temporary solution: Extend the road in start or end and use boundaries on left- and righthand side to the centerline.
2017/01/05 ALL Error in deepblasting when it hits the rock surface in two or more places in the cross-section. Deepblasting surface is then create above the rock surface. Quantities for deepblasting is also wrong.
ALL Top soil or vegetation removal above soft soil removal can give varying results. Check the quantity calculations and mass hatches in cross-section drawings to indentify errors.
KNOWN ISSUES IN NOVAPOINT 21
Date
YYYY/MM/DD
From
version
Description Fixed in
version
2020/03/01 21.FP4? Roadmodel results may look choppy. Happens when combining roadmodel boundary to centerline when cross-sections are overlapping (because of sharp turn on alignment) and the following cleanup that we do to the results.
Temporary solution: Change the boundary to alignment to also have a distance of 1cm or similar.
2020/01/17 21.FP4 Rock <1m not included in summary report.
2019/12/19 21.FP4 Wrong area on pavement layers can occur in quantity report when using the rehab-pavement function.
2019/06/28 21 Vegetation and topsoil removal using vertical-vertical does not work. No material is removed and no fill is put back in.
2019/05/28 21.FP4 Errors in 3D results when road model goes in circle and crosses itself.
From FP4a: Solution is improved when the road is completely crossing itself, but still not when it has a minor overlap in the results.
2018/05/09 21 Deep blasting endsurface method 3 always goes to the last ditch surface.
Temporary solution: Use endsurface method 2 instead.
2018/05/09 21 Draw roadmodel missing possibility to draw contourlines.
Temporary solution: Draw out through a planpresentation in Base to CAD. Select roadtask and set the global filter on objects to Medium=On Terrain.
KNOWN ISSUES IN NOVAPOINT 20
Date
YYYY/MM/DD
From
version
Description Fixed in
version
2016/09/11 20 Error in sight analysis results.
NOTE: Sight analysis report is correct, and we see sightlines in the model, but when a not-approved sightline is found, the sightline does not have the correct direction/length.

CLOSED CASES

Date
YYYY/MM/DD
From
version
Description Fixed in
version
2019/08 21.FP4 3D results might look strange when using boundary to Centerline multiple times on both sides of the road. 21.FP4b
2019/08/12 21 Quantity report with limitation with from-to chainage fails when using the summary function or “No sectioning”. 21.FP4b
2019/06/06 21.FP4 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 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 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 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 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 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 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

Check the Archive for closed cases older than one year.

Last modified: 2020/03/13 10:38 by vn_no_dso