Is "pure virtual function call" on a DR a memory related error?

[snivlem]

HI there, on my DR slaves I get this error message when the scene is generating its light cache:

Building light cache...: 10.55% [ 0h 1m 45.3s] [ 0h 14m 52.4s est]
Building light cache...: 20.63% [ 0h 1m 47.7s] [ 0h 6m 54.4s est]
Building light cache...: 30.96% [ 0h 1m 49.3s] [ 0h 4m 3.8s est]
Building light cache...: 40.35% [ 0h 1m 50.7s] [ 0h 2m 43.7s est]R6025
- pure virtual function call

It seems to reset by itself then try and attempt a render again:

Building light cache...: 10.70% [ 0h 1m 50.6s] [ 0h 15m 22.5s est]
Building light cache...: 21.19% [ 0h 1m 52.8s] [ 0h 6m 59.5s est]
Building light cache...: 30.16% [ 0h 1m 54.2s] [ 0h 4m 24.5s est]
Building light cache...: 40.67% [ 0h 1m 55.9s] [ 0h 2m 49.0s est]R6025
- pure virtual function call

Like a never ending loop. The main rendering machine completes this fine (x64 whereas the slaves are unfortunately 32bit).

If it is a case of memory I've set my memory limits to 3000MB as to keep up with the 32bit machine, but I guess it is still running out? Are there any other options I can play with?

[vlado]

It's not related to memory as such; can you tell me which V-Ray version you are using? Can you get us a scene where we can reproduce the error?

Best regards,
Vlado

[snivlem]

Hi Vlado, thank you, I'm using this version of Maya 2012x64 with Win7 x64.

[2011/Jul/28|09:13:04] V-Ray: V-Ray for Maya version 1.50.SP1 from Jun 20 2011, 19:10:46
[2011/Jul/28|09:13:04] V-Ray: V-Ray core version is 2.00.01

The slaves are on the same version of V-Ray but obviously Win7 32bit and Maya 2011 32bit.

I can try upload a scene but it is quite heavy which I thought it could be a memory error. I'll see if I can strip some stuff out and send it in to your email. If I do I'll reply below and try and send it in. Thanks!

[snivlem]

Hi Vlado, I've narrowed it down to a particular referenced scene.

Unfortunately the parent and child scenes are too complex to send it and when I strip it down it renders fine...d'oh!

At least this is a clue. There is nothing unusual about the scene but it is physically large ([2011/Jul/28|13:03:48] V-Ray warning: Scene bounding box is too large, possible raycast errors.) and contains proxies that are scattered around.

If I discover anything else I'll post back here.

[snivlem]

Final update, sorry for the multiple posts. But this one is definitely memory related in the end.

[vlado]

Well, it may happen when you run out of memory, but still, it shouldn't happen and I think it's a bug - which is why I wanted to take a look at the scene

Best regards,
Vlado