API Error Unexpected Primitive Type 4 and 254 Tweet

[rafg]

Anyone familiar with this Octane API error? It's crashing Houdini and Octane.
"unexpected primitive type 4"
or
"unexpected primitive type 254"

Unfortunately I can't provide a file.

Rather high poly geometry but not an issue for Houdini.

Going to keep troubleshooting on my end but would be helpful to know if this is a known error and how to approach it. Thanks

[juanjgon]

Sorry, I had not seen these errors before. It could be great to have an example scene to reproduce this problem here.

Thanks,
-Juanjo

[rafg]

I've backtracked the error to the velocity "v" attribute.

I am transferring a custom velocity attribute from mesh A to mesh B. Then multiplying that custom velocity attribute with Mesh B's velocity to get a final v attribute. It has been rendering until it hits a certain frame. So now that I know it's v maybe I can try a few things.

Not sure if I'd be able to create an example file that has this same issue. But if I can't find a solution on my own I will try and replicate the issue for you. Thanks!

[rafg]

Juanjo

I've been trying like heck to replicate this issue outside my main file with no success. Is there a deeper program level I can access through Houdini or Octane to troubleshoot what is happening?

In general what is an "Unexpected Primitive Type" ? Just a bad geometric shape that sometimes Octane renders and sometimes not?

Overall it still seems to be related to velocity multiplication I'm using like below to control motion blur. Which works in my example file but not in my project file.

Thanks.

Raf

[rafg]

Reducing point/poly count seems to be helping. Will need to test a few more things, but I can get through a render sequence for the moment.

Not sure why I wouldn't get a warning more specific to a hard poly limit hit rather than a vague Unexpected Primitive Type error.

[juanjgon]

Hmm, if you have 23M points or polygons in a single object, you can indeed be reaching some kind of Octane core limitation, although it can depend on the other attributes that you have in the object, like UV maps, vertex attributes, or as you say the "v" velocity attribute.

You could try to import half of this object into an additional OBJ node to check if it helps.

Thanks,
-Juanjo