- Known issues
- Good to know
Texture Problem with imported Rhino files
Affected version: 18, 19 & 20 | Severity: workaround applicable | ID: 206277
No textures are displayed on Rhino Imported NURBS defined surfaces in ARCHICAD.
The textures are actually visible only probably the UVW mapping of the surface is not correct, therefore ARCHICAD is stretching of the textures is too big. ARCHICAD is stretching the textures based on the NURBS UVW mapping defined by Rhinoceros. If the mapping is not set up correctly in Rhinoceros then the texture applied to the surface will not be displayed correctly in ARCHICAD.
To have a better texture result, use the Reparameterize command to such surfaces to define the mapping to a more realistic value.
Weird shadows on elements imported from Rhino
Affected version: 18, 19 & 20 | Severity: workaround applicable | ID: 181420
Sometimes strange shadows appear on elements imported from Rhino. This happens because Rhino can’t divide the surfaces to triangles correctly.
Workaround: Turn off the Smooth edges in the Settings dialog of the Rhino object. This results in lower quality surfaces, but without weird geometric singularities.
It is not possible to snap to Rhino imported objects (GSM & LCF) in Floor Plan view
Affected version: 18 & 19 | Severity: workaround applicable | ID: 175850
Note:With the Rhinoceros import/export Add-on it is possible to snap Rhino imported objects.
On the floor plan it’s not possible to snap to different parts of the Rhino imported Library Part.
Workaround: Temporarily explode the object in 2D while keeping the original object, use the 2D elements for snapping. If no further editing is needed the 2D content can be deleted.
Using hotlines of Rhino imported objects slows down ARCHICAD
Affected version: 18, 19 & 20 | Severity: workaround applicable | ID: 197036
Turning on the ‘Show hotlines’ 3D View Option of Rhino imported objects can slow down the 3D navigation performance of ARCHICAD in case of large projects.
Only use the ‘Show hotlines’ option if you need to snap other elements to the Rhino object in 3D. If not used, turn it off.
Good to know
Move/rotate Rhino objects imported with LCF file gets returned to the original location on LCF Update
If objects imported via an LCF file are moved/rotated in the ARCHICAD model, and they get updated with LCF Observer, all elements will be positioned back to the original location of the first import.
Workaround: Place the LCF file and the objects in a new file and hotlink this file into the Master plan. It can be freely rotated or moved here.
If an update needed because the Rhino model changed, simply open the holtink project, update the model in it’s original location, then Update the hotlink in the master file.
Updating LCF files in a Teamwork project
In a TeamWork project if a user would like to Update the model which uses the LCF files, they have to reserve all Library Elements which the LCF file contains, otherwise this error message will appear:
To be able to update the Library Container File’s elements:
- Select all the affected elements via using the Find&Select tool.
- Reserve them.
- Use the LCF observer to Update the Library elements.