"Exception: Irradiance map thread"

[40th]

In prepass (3 of 3) process the "buckets" work gets very very slow (hours), then i looked on the V-ray progress window, and i saw this text:
Exception: Irradiance map thread. It's written multiple times (about more than 100 times).
Edit: Eventually it's get stuck/freeze, (the buckets doesn't move).

What does it mean and how can i fix it?

[Jackson_cg]

Re: "Exception: Irradiance map thread"

Does it still happen if you save out the visopt and then reload it? Does it affect any file with that visopt?

[40th]

Re: "Exception: Irradiance map thread"

What i did is, i lowered some settings (lower quality) but still remained a good "quality", and it rendered normaly.

[Jackson_cg]

Re: "Exception: Irradiance map thread"

Glad to hear you sorted it. Out of interest, what were your IM min and max rates?

[40th]

Re: "Exception: Irradiance map thread"

It was -2, 0 on 1600x883px
and i lowered it among other settings to -4,-2

[mjm223]

Re: "Exception: Irradiance map thread"

Just out of curiosity, what other settings did you lower to solve this problem? I've also been getting the same "Exception: Irradiance Map Thread" message.

After reading this post, I lowered my IRMap min and max from -2/0 to -4/-2, but I still got the same message (at the end of the 2nd of 4 prepasses).

Do you have any tips?

[epinox]

Re: "Exception: Irradiance map thread"

I got the same problem; took me up all night to render the same scene over and over again...

I didnt think of reducing the IRMap min and max's though, I just lovered the resolution... I think its rendering it now...

My problem is it never done this before, but I used a lot of trees and displacement grass and water with bump mapping... I think I might have asked for it

[40th]

Re: "Exception: Irradiance map thread"

Which Sketchup version do you use?

[mjm223]

Re: "Exception: Irradiance map thread"

I had updated to the most current SketchUp 7.1 a few weeks ago. I've noticed that ever since that update I've been having a lot more problems rendering from VRay.

[40th]

Re: "Exception: Irradiance map thread"

That's the connection I thought of in the first place. I would recommend you to revert to original SU7 if you having so much trouble with it, it's not worth it.
Personally I'm also using SU 7.1 on daily basis, and i didn't had issues with it so far.

[stefanq]

Re: "Exception: Irradiance map thread"

I also revert to su7.0. I couldn't load any texture in my scenes. Bug splats....allot of them.

[40th]

Re: "Exception: Irradiance map thread"

Sorry to hear that Stefan.
Looks like SU and VfSU has a long way to perfection. I believe that it's all a matter of time and resources invested in to the development.

[stefanq]

Re: "Exception: Irradiance map thread"

Well, it's not necessarily SU's fault, I have to many ruby's, and as far as I know, some of them could create some problems.

[Jackson_cg]

Re: "Exception: Irradiance map thread"

Yep, it's the unfortunate downside to SU's ruby interface. As much as we'd all be much worse off without ruby scripts (even VfSU operates via ruby scripting) it does make it much harder for developers to track down the source of bugs. In this case I'd be inclined to suspect SU itself as these have only appeared since SU7.1 was released, but it is possible that they were already there in VfSU and it was only positive changes in SU7.1 which revealed them.

To be honest, if it wasn't for the SU7.1 hang bug (where SU completely freezes and has to be shutdown via Windows Task Manager) I would probably have persisted with it, but combined with the crashes caused by material editing and parsing I felt I had no choice than to revert to SU7.0 for day-to-day work.

[mjm223]

Re: "Exception: Irradiance map thread"

I've reverted back to the original SU 7.0 as well. My DR is now working properly again (aside from the typical bugs I've experienced on SU 7.0).

I really hope that newer version of VfSU comes out sooner than later. I've been working with the VfSU 1.5 at my job and have been holding off on buying it for my home computer in fear that I'll suffer the "Apple Effect" (buying a program shortly before an updated version of it comes out, thus forcing me to pay a fee to update to the newer version.) ;D