Has anyone encountered the message "Warning: Vertex 150 specified to be sharp does not exist" and know how to avoid the problem?

[vanpixelguy]

We are sometimes encountering a message from V-Ray that says "Warning: Vertex 150 specified to be sharp does not exist". The problem is that some V-Ray jobs report the error hundreds of thousands of times, making our log files enormous, filling up our disk and slowing down the render process. When you have thousands of assets in your scene its very painstaking to isolate which geometries are causing the message, and we have seen no documentation on how to resolve the problem. I know that the message is part of the OpenSubd library, just unsure what it is about the geometry that causes the message to be output. We have come up with various techniques to "repair" the offending geometries in Maya but as I stated earlier, we don't actually know what it is about the geometries that causes the message to be generated. We are running V-Ray for Maya version 3.60.05 and also 3.4 on WIndows 7 and 10.

Has anyone seen these warnings before? Do you know what to change in your Maya scene or V-Ray parameters to eliminate the warnings?
Thanks.

[Morbid Angel]

yeah, it can be related to the crease data with open subdiv. Are you using edge creasing? It could also be that some geometry has double faces, or verts on top of other verts so open subdiv has issue with it.

[vanpixelguy]

Yep, we are using crease sets in Maya which is why the Open Subds but we haven't definitely figured out if the messages are specific to the use of crease sets Once we do narrow down an offending scene to the "bad" geometry the problem goes away when you apply any editing operation to the geometry, suggesting that the mesh might be in some sort of "bad state". Anyway the scenes render correctly, its just that when you get all these messages being output it really slows down rendering.

Did you find any definitive way to determine the problematic geometries in a scene? I'd like to get a list of the geos with the bad data.

[Morbid Angel]

I think when you add crease to edge its recorded in polyCrease node, you can check that value of the crease there. See if you have any values that are insanely high, it could be the reason you have those messages.

[vanpixelguy]

I'll check it out. We've found a few culprit objects in the scenes we're examined to date.