As part of our plugin development of a Cross Referencing solution, I’m discovering what appear to be a number of bugs relating to the Import function.
The following is what I’ve reported, but I’d appreciate what you make of them and if you too have observed them:
IMPORT SKP BUGS REPORT.
We are attempting to build a workflow that will make SU / LO a viable end to end alternative to Revit and Archicad for medium sized, team based Architecture offices like ours.
This requires that team members can work collaboratively with SU by cross referencing each others models.
(I am aware of Trimble connect’s functionality. It is not a viable production environment solution - please contact me for details if you wish.)
We rely on the File / Import functionality as part of this.
This functionality is not performing consistently.
When File / Importing an SU file, the contents of the source file are made into one Component, which is named after the file name.
In the receiving file, the Import appears as an additional Component in the Outliner tray with the naming convention of ""
It also appears in the Component Definitions tray as “FileName”.
At Import, the Move tool is active, requiring the user to manually place the component in the desired location in the model space.
Issues / bugs Summary
1/ More than one Component is Imported from the source
2/ Wrong naming of Imported model
3/ Activation of the Move tool for placement of the Imported model is sometimes not offered - files are automatically placed
Issues / bugs Detail
Please see jpeg “shot 1”. This shows the receiving file where File / Import will be used. Note in the Components tray the 5 Component Definitions existing in this model prior to Import.
Now refer jpeg “shot 2”. This shows the source file, which is named “MC364_Building”. Note in the Components Tray, “component#82” exists.
Now refer jpeg “shot 3”. This shows the receiving file after the Import has been executed.
There should only be one additional Component, namely “MC364_Building”.
However, there are two Components; the expected, as well as a ‘rogue’ "component#82
Please see jpeg “shot 4”. The highlighted Component is the Imported Component. The file name of the source is “1_CONTEXT.skp”.
The expected naming is therefore “<1_CONTEXT>” in Outliner, and “1_CONTEXT” in the Component Definitions.
Note however that the Component has been arbitrarily named “<Group#689>”
It is not predictable which source files will be automatically placed in the receiving file, rather than requiring manual placement, however once the behaviour is demonstrated it is consistently replicable. I have a number of files I can send if required.
When a team of people are Cross Referencing files into their model space in a production environment, the behaviour of the Import function must be reliable to give confidence that co-ordination mistakes don’t happen on live projects.
We need confidence to establish our production workflow exclusively in SU/LO or we must reluctantly join those using Revit or Archicad.
Interface refuses upload.
Here are links: