I don't think it's a shader problem per se. It may be a shader problem indirectly, e.g. something in the mesh might be misbehaving. I don't know anywhere near enough to know where to go from here, either. It could be meta data (which gave me some issues in another game), but my method of stripping that (dumping it to obj and re-importing it) tends to strip out other information, too. You could try it, though, and see what happens.
The bug wouldn't show up on the mesh while it was in the base t-pose animation, only when the m3a was actually loaded in the cinematics editor. With the animations on the mesh normally, no such problem ever occurred. I tried resetting normals, welding, changing materials, just about everything I could think of. The only real possible hint I got is that the morphs were getting screwed up. I don't know animation, so I couldn't say what that even is. Is your mesh animated? Does it look fine when you strip out the animations?
I have yet to encounter it again because I just load the animations with the m3 normally for everything. Though if I do, I'll be sure to post about it.
I actually had this problem happen when I used m3a animations on a model. I could only fix it by leaving the animations in the model. While I doubt this is your problem, that is my only experience with it in the past. I tried everything and was never able to fix it while leaving the animations as an m3a.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I don't think it's a shader problem per se. It may be a shader problem indirectly, e.g. something in the mesh might be misbehaving. I don't know anywhere near enough to know where to go from here, either. It could be meta data (which gave me some issues in another game), but my method of stripping that (dumping it to obj and re-importing it) tends to strip out other information, too. You could try it, though, and see what happens.
You'd be correct, that's a lineage 2 model.
The bug wouldn't show up on the mesh while it was in the base t-pose animation, only when the m3a was actually loaded in the cinematics editor. With the animations on the mesh normally, no such problem ever occurred. I tried resetting normals, welding, changing materials, just about everything I could think of. The only real possible hint I got is that the morphs were getting screwed up. I don't know animation, so I couldn't say what that even is. Is your mesh animated? Does it look fine when you strip out the animations?
I have yet to encounter it again because I just load the animations with the m3 normally for everything. Though if I do, I'll be sure to post about it.
I actually had this problem happen when I used m3a animations on a model. I could only fix it by leaving the animations in the model. While I doubt this is your problem, that is my only experience with it in the past. I tried everything and was never able to fix it while leaving the animations as an m3a.