If you view a lot of IFC files in Tekla BIMsight, you may find that the cache or storage folder fills up quite quickly. If this is in its default location of \%localappdata%\Tekla\Tekla BIMsight\ then you could use up valuable space on your SSD.
We can easily move this folder using symbolic links. In the script below, we:
check the default directory exists, and if so rename it
make a symbolic link to a new target directory, in this case I have used E:\TeklaBimSight
make the new directory if necessary
copy existing contents to the new directory
To use the script:
Close Tekla BIMsight
Copy text from the script into Notepad and save as CMD. Modify the target directory to your preference
Save the script with CMD extension
Right click and Run As Administrator
Open BIMsight and confirm all is working ok
Optional: delete the bimsight.old directory to cleanup
if exist "%localappdata%\Tekla\Tekla BIMsight" rename "%localappdata%\Tekla\Tekla BIMsight" bimsight.old
mklink /d "%localappdata%\Tekla\Tekla BIMsight" E:\TeklaBimSight
if not exist E:\TeklaBimSight MD E:\TeklaBimSight
robocopy /mir %localappdata%\Teklabimsight.old E:\TeklaBimSight\
Tekla has issued an XML file containing preset IFCsettingsforexport to Revit, specifically for Coordination. In some cases, this may already be available on your system, but in other regions you may have to install it manually.
Unzip the XML into this folder on all PC’s running Tekla Structures:
Note: you may need to adjust the above path to suit your Region
Once this file is included in the folder mentioned above it will be available in all projects. When the user goes to File – Export – IFC they will have a pre-saved setting named “RevitCoordination”. The user simply Loads that setting and exports the parts needed.
This “RevitCoordination” setting also is setup to export additional property sets for Design Workflow data that is entered into the member properties (ie. Beam, Column etc.) in Tekla Structures.
A document was recently released that essentially describes differences in the way that Tekla and RST respond to changes in a linked architectural model. This document doesn’t really take into account the other benefits of working in a completely Revit environment – not having to convert to and from IFC, tagging through links, scheduling, bidirectionality, and so on (I don’t feel a need to keep listing reasons 🙂