I guess I was expecting that the "save as" command would create a duplicate, fully self contained ConceptStation project.
However, what I have noticed is that the terrain model is not copied to the new project and repathed accordingly. Rather the link to the terrain.3sm in the parent project is maintained in the child project. This dependancy has the potential to be problematic if the parent project is removed / altered / deleted.
Work around seems to be to recreate the terrain in the child project as whilst I can physically copy the terrain.3sm to where it should be in the child project I can't find a way to repath the terrain link from within ConceptStation.
Would appreciate confirmation if this is what others have observed and whether it is what Bentley intends.
Hi Grant,
3sm terrain files are not copied for various reasons including :
- Can be very large.
- Can be on a server.
- Can be shared amongst multiple .dgndb files.
The idea is if you are using the same terrain for multiple projects/options you should probably use the same terrain.3sm file and avoid recreating new one for each .dgndb.
This is why there is a field (see Terrain file location below) to specify the location of the terrain file.
Also you can Attach an existing terrain file to a new .dgndb file if the project location is the same.
So if you want to change the path just delete the terrain model, move your .3sm file, and reattach it.
HTH,
Mathieu
Answer Verified By: Grant Stewart