has a mismatch between vertices and textures

[ajr0717]

and it will not be loaded into the Octane scene.

Can anyone please help me by fixing my prop so I can not have this come up for every scene I have?
Its an invisible light prop I have seven or eight copies of in every one of my scenes and it plagues me!

I just bought this plugin and its standalone yesterday

[face_off]

Hi - that error message generally means there is a different number of UV coordinates to vertices, so there is a modelling error with the geometry. If you send me the OBJ file, I can take a closer look. Sometimes exporting the prop to 3ds max format and importing back in will fix it.

Paul

[ajr0717]

How do I get this OBJ to YOU?
(ie: Octane mail, Hotmail?)

[face_off]

Email to paul at physicalc-software dot com.

Paul

[samhal]

Paul,

Curious about this as well.

I also run into the vertices/texture mismatch due to a modeling error occasionally. The plugin doesn't like it and ignores it while Poser happily chugs along. I'm guessing Poser is more forgiving about things like this, but why? ...and what would happen if the plugin allows it to go thru?

Thanks,
Sam

[wimvdb]

I occasionally have this as well, often by the same prop maker. Almost all of his props are fine, but every once in a while a few have this problem.
If i come across one, I send him a message and get a correct one back and usually he updates the package at the store.
If i remember correctly it needed a simple operation such as Normalize UVMap (or coordinates).

[samhal]

Thanks wim! I'll try contacting the creator.

Still, why doesn't Poser care while the plugin says "ah, hell no!"

Sam

[wimvdb]

I do not know, but it is probably Octane itself who does not know what to do with coordinates outside the uvmap (which is what happens). Maybe it cuts those off and Poser puts them on the edge, which would explain the mismatch.