In addition, I found the axis direction for sectioning in Forge Viewer is opposite to that in Navisworks. By these clues, we firstly need to get the model offset which Forge has aligned with. So if using distance value of Navisworks to set the clip planes in Forge Viewer, it will be wrong. In Forge Viewer, after the model is placed by setting center of bounding box of the model to WCS origin. In any case, the distance in XML = vec3f.x * (X value in UI ) + vec3f.y * (Y value in UI) + vec3f.z * (Z value in UI) If the plane is rotated and becomes to custom, the related param will look like: After export the viewpoint, the param in XML will be: Only the Y+ (0,1,0) value can affect the sectioning.

in the sample model ClashTest.nwd, Plane 1 is enabled. The sectioning planes align with the XYZ of the origin. One source model might probably be designed far from the WCS origin. After some investigation, I found some tricks with the mapping. The sectioning results are not same to those in Navisworks. However, using the same parameters from Navisworks XML, the planes are not correct in Forge Viewer. In some workflows, we need to map the planes of Navisworks viewpoints to Forge Viewer. įorge Viewer also provides the ability to set sectioning planes. This XML also contains data of camera of this viewpoint, which you can map with Forge Viewer (please check Load XML of Navisworks Saved Viewpoints to Forge Viewer Cameras).

Each item indicates if this plane has been enabled, and corresponding param: direction and distance. It contains the sectioning planes collections (6 planes). By saving and export SavedViewpoints, we can get the params of the sectioning planes. Navisworks provides the ability of Sectioning to place plane or box to create cross sections on the model in a 3D workspace.

Autodesk navisworks viewer for mac