Bug fixInfrastructure Standards

LCD-13771, LCD-13773, LCD-13776
The TLcdIFCModelDecoder support for reading materials has been improved. The decoder now supports reading the material from the presentation layer of an object (IfcPresentationLayerWithStyle). Also support for reading the material from IfcFillAreaStyle, IfcColourRgb and IfcDraughtingPreDefinedColour has been added. In addition, when an unknown material construction is encountered in the IFC file, the decoder no longer assign a wrong material to the object, but instead logs a warning and assigns the default material.

Bug fixInfrastructure Standards

LCD-13770
The TLcdIFCModelDecoder now supports IfcProxy elements.

2024.1

2024.1.04

Bug fixInfrastructure Standards

LCD-13707
To improve the alignment with the other BIM formats, the metadata property containing the original binz file location (a source name property in a root feature) now holds only the filename of the entrypoint of the dataset, instead of its full path.

2024.1.03

ImprovementInfrastructure Standards

LCD-13703

The bim.converter.[bat|sh] commandline sample now has an additional flag to specify whether you want the output folder to contain the OGC 3D Tiles output: --tileset. By default, the flag is set totrue. To skip the OGC 3D Tiles output, set the flag to false by adding --tileset=false or --no-tilesetto the commandline.

Note that disabling the OGC 3D Tiles output is only useful if you enable the -g|--geojson flag to generate geojson output. If that flag is not set to true, and the --tileset flag is set tofalse, then no output will be generated and an error message will be printed.

Bug fixInfrastructure Standards

LCD-13694
Fixed an issue where the TLcdIFCModelDecoder did not properly handle IfcBooleanResult subtractions in some cases, which could result in empty .b3dm files generated by the TLcdOGC3DTilesModelEncoder.

2024.1.02

ImprovementInfrastructure Standards

LCD-13450
The TLcdRevitModelDecoder now uses the Shared Coordinates of a Revit file. This allows to correctly geolocate Revit datasets using standard model references.

ImprovementInfrastructure Standards

LCD-13690

Improved the support for DWG line weights according to the DWG specification.

We now display the line weight of the ILcdDWGShape model elements, taking into account the actual dimensions of your screen. Additionally, if TLcdDWGPolyline2D and TLcdDWGCompositeCurve have a non-zero line width value, that value will be converted to a world-sized line width.

These changes also improve visualisation of a DWG dataset via a WMS service in LuciadFusion.

Line weight visualisation
Line weight visualisation on a standard 96 DPI monitor.

Upgrade considerationInfrastructure Standards

LCD-13663
The myVRDatakitConverter library has been upgraded to version 2024.10.75992. It is used by the TLcdRevitModelDecoder and the TLcdNWDModelDecoder. This upgrade brings the following new features and enhancements:
  • Fixes a decoding crash for some Revit files
  • Contains several improvements to the generated metadata for Revit and Navisworks files

2024.1.01

ImprovementInfrastructure Standards

LCD-13662
Fixed an issue where the line weight of objects in DWG datasets was erroneously rounded to 0.

Bug fixInfrastructure Standards

LCD-13541
TLcd3DTilesProcessorBuilder: fixed an issue that could cause points to get moved far away from the mesh, which resulted in unexpected extruded triangles and overly large bounding boxes.

Bug fixInfrastructure Standards

LCD-13631
TLcd3DTilesProcessorBuilder: fixed an issue where material colors were applied multiple times, causing textures to become darker than intended. This happened if a texture was referenced multiple times in different materials.

Bug fixInfrastructure Standards

LCD-13369
TLcd3DTilesProcessorBuilder: fixed a possible performance degradation when processing an OBJ file with textures.

Bug fixInfrastructure Standards

LCD-13674
Fixed a bug where the TLcdBinzModelDecoder could generate wrong material PBR color values for the output 3DTiles dataset for some input data.

Bug fixInfrastructure Standards

LCD-13635
Fixed an issue where the TLcdIFCModelDecoder did not properly handle IfcBooleanResult subtractions in some cases, which could lead to missing objects in the geometry model.

2024.1

New featureInfrastructure Standards

Visualization of a Navisworks file in LuciadRIA, processed and served using LuciadFusion's OGC 3D Tiles service
Visualization of a Navisworks file in LuciadRIA, processed and served using LuciadFusion's OGC 3D Tiles service

Added support for the Autodesk Navisworks data format. Autodesk Navisworks is a BIM software tool for architects, engineers, and construction professionals to combine and review 3D models created by other software packages, such as Autodesk Revit, AutoCAD, and others.

For more details, see the Autodesk Navisworks entry in the Data Formats documentation section.

New featureInfrastructure Standards

The TLcdIFCModelDecoder now supports decoding IFC files in the IFC 4.3 file format.

ImprovementInfrastructure Standards

LCD-12693
We improved the FeatureId shift when combining multiple Binz datasets using a *.binz.index file in the TLcdBinzModelDecoder. The resulting dataset will now no longer have huge gaps in the FeatureId range. The link to the original FeatureId is now also stored in the feature metadata as RenderId.

ImprovementInfrastructure Standards

LCD-12404
We enhanced the feature metadata for Binz files by adding the possibility to link back to the original data. We added (a) root feature(s) containing the original binz file location(s). Next to that we added a RenderId property, which is the original FeatureId in the original binz file. Both are especially useful when converting multiple Binz files into a single model using a *.binz.index file in the TLcdBinzModelDecoder.

ImprovementInfrastructure Standards

LCD-13534

Changed the log level for problems when decoding IFC, Binz, Revit and Navisworks datasets: if the input dataset contains objects that are incorrect (for example, a circle with a negative radius) or impossible to discretize (for example, a cylinder with zero height), this will no longer appear in the log as ERROR or WARNING messages.
This change affects all BIM data types: IFC, Binz, Revit and Navisworks.

The log level has been changed to DEBUG, so to re-enable the output you can change your log configuration accordingly. Refer to the Logging tutorial for more information.

Bug fixInfrastructure Standards

LCD-13584
The TLcdRevitModelDecoder failed to decode Revit files if the working directory was read-only.

Upgrade considerationInfrastructure Standards

We aligned the approach for feature metadata between all supported BIM formats. For Binz, this means the adjustment of the naming of the "minZ" and "maxZ" properties in the generated dataModel to "MinZ" and "MaxZ". This affects both the generated geoJson file and the WFS service for features of a BINZ dataset. You could be using the "minZ" and "maxZ" properties to allow automatic fitting to a feature. If you are using the "minZ" and "maxZ" properties in your code, you will need to adjust the property names to "MinZ" and "MaxZ".

Upgrade considerationInfrastructure Standards

The myVRDatakitConverter library has been upgraded to version 2024.10.75374. It is used by the TLcdRevitModelDecoder and the TLcdNWDModelDecoder. Without this upgrade, there is no support for the Navisworks format.

Upgrade considerationInfrastructure Standards

The commandline samples to create 3DTiles datasets for different BIM data types have been consolidated into one single sample:bim.converter.[bat|sh]. The previous samples all used the same syntax, which is now available on the new sample.
The sample provides a uniform way to convert these data formats: Binz, IFC, Revit and Navisworks.

The following commandline samples are no longer available:

  • decoder.binz.[bat|sh]
  • decoder.ifc.[bat|sh]
  • decoder.revit.[bat|sh]