Author Topic: White Stripes - DR  (Read 1202 times)

2023-04-20, 11:47:00

metanerd

  • Active Users
  • **
  • Posts: 7
    • View Profile
When rendering with DR enabled, white stripes appear in the image. The problem cannot be reproduced.

Attachment 1 shows Bloom and Glare enabled
Attachment 2 shows Bloom and Glare disabled

Render nodes: PC (i9 / AMD Threadripper)
Scene on Mac Studio, sent to nodes
Corona 9 (Hotfix 9)
Cinema R2023.1.3

2023-04-20, 12:40:23
Reply #1

Beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 3814
  • Bengamin
    • View Profile
    • Cormats
Hi, what DR are you using?
Bengamin Jerrems l chaos-corona.com
3D Support Specialist - Corona l contact us
Corona Uploader l Upload
Portfolio l Click me!

2023-04-20, 12:47:08
Reply #2

metanerd

  • Active Users
  • **
  • Posts: 7
    • View Profile
I do not know if I have understood your question correctly, but we us the TeamRender Function in C4D.

2023-04-20, 14:07:53
Reply #3

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5434
    • View Profile
As a first thought, looks like one machine is missing some or all of the assets and so is returning a white blank result. Are the assets stored on a network drive (does that one machine have access?), duplicated on each machine (does that machine have them duplicated in the same place?), as first things I'd ask myself. As well as the standard check of "does every machine have identical versions of C4D and of Corona installed?" of course.

Oh and that is a lot of render nodes, so I'd also check there are enough licenses to go round, and check the logs to see if there are any errors about missing a license.
Tom Grimes | chaos-corona.com
Product Manager | contact us

2023-04-20, 14:19:04
Reply #4

metanerd

  • Active Users
  • **
  • Posts: 7
    • View Profile
Hi Tom, your approach sounds interesting. We were just thinking about that as well. Many assets are stored using the built-in C4D Asset Browser (Asset Browser is stored on a Synology NAS with 10Gbit connection)
Possibly it could be related to the lack of indexing of the database.
But it is strange that the error occurred only after approx. 35min. or render time (with a total of 40min render time). The error should show up instantely, right?

We will try to update the index of the C4D Asset Browser.

Regarding the same version, everything is double checked, i.e. the Corona and C4D versions are all exactly the same. So it can't be because of that.
As far as I know, there should be enough licenses available.



« Last Edit: 2023-04-20, 14:25:41 by metanerd »

2023-04-20, 14:24:30
Reply #5

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5434
    • View Profile
It MIGHT show up instantly - the strip is very narrow (when you remove the expansion from Bloom and Glare :) ) so it could be that this machine is the slowest and not contributing much, and it could be that in earlier renders other machines "did its work for it" because they finished their work faster, but in a later frame the scene took longer for all machines and this one did send in a contribution. So it's still somewhat possible missing assets could be the issue, worth a check anyway!
Tom Grimes | chaos-corona.com
Product Manager | contact us

2023-04-20, 14:27:08
Reply #6

metanerd

  • Active Users
  • **
  • Posts: 7
    • View Profile
It MIGHT show up instantly - the strip is very narrow (when you remove the expansion from Bloom and Glare :) ) so it could be that this machine is the slowest and not contributing much, and it could be that in earlier renders other machines "did its work for it" because they finished their work faster, but in a later frame the scene took longer for all machines and this one did send in a contribution. So it's still somewhat possible missing assets could be the issue, worth a check anyway!

Could it also have to do with the fact that not all nodes are equipped with 10Gbit?

2023-04-20, 14:57:44
Reply #7

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5434
    • View Profile
Could play a part, can't say for sure but it's a possibility.
Tom Grimes | chaos-corona.com
Product Manager | contact us

2023-04-21, 17:37:12
Reply #8

metanerd

  • Active Users
  • **
  • Posts: 7
    • View Profile
* short update
After 2 days of intensive testing, it seems that either materials containing the bitmap shader or / and shared textures (especially SIGER materials stored in the asset browser) are causing the problems.

I will do some more tests.

2023-04-21, 22:18:55
Reply #9

BigAl3D

  • Active Users
  • **
  • Posts: 879
    • View Profile
Oh man, THAT problem again? I had a similar thread about this issue. Turns out the main culprit is the Corona Bitmap shader. I have the Corona shader pack from Pixel Lab and had this problem. After replacing the Corona Bitmap node with C4D's Bitmap node, most of the problems went away, even with shared nodes. You might have to test it after the bitmap node in case you don't need to remove the shared node.

2023-04-22, 00:01:49
Reply #10

Juraj

  • Active Users
  • **
  • Posts: 4743
    • View Profile
    • studio website
I had this EXACT problem +/- 5 years ago. (3dsMax user)

It has nothing to do with server not having bitmaps or such. If you color-pick in VFB into that white line, it will turn some absurdly high number value.
I even sent my scene back then to the team but they could not recreate it.

I never had it again since. Was one time occasion. Definitely not user mistake, absolutely some weird bug.
Please follow my new Instagram for latest projects, tips&tricks, short video tutorials and free models
Behance  Probably best updated portfolio of my work
lysfaere.com Please check the new stuff!