In 3Delight Display' Image View
When launching a rendering, you will be presented a progress indicator in the image view after a few seconds (if the image does not immediately appear). The indicator goes through two stages:
Syncing… | It indicates that scene data is being uploaded to the cloud. (There is no charge for that process.) |
Starting... | It indicates the rendering process is in the initialisation phase, including reading and parsing the scene. |
In the future, we may report the Starting stage in two steps for a more detailed update. If so, the indicator would go through three stages:
Syncing… | It indicates that scene data are being uploading to the cloud. (There is no charge for that process.) |
|---|---|
Starting… | It indicates the rendering process is in the initialisation phase. (This can take from 1 to 30 seconds.) |
Parsing... | It indicates the rendering has started parsing the scene (reading and building the data structures for the ray-tracing algorithm). (The duration of this step in entirely dependent on the size and complexity of the scene.) |
In 3Delight Display's Sidebar
For an image:
In the Cloud tab of the Sidebar, the STATUS column of the Activity tab have the following indications:
Syncing | It indicates that scene data are being uploading to the cloud. (There is no charge for that phase.) |
Starting | It indicates the rendering process is in the initialisation phase (i.e. commissioning of ressources and starting the rendering application). (This can take from 1 to 30 seconds.) |
Parsing | It indicates the rendering has started parsing the scene (reading and building the data structures for the ray-tracing algorithm). |
Rendering | The rendering has started to compute pixels. |
Completed | The rendering finished normally. |
Cancelled | The rendering was cancelled by the user. |
No service | The rendering was cancelled due to no service availability (after a short while waiting). |
Stopped | The rendering was stopped due to no sufficient credit or due to the lack of cloud usage authorisation. |
Aborted | The rendering finished abnormally (eg. crashed). |
| The following STATUS only applies for images as part of a BATCH rendering of a sequence. | |
Waiting (service) | The rendering process for that image has not started yet. It is waiting for ressources to become available. This should rarely occur. Note: this is unlike the No service status for single interactive image rendering. In Batch rendering of a sequence, it will wait indefinitely for the service to become available. |
Waiting (spending) | The rendering process for that image has not started yet because if it did, it would exceed your spending rate limit. It is waiting for other images to be completed before starting. |
Waiting (download) | The rendering process for that image has not started yet because if it did, it would exceed your download speed capability. (You already have other images rendering and have reach the limit of your download bandwidth.) |
For a sequence of images:
The status for a sequence of images as shown in the activity represent the status of the underlying images. Since these images can be in very different statuses, we select the most indicative status to report. The selection is made with the following logic:
- Will look if any of the images are currently in the following status: Syncing, Starting, Parsing, Rendering. If so, it will report the most advance stage among these. As a result, most often, Rendering will be indicated.
- Otherwise (it means there is no activity), it will look if at least one image is in one of the Waiting status. If so, it will report as such.
- Otherwise (no activity and nothing waiting), it will look for images No service status and report as such if any.
- Otherwise, it will look for images in the Completed status and report as such if any.
- Otherwise, it will look for images in the Cancelled status and report as such if any.
- Otherwise, ???