Render the project
The render farm is not responsible for the result of the rendering if the instructions for the preparation of the project have not been followed properly. We would also want to avoid the situation in which our specialists have to interfere with the project file, to correct and configure it.
2.1. Before sending the project to the final rendering, the manager can make a test preview of the IPR. To do this, you need to pick demonstration frames, and we will send you images for approval.

2.2. If the previs looks correct, you should approve it for the manager, and they start the final rendering. You will be notified about that in a message.

2.3. If the previs reveals any issues, you are given access via TeamViewer (access time is included in the free test for 30 minutes). It is important to check the project following the instructions and to make a previs.

2.4. When the result is satisfactory, you save the project and disable TeamViewer. Then you notify the manager that you are ready for the final rendering.
2. Preview
3. The final result
1. How the rendering takes place
1.1. For optimization and rendering speed, the frames of your project are divided into parts (tasks). Each task is rendered simultaneously by a separate server (which is free at the moment). As a consequence, the output frames may appear in a different sequence.
The scheme of splitting the frame-range into tasks
Since the scene is being rendered on several servers, it is necessary to cache parameters, pathologies, etc. More details about this can be found in the section "Prepare the project".

1.2. Rendering one task consists of several stages indicated in the diagram. The time taken to prepare and save the scene depends on its complexity. Frames in the project have different loads, which can also increase or decrease the render time. This time cannot be predicted and included in the calculation, therefore, the calculator's forecast and the actual render time may differ significantly. But the calculator will show you a rough estimate.
Rendering steps for each task
3.1. When the final rendering begins (not the test), you will receive a notification from the manager. After that, it is highly recommended to be in touch and promptly check the finished result.

3.2. If something is wrong with the result, you have to quickly inform the manager about it. In such cases, we provide a free test rendering for 30 minutes (includes a setup via TeamViewer). If the rendering time exceeds half an hour, and you do not make a signal to stop, then the payment counter turns on.
4. Fixing bugs in the project
If necessary, you can make changes to the project, then you need to inform the manager about the corrections and stop the current render if necessary. After that, you need to save the file (file-save incremental) and specify the path to the scene file to the manager. Change the iteration index in the output path ./out_01/$prj/

Moving and deleting files. Before starting rendering, you can replace and move files, create new folders. In the process of rendering, it is strictly forbidden to move, delete, etc. anything from the project, you also cannot move and delete render files in the out folder.