memory heap reported damaged

[cristoforo]

What does this message mean? What to do about it? AND....is there a way to find out why a DR render node is no longer responding when the message appears....."Render node xx not responding."

[studioDIM]

The warning, i seem to recall (a search might lead to more accurate results), is not due to VRay, but just to something in the max scene which has gone messy in RAM.
Might not influence the render at all, but to get rid of it i seem to remember you need to re-merge the scene in a fresh one.

Lele

[vlado]

Re: memory heap reported damaged

AND....is there a way to find out why a DR render node is no longer responding when the message appears....."Render node xx not responding."

You can be about 90% sure it is because the render node has crashed. To see if this is really the case, it is a good idea to change the name of the vraylog.txt file in the System rollout before starting the DR, for example to vraylog_dr.txt so that it doesn't get overwritten on the slave machine when 3dsmax is restarted by the spawner. After you get the "render node not responding" message, you can examine the vraylog_dr.txt file on the render node to see if there is any meaningful information there.

Best regards,
Vlado

[Neilg]

Ive been getting this a hell of a lot recently, managed to narrow it down to a bad scene in general and it goes when merging.

[siliconbauhaus]

I had this the other day and I dont use DR. I shut max down and restarted and it seemed to go away.

[DaForce]

Yeah this happens often enough, not really a problem, just due to memory fragmentation I would say.. nothing to worry about.
Restart max and it all goes... usually.