You can store and open Cinema 4D projects on a network drive. To work with them, your computer needs a reliable connection to the server and access to the project and any linked files, such as textures, caches, and XRefs.
A network interruption during saving can leave a project incomplete or damaged. We recommend working from a local copy whenever possible, especially with large projects or an unreliable connection. When you finish working, copy the updated project back to the network drive.
Avoid conflicting saves
Make sure only one person edits and saves a given Cinema 4D project file at a time. Wait until saving is complete before copying or synchronizing the project folder.
Recommended workflow
- Create a local working copy. Copy the project folder to a local drive. If assets are stored elsewhere, follow Collecting project assets below. Keep the original network copy until you have checked the local copy.
- Check the local copy. Open it and go to Window > Project Asset Inspector. Check the Absolute Path column for files still linked to the network; a green check means an asset was found, not that it is stored locally. Collect the files you need locally, resolve missing assets, and run a test render.
- Edit and save locally. Save to the local project folder while you work. Choose local folders for caches and render output as well.
- Copy the finished project back. Include any assets added while working. Wait until all saves and cache writes finish, then close the project to prevent further changes during the transfer. Copy the complete project folder to the network drive. Once the transfer finishes, check the copy before replacing an earlier version. You can leave Cinema 4D itself open.
Collecting project assets
Open the project and choose File > Save Project with Assets... to save a new copy with the external assets Cinema 4D can collect. Choose a location on your local drive. Where supported, Cinema 4D updates the asset links to use paths relative to the project folder, making the files easier to move together.
If Cinema 4D reports a missing asset, locate the file before continuing. Choosing No skips that file. Choosing Cancel stops the process but leaves any files already copied in the new folder. In either case, the folder may be incomplete.
If your project uses assets from an Asset Browser database and you need to work without access to that database, check these settings before collecting the assets:
- Open Cinema 4D's Preferences.
- Go to Import/Export > Cinema 4D (Save Project) and select Save Project Including Assets.
- Enable Copy File Assets to Texture Folder and Copy Node Assets to Scene Database.
- Close Preferences, then choose File > Save Project with Assets... to save the project and collect its assets.
These options copy file assets into the project folder and store Node assets inside the scene file.
Check for files that need separate attention
If an XRef scene references other files or contains additional XRefs, those files are not automatically collected when you save the main project with assets. Include them separately. Some files, such as GI caches, use absolute paths, so you may need to update their locations after moving them.
The Project Asset Inspector does not list assets used by tools, such as a texture in a sculpting brush. Check any tool assets you need separately, and test the collected project without access to the original asset locations if you need it to work independently.
How to find and relink missing assets
- Open Window > Project Asset Inspector.
- Clear any asset filters so the full list is visible, then choose Edit > Select Missing Assets.
- Choose Assets > Relink Assets...
- Select the folder that contains the missing files.
- Save the corrected project.
Relinking tells Cinema 4D where to find the files; it does not copy them. Use Save Project with Assets... afterward to collect them with the project. For missing Node assets, reconnect their database in the Asset Browser first.
If you need to work directly from a network drive
If your workflow requires opening and saving projects directly on a network drive, check the following with your IT team:
- Use a stable, low-latency connection. A wired connection is preferable for large projects.
- Make sure you can read the required assets and save files to the project, cache, and render output folders. You only need write access to a shared asset library if you change files in it.
- Make sure each computer that opens or renders the project can access its linked files at the paths saved in the scene.
Backups and Auto-Save
Save dated or numbered versions as you work, and regularly back up the complete project folder, including its assets.
Keep Auto-Save copies on a local drive
In Preferences > Files > Auto-Save, enable automatic saving and set Save to Folder to Custom, then choose a local folder. If you choose Project, Auto-Save copies go into a backup folder alongside the scene. For a project on a network drive, those copies will also be on the network.
If you still have problems
Try the local workflow described above. If the problem only occurs on the network drive, ask your IT team to check the connection, server, permissions, and file paths.
If it also occurs locally, keep the original file; copying a damaged project to a local drive will not repair it. For further help, submit a support ticket with the exact error message, your Cinema 4D version, and the result of your local test.
Comments
0 comments
Article is closed for comments.