Date: Tue, 19 Mar 2024 07:31:30 +0000 (UTC) Message-ID: <1530162755.18488.1710833490918@confluence-prod.c.chaos-bs-production.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_18487_1736311571.1710833490918" ------=_Part_18487_1736311571.1710833490918 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page provides answers to the most frequently asked question= s about Chaos Cloud rendering.
Chaos Cloud rendering is a software a= s a service (SaaS) which allows you to submit and render scenes with cloud-= based V-Ray. You can concentrate on designing and creating your scene, and = Chaos Cloud rendering will take care of installing and maintaining everythi= ng needed to run V-Ray, without hogging your hardware and software.<= /p>
The app is the connection between you= r scene and Chaos Cloud rendering, and it allows you to submit scenes to th= e cloud. Depending on your workflow, the client app can be started from the= 3D application you used to design your scene, or manually. If it is starte= d from the 3D design application, it will automatically load the scene you = are working on. If you start it manually, you will have to find and open th= e vrscene you have exported and want to render in the cloud. To start it ma= nually on Windows, open: "%appdata%\Chaos Group\Cloud\Clien= t\ccloud.exe". To start it manually= on macOS, open: /Applications/ChaosGroup/Cloud/Client/cclo= ud. To start it manually on Linux, = open: $HOME/.ChaosGroup/vcloud/client/ccloud.bin.
You can open and work with Chaos Clou= d rendering web portal and client app in the latest versions of Google Chro= me, Mozilla Firefox, Microsoft EDGE, Apple Safari and Opera browsers.
Chaos Cloud rendering supports render= ing still images and animations.
Chaos Cloud rendering can render scen= es using Progressive or Bucket render mode, depending on the scene setup in= the 3D application.
Chaos Cloud rendering support= s and renders scenes using the V-Ray CPU and the V-Ray GPU engines. Chaos Cloud rendering supports V-Ray GPU ren= dering running on CUDA and RTX enabled devices.
Chaos Cloud rendering support= s only versions V-Ray Next Update 1 (4.10.x) and above for V-Ray G= PU, i.e. any V-Ray GPU scene created with a previous version will be render= ed with V-Ray Next Update 1 (4.10.x).
V-Ray GPU jobs are rendered with GPU devices, but submitted scenes= should not exceed 16 GB of GPU memory. Else the jobs fail.= strong>
V-Ray GPU versions Next and prior run only in Bucket mode, hence any V-R= ay GPU Progressive scene will be forced to Bucket mode. For V-Ray 5 and onw= ards all submitted V-Ray GPU jobs are rendered only with Progressive m= ode! It is recommended to use Progressive mode when submitting V-Ray GPU jo= bs to Chaos Cloud rendering, as it runs faster than the Bucket mode.
The supported V-Ray versions are listed here. Each Chaos Cloud rendering job is rendered with= the latest publicly available build of the V-Ray version used to create th= e original scene, e.g. a scene created with V-Ray Next is rendered with the= latest publicly available version of V-Ray Next.
To start a render job, submit a scene= through the client app. If there are free resources in the cloud, Chaos Cl= oud rendering will start rendering your job. If there are no free resources= , your job will join a queue and will start rendering automatically when re= sources become available.
The output image types you will be able to download by rendering in Chao= s Cloud rendering are JPG and the file type you have specified in your scen= e=E2=80=99s settings. These settings are customized in the 3D application y= ou use for designing your scene. If you don=E2=80=99t specify anything in t= he 3D application, Chaos Cloud rendering will generate an EXR image beside = the JPG. If you have enabled the Include additional JPG output toggle in the Options page, Chaos Cloud rendering generates an additional high-quality JPG file for your output at no extra cost.
Yes, you can download the image at th= e current status of your rendering job. Bear in mind that Chaos Cloud rende= ring will generate the image type you have specified in your scene=E2=80=99= s settings in the 3D application. If you haven't specified anything, Chaos = Cloud rendering will generate EXR and JPG images as outputs for your job. I= f you have enabled the Include additional JPG output optio= n, Chaos Cloud rendering generates an additional high-quality JPG for your = output at no extra cost.
Chaos Cloud rendering is available fo= r all 3D applications supported by V-Ray via vrscene file export. Chaos Clo= ud rendering also integrates directly with V-Ray for SketchUp, Rhino, Revit= , 3ds Max, Modo, Blender, Houdini, Cinema 4D and Maya.
The Chaos Cloud rendering client app installer can be downloaded from the Chaos Cloud w= eb portal.
The Chaos Cloud rendering client app is available for Windows 64-bit, macOS 10.12 or later, = and Linux 64-bit.
When a new version of the Chaos = Cloud rendering client app is available, a notification= appears. Click on it and update the client app.
You can render up to 100 frames at th= e same time. If you want to increase this limit, let us know with a Support ticket or via the Chaos Cloud Feedback form.
Yes, there is a limit. For 30 calenda= r days, i.e. 720 hours, you are limited to downloading 25 TB of data. If yo= u hit this limit, you can always contact us through support and ask for a q= uota increase.
Yes. By default, our notification ser= vice will send you an email if your job status changes from active state to= one of the two final states: "Completed" or "Failed". You can unsubscribe = from these notifications from Chaos Cloud rendering portal options. Ch= aos Cloud rendering also has in-app notifications in Google Chrome and Mozi= lla Firefox.
Yo= u=E2=80=99ll find them in the Job Details page on the web portal, or you ca= n download them with the corresponding command in Chaos Cloud Command = Line Interface (CLI): "ccloud job download --id --= output=E2=80=9D
All communication between the user an= d our services is encrypted, so your data is safe. Chaos Cloud renderi= ng jobs are attributed to the user who submitted them, making accidental sh= aring impossible.
If your job renders successfully on y= our computer, it shouldn=E2=80=99t fail when rendered with Chaos Cloud rend= ering. If your job still fails on Chaos Cloud rendering, review the logs in= the Job Details page in the web portal, and copy and send them to us to in= vestigate. We=E2=80=99ll be in touch.
If you run out of credits on Cha= os Cloud rendering, your "Active" jobs will be paused, and you won=E2=80=99= t be able to submit new jobs. You will be able to resume your job and submi= t new jobs when you get more credits.
Every user is entitled to 20 free credits to test the service. Once this= allowance is exhausted, users can purchase more credits from our onli= ne store or via one of our preseller partners. If unused, = trial credits expire after 90 days.
Returns are honored by special reques= t only and can be requested within 14 days from the order date. Chaos Cloud= Credits will be refunded under the following conditions:
The amount will be calculated according to the price per Chaos Cloud cre= dit depending on the package you have purchased.
Yes, Chaos Cloud rendering will refun= d any credits spent for failed frames and still scenes. That is if a still = scene job fails, we will refund the credits spent for the whole scene, and = if a frame (or frames) from an animation job fails, Chaos Cloud rendering w= ill refund the credits spent just for the failed frame(s) (not for the whol= e animation job).
No, we don't offer support and refunds for deleted jobs. Even if they have= failed. The reason is that by deleting the jobs you delete all associated = input files, output images, assets and logs. If you report a problem with a= job, please do not delete the job until our team has finished investigatin= g the issue.
If your job has dark spots where you = expect to have objects, it might be because you are trying to render a scen= e with plugins which are not supported by V-Ray.
If your image is black, it might be t= hat you are using plugins which are not supported by V-Ray. Another possibl= e reason is that you are using a camera directed in a position opposite you= r scene.
It may take up to three minutes to se= tup and start a rendering machine. If it fails, the job state will change t= o "Failed" and we will notify you.
If more than 5% of the animation fram=
es fail, the whole animation job will be stopped and considered as failed. =
If the number of frames is too small, than at least two frames have to fail=
to fail the whole job. You will still be able to download the output gener=
ated up until the fail of the animation job. If you clone the failed animat=
ion, the Clone UI will suggest you to render just the failed frames by fill=
ing in their numbers in the Frame Range field.
Yes, you can re-submit a job with the Clone option, which is located in = your Job Details page.
If you want to check how many credits= you have left, go to the Resources tab and check the Remaining credits.
Your Credit Balance is also disp= layed on each Chaos Cloud rendering portal page. It is visible in the top r= ight corner next to the login information.
One of our primary goals is to keep t= he workflow as simple/automated as possible with little to no sacrifices. W= ith that in mind, selection of machine type and number is handled for you b= y us. At the moment we use a wide range of machines from 36 to 96 cores. Bu= t we continue to experiment with different configurations so these might ch= ange. Also, we are currently working on making distributed rendering automa= tic. With that in place you may seldom feel the need to specify anything up= front. That said it is important to clarify that the number of credits cons= umed takes into account the amount of processing power used for a given per= iod of time. So 1 hour on a 36 core machine will cost the same amount of cr= edits as 30 mins on a 72 core machine and the same as 22.5 mins on a 96 cor= e machine.
If you are re-submitting an animation scene that has a change in a chara= cter or geometry, the whole export process of a scene is done again. This p= rocess might take up to tens of hours depending on the complexity and numbe= r of frames in the animation.
Some scenes that are rich in geometry or some long animations could also= take long during the exporting process. Note that the exporting process an= d the rendering in Chaos Cloud are two different things and you are not cha= rged with credits during the export.
If you add a new version of a job that yo= u have already submitted to Chaos Cloud rendering, its upload will be much = quicker than the initial upload. Chaos Cloud rendering compares every new j= ob to the existing ones, and if there is a match the client app will upload= only the changes. This is useful when you make a new iteration of an exist= ing scene. That is why it is useful to keep your jobs in Chaos Cloud render= ing while you are still working on them.