"warning: Invalid normal index found on face..."

[jim mann]

Just upgraded to Vray 3.50.03 with Max 2017 and now all my scenes are reporting the following warning "warning: Invalid normal index found on face..." for what seems to be every face in the scene. This is on existing scenes, that weren't exhibiting any problems previously.

I don't seem to be seeing any issues in the resultant renders...yet. Should I be worried?

Should I revert back to previous version?

[matanov]

I've logged recently a similar issue into our system, I will let you know when there is movement on the subject.

[jim mann]

Thanks Peter, also having problems with DR now so am reverting back to 3.4. Can't risk problems as I've got two deadlines hurtling towards me.

[GLASS-CANVAS]

We had this problem, and we *think* it is related to using SiNi Ignite to attach multiple objects by material. Whatever causes it, here's the workaround:

Select objects causing errors
Add an Edit Mesh modifier, in Edge mode set all edges to Visible
Convert all objects to Editable Poly
(optional) Convert all objects back to Editable Mesh

This worked for us, we had 64 thousand errors previously, it cleared the whole lot. YMMV

[matanov]

Thanks Peter, also having problems with DR now so am reverting back to 3.4. Can't risk problems as I've got two deadlines hurtling towards me.

What DR problems ?

[jim mann]

None of the render servers were being accessed. Whether or not this was due to the Vray 3.5 upgrade I can't say, but can't take the risk for the next couple of weeks.

[jim mann]

...here's the workaround:

Select objects causing errors
Add an Edit Mesh modifier, in Edge mode set all edges to Visible
Convert all objects to Editable Poly
(optional) Convert all objects back to Editable Mesh...

That sounded like far too much work for a Friday.

[matanov]

Everybody with the warning - please send your scenes to me (peter.matanov@chaosgroup.com).

[jim mann]

Hi Peter, Are you still looking for files with this warning? I've left Max 2016 as it was, but gone back and upgraded Max 2017 so that I can use it on a new project. Newly created files/projects don't have the warning. Upgraded files do. Can send you examples if you are still investigating.

Jim

[Margarita.Stoeva]

Hello!

There is a fix for such log flood with "Invalid normal index found on face" messages in the new V-Ray 3.50.04 - the builds were released a couple of days ago.
If the issue still persists with the new builds a scene will be very helpful!

Best regards,
Margarita

[jim mann]

Thank you Margarita,

I had installed 3.50.03, but will update to the latest version straight away. If the error persists (though I'm confident and hopeful it won't) I will send you the offending files.

Thanks again.

Jim

**UPDATE** Just checked after updating. No problems, all fixed. Thank you!