[DiscordArchive] did you also used the last skin as the only skin ?
[DiscordArchive] did you also used the last skin as the only skin ?
Original source
did you also used the last skin as the only skin ?
rektbyfaith
07-31-2024, 11:40 PM #1Archived author: A2 • Posted: 2024-07-31T23:40:07.499000+00:00
Original source
did you also used the last skin as the only skin ?
Original source
DBC has nothing to do with skin files
rektbyfaith
07-31-2024, 11:40 PM #2Archived author: A2 • Posted: 2024-07-31T23:40:49.272000+00:00
Original source
DBC has nothing to do with skin files
Original source
```
0x00684527 read 0x????????
A .skin file's releated issue. Most likely keybone/bone related This error seems to relate directly to the actual bone structure AND bone indices of a (usually custom) .m2. This could mean anything from BoneLookupTable to the actual order by which bones are generated. We we're able to see that this error can sometimes be caused by a parent structure involving a parent with a higher index than its child (0>50>3) Bone 0 can be Bone 50's parent, but not the other way around. In most cases this ends up being the root bone with a very high index, root should almost always be 0. Another solution involves swapping the mesh of the broken model and giving it a new, already working, bone structure. A symptom of this phenomenon, before an error is produced, may show a model with "jitteriness" when the camera is moved in-game.
```
rektbyfaith
07-31-2024, 11:53 PM #3Archived author: Kebful • Posted: 2024-07-31T23:53:56.458000+00:00
Original source
```
0x00684527 read 0x????????
A .skin file's releated issue. Most likely keybone/bone related This error seems to relate directly to the actual bone structure AND bone indices of a (usually custom) .m2. This could mean anything from BoneLookupTable to the actual order by which bones are generated. We we're able to see that this error can sometimes be caused by a parent structure involving a parent with a higher index than its child (0>50>3) Bone 0 can be Bone 50's parent, but not the other way around. In most cases this ends up being the root bone with a very high index, root should almost always be 0. Another solution involves swapping the mesh of the broken model and giving it a new, already working, bone structure. A symptom of this phenomenon, before an error is produced, may show a model with "jitteriness" when the camera is moved in-game.
```
1 Guest(s)
1 Guest(s)