Hi,
For a long time in the Corona for cinema there is a problem that is not present in the version for 3d max. (In Corona Render Benchmark and 3D Max are OK)
I use a dual-processor configuration with two intel xeon e5-2698v4 es
If you just add textures (just one texture in diffusion, gloss, bump), then we have this (LOOK AT THE NUMBER OF RAYS) It is low!
And if you use a lot of Corona Bitmap, then the textures start to blur very much
Please help me, as it takes a lot of time to assign a Corona Bitmap to the textures, and if you don’t assign it, it takes a lot more time to render (several times), thank.
There’s a lot of issues reported in this ticket. If I understand this correctly:
C4D bitmap being slow to render
Corona bitmap’s texture projection not working under projector or layer shader
Bump inconsistency between C4D and Corona bitmaps
Texture bluring with a lot of Corona bitmaps (what does this mean?)
Slow and buggy material editor (We need more specific information here.)
Numbers 1 and 2 are new to us, we’ll need to do our own tests to determine the cause and possibly fix these bugs.
Number 3 seems like a minor issue to me. Just use the setting that produces the best result. Actually, the images seem pretty similar.
Numbers 4 and 5 need more information.
In general, I’d suggest to use C4D native bitmap for now. Corona bitmap needs some more attention from us for now.
Hi, I just tried to replicate your (bitmap vs no bitmap) scene as best I could and have to say that my results were almost the same. To make it a fair comparison on our end could you upload your test scene for us to check? If so, the upload link is in my signature below. Thanks.
and when a large scene with a large number of corona bitmap begins to become like this (the level of blurring can be different, from a slight blur, to a full one, where only the color is visible)
Let Gr100 describe this mistake, I didn’t notice it.
Number 3 seems like a minor issue to me. Just use the setting that produces the best result. Actually, the images seem pretty similar.
Well, using the corona bitmap in the bump, I lose the quality of the bump (noticeably on the fabrics, especially if you need a good picture), and if you don’t use the bitmap crown, the rendering speed drops(
In general, I’d suggest to use C4D native bitmap for now. Corona bitmap needs some more attention from us for now.
Not using corona bitmap is very bad for rendering speed on systems with 2 CPUs
I see no reason to do test scenes, as this is a constant problem. The more textures added through the corona bitmap, the higher the render speed (almost “linear” dependence of the speed increase), let’s say 100% of all the textures through the corona bitmap, which means 100% speed if there is 50% of the textures through the Corona bitmap, hence the speed will be 50%
It is necessary to check on other systems with two processors, with a different architecture. My processors are Broadwell-EP, I also checked with my friend, who also has processors on Broadwell-EP architecture, he has the same problem. Maybe on older or newer processors (Dual processor configurations) there will not be such a problem
We mostly use 8-core processors, so it’s possible that it’s an issue relevant to dual-core CPUs.
Edit: My bad, you said dual processor… That’s more interesting then. Unfortunately I don’t know what could be the cause. It might quite possibly be an inherent feature of the system.
Yes, it is a system with 2 processors that would show two CPU-Z in the first screens
But in 3d max + corona Ok, corona render benchmark ok too.
It turns out that the corona bitmap works like a “crutch”, somehow forcing a bunch of 2 processors to work + a crown + texture in another way.
If I set a limit on rendering in threads in the settings of the Cinema, let’s say the number of threads per processor, in my case it is 40 threads, then everything is fine, the situation is the same as with systems on one processor. But if you set 41 threads (40 threads of the first processor, and 1 thread of the second), then the situation described above begins((
I will try to make a screen recording soon so that you understand me better)
Just a note:
Maybe this is also a texture sampling problem. Disable it (under texture settings/options: set Sampling to None) and see, if it makes things any better.
Another +1 from me. I’m running into very similar issues using a dual socket (2S) machine. I wonder if 2990wx can replicate this behavior as well due to its “multiple” NUMA nodes architecture.
:\ Yeah, I’m running an expensive workstation at the speeds of mainstream consumer chips because of this issue. Its either that or I use the CBitmap to get the speed back but then loose the ability to scale maps.
If you don’t use the bitmap corona, then it’s better to render on a single processor, in the settings of cinema (edit-preferences-renderer) and indicate the number of threads of one processor
