Invalid ray length

[cbamber85]

Got any lights in the fluid?

[MikeRhone]

Yes. 2 raytrace shadow casting directional lights. I have tried deleting those and using spot lights, and point lights to no avail. I have also gone from scanline to rasterizer to raytracing in the render globals. I now know why I turning the verbosity off isn't helping on the render farm, but I would still love to know more about how to cancel the error at its' source.

m

[MikeRhone]

Follow up to old thread:

I never did find out what the cause of the error was, but I think it was actually a warning message. The trouble arises when it gets printed thousands of times per frame, increasing a 10 minute render to over an hour. I was incorrect when I stated I turned off verbosity. I set MR verbosity to 0, which actually means default to a verbosity of 3! The actual fix:

Set mr verbosity to 1.

[Kev3D]

That's a pretty useful thing to know, thanks Mike.

[Narann]

This doesn't solve the prob ^^

[sacslacker]

To me, it sounds like it did solve the problem. MR was basically spending all it's cycles logging warnings. If the frames rendered and the slowness was due to the verbosity, I'd say that's a decent fix.

It may have not fixed the invalid ray length issue but I seem to get that with fluids as well. It doesn't appear to effect the renders I've done when getting this message so who knows. I found it was more trouble trying to debug a problem that didn't appear to affect the render anyway.

Any clue what the deal is?

[ytsejam1976]

the invalid raylenght detecte not appear ever.

@MikeRhone
Is possible for you export your fluids and light only in another scene and share this scene for test it?
Or any scene simple with this same problem.

[tharrell]

Tangentaly related to MR error message spam causing render times to skyrocket from minutes to hours...

In Maya 2009/2010, be very very careful if you hide any lights in your scene. Fairly often you'll get an error message per bounce per subpixel written to your render log that looks something like:

shader "mia_whatever_shader" called mi_sample_light with unknown light tag 0x64e

Now take a micropoly displacement, and 3 bounce FG and you've got a gigabyte or two's worth of error message spam per frame (regardless of verbosity settings) and your render time will jump from about 5 minutes to over an hour a frame due to disk thrashing.

If you're lucky, your mayaRenderLog.txt won't overflow your drive before you catch it ;)

--T

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.