In accordance with the art. 13 section 1 and 2 of the European Parliament and Council Regulation 2016/679 of the 27th April, 2016 on the protection of natural persons, with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation), hereafter RODO, I hereby inform that:
1. EVERMOTION S.C., 8 Przędzalniana Str., 15-688 Białystok, Poland is the Administrator of your Personal Data (APD)
2. Data Protection Inspector can be reached through e-mail: iod@evermotion.org
3. Your personal data are to be processed on the basis of art. 6 section 1 letter a, b and f of RODO in order to: a) prepare, conclude and execute the agreement and for other purposes approved by you, b) to execute the legitimate interest like marketing of products and the agreement, claim assertion or defence against claims resulting from the law regulations.
4. Entities entitled to the reception of your personal data may be the authorised public bodies; mail providers; providers of the services covered by the agreement; responsible for debt recovery, keeping the archives, document utilization, legal consulting, technical services, IT services and accountancy.
5. Your personal data shall not be transferred to the third country, nor to the international bodies.
6. Your personal data shall be processed within the period of the agreement and upon your additional consent until you withdraw it. APD shall keep the data for the period of any civil law claim execution connected with the agreement.
7. You have the right to demand an access to your personal data, to correct or to delete the data if there is no other basis for the processing or any other purpose of such processing or to limit the processing of the data, to transfer the data to another administrator and to raise objections to the further data processing if there is no legal basis for further processing and to withdraw any previous consent.
8. You provide the personal data voluntarily, however they are necessary to conclude the agreement. The refusal of providing such data may result in the refusal of the agreement conclusion.
9. You have the right to lodge a complaint to the Personal Data Protection Office when in your opinion the data processing violates the regulations of General Data Protection Regulation of the 27 April, 2016 (RODO).
10. Your data will be automatically processed, including the form of profiling. 11. You are obligated to forward above mentioned information to your representative, especially if you appointed this person in the agreement as the contact person or as the representative for the agreement execution.
OK
Blender Cycles X - Render Speed Test in ArchViz Scenes
How fast is the new version of Cycles rendering engine?
Just a couple days ago Blender Foundation announced new Blender 3.0. One of the most exciting features in this version is Cycles X - the new incarnation of path tracing rendering engine for Blender. From the first announcements of developers it looks that it is to be much faster than the current version. Is it true? Let's find out!
I conducted tests on PC with AMD Ryzen 3900x, Nvidia Geforce RTX 2080 Ti and 32 Gygabytes of RAM. I set Blender to Optix GPU rendering, although i selected only GPU as my Optix device, AMD Ryzen was not involved in rendering process. Since Blender 3.00 Cycles X branch does not allow you to choose tile size, I used "progressive refine" in Blender 2.92, so tiel size would not affect the render time.
improve the architecture of rendering engine for future development,
improve usability of viewport and batch rendering,
improve performance on modern CPUs and GPUs
introduce more advanced rendering algorithms.
Today we will focus on the performance. I will use our Archinteriors for Blender collection as a benchmark. I downloaded it from Evermotion Shop and just drag and dropped blender files to two Blender instances. It's just as simple as that.
First, I set my render samples to 128. I need to turn off "square" samples option in advanced settings. It increases sample count to the power of two, so when you selected 64 samples and they are squared, in fact you are rendering 64 times 64 samples which is 4096. we don't need as many samples in our test. So I uncheck "square samples" and change number to 128.
Since the release of our collection, Blendere introduced great viewport and render denoising options, so there is no need for rendering insane amount of samples. 128 is rather low, so we will render our scene in 1200 samples too, just to see the image that can be treated as a final.
One word about denoisers in Blender: in current stable version, which is Blender 2.92 we have three options: NLM denoiser, Intel Open Image denoiser and Nvidia Optix denoiser. In Blender 3.0 NLM denoiser will be removed, because AI based denoisers, like Optix and Open Image denoiser give better results, so there will be only two denoisers in the final version. I will use Optix denoiser in both renders - in Blender 2.92 and Blender 3.0 alpha.
I havent tested CPU performance yet, because with the modern GPU at hand I don't think that CPU rendering on Cycles makes sense, accounting that you have enough of GPU memory. GPU rendering is much faster and it is the future of Cycles in my humble opinion.
As you can see, it took only 2 minutes and 5 seconds for Cycles X to render our image with 128 samples. for comparison - Blender 2.92 with regular cycles rendered this image for 4 minutes and 30 seconds. Stunning! The grey part of both bars is the time that it took to load the scene into memory and start rendering. In both case it was just about one minute.
When rendering with 1200 samples, it took 15:35 minutes to cycles X to deliver the image. On the contrary - regular Cycles struggled for 35:15 mintes with this scene. we are talking here about insane gain! This time prefetching the scene took also just about a minute in both cases.
This is a scene number four from the same Evermotion collection. It is also a loft, this time a bit more vintage.
Again, Blender Cycles X beats regular Cycles version by far. Only 33 seconds for low quality rendering, two minutes 42 seconds for rendering of 1200 samples version and 5 minutes 13 seconds for rendering with 2400 samples. To render this last image, older Cycles version needed over 30 minutes! It means that new Cycles X can be almost six times faster!
Here is a tutorial that covers matching a 3D Camera in Blender to a still photograph and then animating onto a ground plane to receive the shadows. In part two of this tutorial, we will bring this animation into After Effects.
COMMENTS