Author Topic: Render gets stuck - volumetrics excessive ray weight  (Read 14374 times)

2017-04-09, 19:29:44

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio
Hi,

So basically, my renders are getting stuck.

Elaborating.

Press render, it starts rendering. Hours late I check the render and let's say is at 70 passes and 8.0% noise level.

6 hours later

70 passes and 8.0%.

Another one.

Set the render to last 24 hours.
24 hours later - it says, 17 hours elapsed. Estimated remaining: 20 hours What???

And this is happening in a lot of machines. Which is great news when you have a deadline for Tuesday.

Any solution? We are using Corona 1.5 hotfix 2
« Last Edit: 2017-04-13, 11:24:01 by Ondra »

2017-04-10, 09:44:00
Reply #1

Nik

  • Active Users
  • **
  • Posts: 167
    • View Profile
    • HQ Details
Only time limit is set? No passes or noise level limit?

2017-04-10, 10:11:56
Reply #2

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio
Both. With noise level, time and passes limit.

Giving an example.
Last night I left a render at 9% noise level and 47 passes. This morning was at 9% noise level and 50 passes. The CPU was at 8%.

My machine the same.

It starts well and but then after a couple of hours it seems that Corona just stops caring. I don't know if it helps, but when using time limit, the Estimated remaining time is stuck it doesn't go down.

2017-04-10, 10:24:31
Reply #3

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio
Basically I have been saving the VFB and restart the render. Which is quite fun when you have 12 machines to check.

2017-04-10, 10:28:27
Reply #4

Nik

  • Active Users
  • **
  • Posts: 167
    • View Profile
    • HQ Details
This happens only in one scene?

2017-04-10, 10:33:18
Reply #5

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio
This happens only in one scene?

So far yes. But this scene is divided into different Xrefs and they are not the same for each camera.

And if you click stop the render, it refuses to stop and apply the denoising.

2017-04-10, 11:42:05
Reply #6

Nik

  • Active Users
  • **
  • Posts: 167
    • View Profile
    • HQ Details
Well, the problem maybe related to Xrefs somehow.
If you want to find a reson then try to disable half of Xrefs, then check if problem is still there. If not - problem was in disabled Xrefs, so you can enable them and disable half of that half :) and so on, until you will find a problem.

And Stop in VFB should apply denoise when it's pressed. After denoise it should stop. It doesn't?

2017-04-10, 12:11:48
Reply #7

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio
That is why I don't think the problem are the Xref.

First, the render starts really well. Like after 2 hours I am already around 12%. Then when I press stop the render, the render doesn't stop and apply the denoising. Also, if I am using the time limit it starts well, so why after a couple of hours it stops working?

I think that if the problem were the Xrefs the render wouldn't even start.

2017-04-10, 14:16:06
Reply #8

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio
And it keeps doing it. Just now this render is stuck at 30% noise level.

2017-04-11, 12:00:37
Reply #9

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio

2017-04-11, 12:18:27
Reply #10

Nik

  • Active Users
  • **
  • Posts: 167
    • View Profile
    • HQ Details
It seems for now you are the only one who had this bug.
You can share scene with all xrefs or you can try to find a reason yourself.

Did you use DR or backburner? If yes, then does bug persist if you render locally?

2017-04-11, 13:19:11
Reply #11

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio
I know, but would be nice to hear something like: "Yeah probably is an XREF that is stopping the render." or "have you try XYZ?"

 I still don't believe that the render starts with no problems and then it stops because of a XREF.

And isn't only me, is 12 other guys using Corona on our team and hear some of them saying they want VRAY back.

Not using DR or Backburner. I will be working on another project and see if the problem persists.

2017-04-11, 13:20:39
Reply #12

Nik

  • Active Users
  • **
  • Posts: 167
    • View Profile
    • HQ Details
Quote
And isn't only me, is 12 other guys using Corona on our team and hear some of them saying they want VRAY back.

In one scene?

P.S. I'm using xrefs rarely but there were no problems when I did.

2017-04-11, 13:25:11
Reply #13

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio
Yes, so as you can imagine is quite a pain. Having to save VFB, close 3ds Max, open again all those Xref and resume render.

And that is what to me doesn't make sense. How is possible that only after a couple of hours the Corona stops working? And if you look at it, everything is normal. The smiley face keeps moving, the numbers keeps going up and down, is only you see the same Pass number and noise level, that you realize something is wrong. And then you press stop the render, and it simply ignores you. It doesn't stop, it doesn't apply the denoising.

2017-04-11, 13:26:17
Reply #14

CiroC

  • Active Users
  • **
  • Posts: 506
    • View Profile
    • Portfolio

P.S. I'm using xrefs rarely but there were no problems when I did.

We always use Xref without any problems. The plugins we use are:

ComplexFresnel
FloorGenerator
ThinFilm
Clone