Building light cache infinitely...

[kwok3d]

This happened twice to me in the past 2 weeks. I'm using Vray 1.50.SP5

I have very small and simple scene. Rendering usually take less than one minute. So after many rendering, one of them would starts building light cache and goes on forever until I have to kill max. The weird thing is that I was able to move around in max UI, click menu and stuff. I could even try saving the scene but of course it errors out and telling me file's corrupted. Any ideas?

[JOAN_LORD]

Happens to us sometimes, the only way to cancel it usually is to end in task menu, so we've got into the habit of saving before rendering every time, best thing to do - PLUS it always help that everything is a VRAY material, so using the Convert scene is always a good one before rendering.

[leehumphries]

Same here..happens daily..

File also always get corrupted

[vlado]

Do you have auto-backup enabled? This could happen if 3ds Max decides to do an auto-save during the render process (even though V-Ray specifically disables it).

Best regards,
Vlado

[leehumphries]

apologies for leaping on this thread.

Autosave is disabled.

This isn't a new thing,since owning Vray 2 years i have had this problem - all versions. Just very random,i could be rendering a preview render 640 pixels,keep stopping and tweaking,hit render again and all of a sudden the light cache builds and the the infinite loop.Nothing happens until you close max. the file you were then using then becomes corrupt.

I didnt think it was Vray specific and would be a 3dsMax 2011 design problem,which there are many. So ignored the error and started learning to keep saving many incremements of the file

[vlado]

Ok, thanks for the pointer; will look out for this.

Best regards,
Vlado

[simmsimaging]

Happens here occasionally too, but not often. Autosave related crashescare frequent though.
B

[MoonDoggie]

Happens to me frequently as well, sometimes making sure reflections aren't set to 100% white helps, and making sure my materials aren't unsupported types, or even standard materials. But Autosave during rendering almost guarentees it happens.

[Morne]

I sometimes get this also. Sometimes not so much, and other times a lot. I've done extensive research into the matter and even setup an independant panel of people to help me investigate. We've narrowed it down to the fact that "Autodesk" is in the main software titel

But seriously, this happens maybe once every 2 months, and there is nothing special that I do or don't do that would point to anything concrete.

[voltron7]

wanted to see if this has been addressed yet?
like others have always had this issue and still plagued by it today.
For me it seems to always be during light cache calculation...seems random, too.
This scene was fine for days just doing some different views, and all of a sudden...infinite LC....
auto-save is enabled and prefer to keep it that way...

[kosso_olli]

Problem still exists. I encountered that one in one of our projects last year. Sent a scene to Vlado for investigation, but the problem wasn't solved. In the end I found out that certain maps are responsible for that, one major one was the flakemtl. Vlado said that some other procedural maps could also produce this issue. The problem should be fixed with one of the lastest updates, but frankly it isn't. Still come across it sometimes. Here's the link to the topic I opened back then:

http://www.chaosgroup.com/forums/vbu...es-Light-Cache

Regards

Oliver

[vlado]

If you come across a case where you get this, can you send me the scene to vlado@chaosgroup.com so that we can fix the particular situation as well?

Best regards,
Vlado

[voltron7]

Happens here with only standard bitmaps and one HDR in a domelight...no flakes material either...
Lost countless hours from this problem...a real fix would be wonderful.

It has happened lately under the following condition...

1. start lightcache and notice max is also attemptimg to autosave...
2. as I clicked the open render dialog button, once the button was "pressed down" max tried to autosave...

So, for me, it almost always related to autosave...can't send that scene, but happens on any scene for many releases...

[MoonDoggie]

I can verify the above. If you hit render when autosave hits, you're screwed.

[voltron7]

yeah, a real bummer, and I always try to not do that, but it seems to happen as I'm clicking the button, max also decides to autosave.

O.T. Funny, this bad timing also happens to me in AutoCAD almost everyttime I use the "LIST" command.

Maybe is there a way to force vray to not initialize if an autosave is happening? (Similar to the "check for missing files" warning.)
Thanks