Final render pass (single sample) blows out render

[14bmwc780nike]

Looking for some insight on what might be happening here. This is what the render should look like as the final https://i.imgur.com/vPeCOD9.png(403 kB)
https://i.imgur.com/vPeCOD9.png This is the result when rendering the final at a larger size for print. No changes were made other than resolution 18k x 12k pixels. https://i.imgur.com/BrJTViC.png(248 kB)

[frankmci]

What trouble shooting have you done? The most obvious question is Does it happen at intermediate resolutions? How about, Does it happen with a simplified light source? Does it happen without the bottle geometry? Does it happen with simple stand-in geometry? How are you generating your background gradient, since it seems to be gradient related. Does it happen with other render kernels? There's a lot of basic things to test to try to understand what's going on.

[14bmwc780nike]

-SNIP-

[14bmwc780nike]

What trouble shooting have you done? The most obvious question is Does it happen at intermediate resolutions? How about, Does it happen with a simplified light source? Does it happen without the bottle geometry? Does it happen with simple stand-in geometry? How are you generating your background gradient, since it seems to be gradient related? Does it happen with other render kernels? There's a lot of basic things to test to try to understand what's going on.

*** LIVE UPDATING HERE ***

What is interesting though is the issue only shows up in the very last and final pass prior to saving.

Updated: 2/8/2020

Failed tests
- PSD vs EXR
- Emmisve background ON vs OFF
- 32 bit vs 8 bit
- Hot Pixels 1 vs 0
- AI Lights ON vs OFF
- HDR OFF vs ON
- Glass/Wine OFF
- Background light OFF
- Render Passes toggled OFF
- Post-Processing OFF
- All scene lights OFF
- Deleted Model: Empty Scene
- Neutral Response OFF
- Move all assets to a fresh new file (copy and paste)
- Emissive background OFF
- Drop PX dimensions and up-resolution from 300 -> 600

[frankmci]

What is interesting though is the issue only shows up in the very last and final pass prior to saving.
.

Ah-ha!, "... only shows up in the very last and final pass..." I didn't understand that in your first post, and what do you mean by, "single sample"?

What exactly do you mean by only the final pass? What passes do you have enabled? What happens when you just do a single beauty pass? Are you using any post effects? De-noising?

Off the top of my head, maybe there's a post process that doesn't have enough memory to complete its task and is returning wacky results. You might have to use the tiling camera.

[14bmwc780nike]

What is interesting though is the issue only shows up in the very last and final pass prior to saving.
.

Ah-ha!, "... only shows up in the very last and final pass..." I didn't understand that in your first post, and what do you mean by, "single sample"?

What exactly do you mean by only the final pass? What passes do you have enabled? What happens when you just do a single beauty pass? Are you using any post effects? De-noising?

Off the top of my head, maybe there's a post process that doesn't have enough memory to complete its task and is returning wacky results. You might have to use the tiling camera.

What I mean regarding the final pass... say I have the samples set to finish the Path Traced render at 200 samples. When it reaches 199 samples, it looks perfectly beautiful and then when it hits 200 samples and is saving that's exactly the moments the freakish glowing colors show up.

As a workaround, we've been saving the render prior to the last few samples and working with those.

[14bmwc780nike]

Sadly I can't test this at home since I have an older version of Octane 4. The render crashes Cinema 4D upon the last sample pass.

[frankmci]

If you can, upload a zipped version with any proprietary stuff stripped out, and I'll take a look.

[14bmwc780nike]

If you can, upload a zipped version with any proprietary stuff stripped out, and I'll take a look.

We ran a battery of tests trying to vet out the problem. The only time the giant glowing anomaly doesn't appear is when the render is set to a much lower resolution. Hoping to gain some insight!

[14bmwc780nike]

Solved. I need double the amount of installed RAM from the current which is 64gb.