TUTORIAL / CINEMA 4D
Save-At-Render
setup and shortcuts.
Save-At-Render setup is about making a useful save step part of your Cinema 4D render workflow. The original video shows how Alpha Pixel’s three scripts can be assigned to render shortcuts, so the scene-saving action is easier to remember.
This guide focuses on installing, checking and accessing the scripts. For the individual script behavior, filenames and output folders, use the Save-At-Render script reference. The download is a legacy release; read the compatibility note before replacing a working render shortcut.
01 / EXPLORE THE WORKFLOW
Start with
a small render test.
The original idea was to keep a scene copy with the render output, making it easier to return to the scene state behind a finished image. Installing the files alone does not change Cinema 4D’s normal render commands: you need to run the matching Save-At-Render script.
Before testing, save a simple project and set a writable output folder and filename in Render Settings. The original instructions call for both Save options to be enabled. Check the saved scene copy as well as the rendered image before treating the setup as part of your routine.
Important correction to the old instructions: a Picture Viewer or Team Render action can still start when the scene-saving conditions are not met. Seeing the render begin does not prove that a scene copy was written. Verify the file on disk and reopen it.
02 / EXPLORE THE WORKFLOW
Choose the matching
render action.
Picture Viewer: use SAR_PV for the local Picture Viewer action.
Team Render: use SAR_TR for Team Render to Picture Viewer.
Render Queue: SAR_RQ opens the queue and adds the saved scene; it does not start the queue.
03 / EXPLORE THE WORKFLOW
Save-At-Render setup:
make it easy to reach.
1. Install and identify the scripts
Extract the download and choose the folder for your operating system. Follow the Cinema 4D script installation guide, then identify the Picture Viewer, Team Render and Render Queue entries. Keep their names distinct so you know which action you are about to launch.
Maxon’s Script Manager guide explains how Python scripts are managed and provides a shortcut button that opens Command Manager for the current script.
2. Test before assigning a shortcut
Run the appropriate script on the saved test scene. Use a small image size and short range so the test is quick to inspect. Confirm the render action, locate the extra scene file and open that copy to check it contains the expected project state.
If the script stops or reports an error, investigate it before changing your normal render command. The original Windows Picture Viewer script contains Python 2 print syntax and needs updating for Python 3. Current-release compatibility has not been verified.
3. Assign a deliberate keyboard shortcut
Once the script works in your installed version, use Command Manager to select it and review the shortcuts already assigned. Enter your preferred key combination, check for conflicts, then assign it. Test that combination on the same small scene.
Maxon’s Command Manager reference covers keyboard assignments and command palettes. You can use a palette button instead if you prefer a visible reminder. The video demonstrates the original shortcut workflow; menu labels can differ in later releases.
04 / EXPLORE THE WORKFLOW
Get the files.
Keep normal backups.
Find Save At Render in the shared freebie library. Confirm your newsletter signup to receive access, or open Freebie Downloads with the current password. The script reference page explains the supplied files and their limits in more detail.
Continue saving your working project normally. This workflow does not collect every texture or cache, create an automatic history of uniquely numbered versions, or guarantee that a render and its scene copy both succeeded. Give revisions distinct output names when you need to preserve them separately.
05 / GOOD TO KNOW
Setup
questions.
Does installing the scripts activate automatic saving on every render?
No. The save step runs through the supplied script. A shortcut or palette button is a convenient way to call it, but normal Render commands remain separate.
Should I overwrite my usual render shortcut immediately?
Test the script first. Confirm the extra scene file, then try a separate shortcut before deciding whether to replace a familiar command.
Why did the render start without a saved copy?
Check the output path and Save settings. The render command can still run when the script’s scene-saving checks fail, so inspect the output folder rather than relying on the render window alone.
Does the queue option render immediately?
No. It opens Render Queue and adds the saved scene. Review the job and start the queue when you are ready.
Is this download ready for every current Cinema 4D release?
No current compatibility range has been established. The Windows Picture Viewer script needs a Python 3 update. Keep your normal render workflow available until a compatible version has been tested.
