PDF Export RSS - Latest News

Known issues

Novapoint Base


Conversion rules that come with the new import routines require the latest feature type registry. For Quadri models created before FP5, use the following workaround (single user models): Create a new Quadri model with latest feature type catalogue. Use Insert QG4 to insert your Quadri model to the new empty model (with proper feature type catalogue). Now you can import IFC files to your model.

IFC import

The IFC objects must be geo referenced in the IFC file to succeed with correct location.

If you receive IFC files of large complicated buildings, you may experience that this uses lot of computer resources. To reduce memory use during import, run the file through Solibri IFC Optimizer before importing it to Novapoint.

If you want to import more than the buildings outer volume, you must create a new conversion file.

IFC files are very diverse and include a lot of information. Using a conversion file to import everything from IFC to Quadri will lead to a large model. It is important to be selective when deciding what to import. Import only what you need in your project.


The Collection task was introduced in NovapointDCM 19.2XFP5. Earlier versions cannot use this task type. If you start using this task type, all other who uses the same model must update to NovapointDCM 19.2XFP5 or newer versions. If model is opened in earlier versions, the program will not recognize these tasks and when recalculating tasks with Collection task as indata, the result will not be as expected.


INFO: The new Collection task is now recommanded to use to collect tasks and features as calculation base. The collection task will automatically update result when the indata tasks changes. Ground and Sub Surface tasks will from this version always create new result feature when recalculated. If these tasks are input to a Group task, the group task must also be updated evry time Ground surface and/or Sub surface tasks are recalculated. Create a Collection task to replace the Group task and this problem is avoided.

Ground surface/Sub surface

Keep existing TIN structure
  • Even if neighbour surfaces do not seem to overlap, one can in process info get the message that the surfaces or boundaries are overlapping. This is because the boundaries of two neighbours must have the exact same points along their boundaries.
  • If you have selected this setting and a TIN that is input to calculation has holes, then other indata for the calculations that are inside the hole will not be included in the calculation
Multiple outer boundaries

When user selects multiple outer boundaries, these cannot overlap. If they are overlapping, user get the message Overlapping triangle modedels. You can right mouse click the message and select Go to location to see where the surfaces are overlapping in the active window:

Problems with Ground surfaces and Sub surfaces as calculation base

Tasks that uses Ground surface and/or Sub surface tasks as calculation base (e. g Move vertically, Extrude, Road model,…) can in some cases not find terrain. Especially this can happen when the Ground surface/Sub surface task is created in earlier versions of NovapointDCM. Try to recalculate the Ground surface task. If this does not help, create a duplicate of the Ground surface/Sub surface task and use this further as calculation base. In order to create a duplicate of the task, you can use the arrow beside Features-button and select to reuse the queries from the previous task:

Output feature - Not possible to select result feature type

In the tasks Ground surface, Extrude and Sweep is not possible to select Output feature type when the Novapoint application window is minimized as shown in image:

When you point to select feature type, it is not possible to make choice and you cannot continue. A workaround is to maximize the application window, or change to higher resolution so that no tool is minimized in the Novapoint application. When it looks like the image below, you can select output feature:

Novapoint Tunnel

  • Ditches modeled by the water and sewer module and referenced into the road model are not always handled correctly in NP Tunnel. The functions 3D-drawing, volume calculation and LandXML export all give wrong results in some situations. This will be corrected in later releases
  • The function for exporting/importing the cross-section geometry in the crossing tunnels definition dialog crashes. This will be corrected in the next release.
  • Background images don't show up in the AutoCAD drawings produced by the function “Geology and Rock Support Drawing Generator”. This will be corrected in the next release.
  • The LOFT-function is much slower in AutoCAD 2015 than in previous versions of AutoCAD. We have reported this error to Autodesk who admits that this is an error. They can't tell when the error is fixed. It was not fixed in update 2 for AutoCAD 2015.

en/np/release_notes/np1920/np1920fp5/np1920fp5_known_issues.txt · Last modified: 2015/01/05 11:23 by vn_no_sfi