I am creating a deployment for IDSP 2014. Why isnt the "search paths and file locations" option available for Civil 3d?
It is there for AutoCad and a few others. If I set the paths in the AutoCad setup wll they be set the same for Civil 3D?
Did you ever get an answer (workaround) regarding the support file search paths for Civil 3D? if so, I would like to know your solution.
Please provide a little more information regarding the issue you're having with building the deployment. Also, attach any screenshots and/or log files.
As the OP stated the search paths and file locations aren't available to set when creating a deployment under Civil 3D 2014. If we set them in the Autocad section will they also set for Civil 3D?
Sorry Brandon, I was thinking of another post. lol...
No, Autodesk removed the ability of setting the resource paths with Civil 3D, so you'll have to do this after the installation. Also, the AutoCAD paths will NOT carry over into Civil 3D as they are separate applications.
As a recommendation, you could install Civil 3D onto your machine and make the neccessary changes to Options > File then export the profile or registry key (HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R20.0
Hope that helps.
After you've created the deployment for C3D in the folder .\Img\x64\C3D you have the C3D.msi and C3D-<deployment-name>.mst files.
You can load these two files in Orca (free MSI and MST editor) and adapt the .MST file for your needs. You can edit/modify all configurations, paths etc. you need.
When you create the deployment it is just what it also does. You put your settings in the setup dialogs and the setup program creates a .MST file to bring these changes to the C3D.MSI file.
If you export and import the settings manually after the installation, you have to do this for every user.
If you modify the MST file, these settings (additional paths, etc.) are automatically set every time the "per user" installation is triggered from your installation as in previous releases.
Download for orca msi editor:
A preview from the transformation of the C3D.MSI after a standard deployment: