Corona Renderer for Cinema 4D > [C4D] Bug Reporting

Dual cpu speed problems

(1/2) > >>

Evolist_ua:
Hi guys, the 8th daily version of the Corona for the cinema has already been released, and the problem that I wrote about back in 2019 is still present (https://forum.corona-renderer.com/index.php?topic=24238.0)
The confirmation:
One cpu with no corona bitmap at materials, 9,7m rays actual

TWO CPU (not 2 core) with no corona bitmap at materials, 5,5m rays actual. One cpu is faster than two,LOL.

Two cpu with corona bitmap at materials, 16+m rays actual, this is NORMAL speed.


Are you planning to fix the render speed issue on dual-processor systems at all? If not, then at least add to the converter the ability to immediately convert all textures to the corona bitmap,because doing it manually takes a lot of time, thanks.

maru:
We have a similar issue reported for Corona for Max, but we were not able to reproduce it on our end (it only happens to the user).

Are you using the Corona UVW Randomizer map here?
Are you using the Corona Triplanar Map here?

Can you please share the scene with us? (if you haven't yet)

Max report for our team - (Report ID=CRMAX-866)

Evolist_ua:

--- Quote from: maru on 2021-08-18, 13:33:51 ---We have a similar issue reported for Corona for Max, but we were not able to reproduce it on our end (it only happens to the user).


--- End quote ---
I tested in 3d max, even in 2019 everything was ok there with speed.
No  UVW Randomizer or Triplanar there, only maps at diffure,reflect\gloss, bump.

There is no need in dropping this test scene for you, created in a couple of minutes, it's just a set of simple geometric shapes, with sky and two materials, starting from 2019 with almost every assembly I create a similar test scene, and the result is always the same.


--- Quote --- but we were not able to reproduce it on our end
--- End quote ---
Have you tested this on a DUAL PROCESSOR PC???

TomG:
Just as a note, a scene is always handy, just in case some default render settings have been changed by a user etc. It's always useful to know we are testing EXACTLY the same thing, and not something "close to" or "similar to" or "kind of like" the scene where a user has a problem. So sharing the scene would still be useful, thanks :)

maru:

--- Quote from: Evolist_ua on 2021-08-18, 13:51:45 ---
--- Quote --- but we were not able to reproduce it on our end
--- End quote ---
Have you tested this on a DUAL PROCESSOR PC???

--- End quote ---

We tested this ON BOTH SINGLE PROCESSOR PCS AND DUAL PROCESSOR PCS!!!

And to test it thoroughly we would need exactly the same scene that you are using so that we could compare with your results too.

Thanks for understanding.

Navigation

[0] Message Index

[#] Next page

Go to full version