Warning of more than 10.000 components when creating an issue

Warning of more than 10.000 components when creating an issue

Viewpoints with thousands of components can be slow to publish, download and to lookup in the model. We advise you to limit the number of linked components in a viewpoint. For this reason you can choose to link visible components and/or selected components. Small viewpoints are lightweight and fast. To prevent you from creating large viewpoints by mistake we have built in this warning.

When no components are linked to a viewpoint the whole model is shown. In combination with the use of clipping planes you can create small viewpoints with good insights in the issue.


    • Related Articles

    • Warning of more than 25.000 components when zooming to the viewpoint of an issue

      Some applications using BCF can create viewpoints with an extreme number of components. This can seriously effect the practical use of BCF and BIMcollab Nexus. For performance reasons we have added a warning when (too) many components are associated ...

    • Why are components not stored in a viewpoint?

      In Tekla, components can be part of an assembly, to easily select them as a group. These assemblies do not have the same reference ID as the components they contain. If an assembly is selected as a whole and linked to an issue, the BCF Manager will ...

    • Why are components that are visible not stored when I create an issue?

      In Tekla, it is currently not possible to automatically save visible components in an issue. You can either save the selected components or no components. The best way to link components to an issue, is to first select the components that need to be ...

    • Why are viewpoint components missing after an import?

      When issues are imported, Solibri builds a new viewpoint internally. Any components referred to from the viewpoint which are not present in the currently loaded models will be discarded, and will not be visible in the viewpoint. This can be the case ...

    • Why does the issue numbering in Solibri differ from BIMcollab Nexus's?

      Issue numbering in versions prior to Solibri 9.10.8.34 can differ from those synced from BIMcollab Nexus. In this version a new connection option has been added that correctly synchronizes the index numbering from BIMcollab Nexus to Solibri. Change ...