-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in Model class SDKMESH loader #13
Comments
I assume you mean the
I see it has two mesh parts, and I don't see any specific reason why it wouldn't work. Let me try it out. |
Hello, sorry, I meant 2 subsets. Regards |
To render |
Ok, I'll try that, thanks for your advise. |
One quick hack for this specific model is to reach into the first
|
I tried checking the values of the meshParts members of the mentioned mesh: For the first meshPart I get: For the second one I get: I wonder if I should be getting different values for startIndex, vertexOffset or vertexStride for the second meshPart, or I am doing something wrong? Thanks |
I see the problem. That model uses a non-zero vertexStart value for the second subset which is an offset to each index in the IB. |
Ignore my original comment about The fix is to add a single line to
Thanks for digging into this one. I also need to add this information to my |
Fix submitted. Will be included in the next release. Thanks! |
BTW, after updating my dump utility, I can see the offset is in use:
The Sample Content Exporter never uses a non-zero |
That's great! thanks. |
I think I found a bug when loading and rendering the island.sdkmesh using a Model class object. The island.sdkmesh model has two mesh parts but only one is rendered.
The text was updated successfully, but these errors were encountered: