[DiscordArchive] depends very much on why your skin file has 0 bones. how did you create it?
[DiscordArchive] depends very much on why your skin file has 0 bones. how did you create it?
Original source
depends very much on why your skin file has 0 bones. how did you create it?
rektbyfaith
04-18-2022, 06:24 PM #1Archived author: <o> • Posted: 2022-04-18T18:24:57.718000+00:00
Original source
depends very much on why your skin file has 0 bones. how did you create it?
Original source
<@207762379776327681>
```
// to human
player->SetDisplayId(19723);
player->SetNativeDisplayId(19723);
```
- if i set it to 49 (base human character model from creaturedisplayinfo) model can wearing equipment but face hair skin is broken
- 19723 using human m2 model but has extra flag to setup hair etc, model are showing correct but cant see wearing equipment
![[Image: Bez_nazvu-2.png?ex=690c41a5&is=690af025&...ba8765866&]](https://cdn.discordapp.com/attachments/415944535718494208/965681945180770334/Bez_nazvu-2.png?ex=690c41a5&is=690af025&hm=0b6b62f7c3979c49df01a9dca4626d6e974b3c237f3b187d09e17bdba8765866&)
rektbyfaith
04-18-2022, 06:35 PM #2Archived author: Lucifer • Posted: 2022-04-18T18:35:17.492000+00:00
Original source
<@207762379776327681>
```
// to human
player->SetDisplayId(19723);
player->SetNativeDisplayId(19723);
```
- if i set it to 49 (base human character model from creaturedisplayinfo) model can wearing equipment but face hair skin is broken
- 19723 using human m2 model but has extra flag to setup hair etc, model are showing correct but cant see wearing equipment
Original source
Using Hutchys guide, line for line
rektbyfaith
04-18-2022, 06:46 PM #3Archived author: Sanctuary • Posted: 2022-04-18T18:46:58.872000+00:00
Original source
Using Hutchys guide, line for line
Original source
do you have a link to that
rektbyfaith
04-18-2022, 06:47 PM #4Archived author: <o> • Posted: 2022-04-18T18:47:17.298000+00:00
Original source
do you have a link to that
Original source
https://model-changing.net/index.php?app...iew&id=157
rektbyfaith
04-18-2022, 06:48 PM #5Archived author: Inevitable • Posted: 2022-04-18T18:48:12.819000+00:00
Original source
https://model-changing.net/index.php?app...iew&id=157
Original source
oh right, retroporting is out of my paygrade all i can give is some very quick theory:
- in your m2 file, you have an array of "bones", these are the actual bones in your model
- in your m2 file, you also have an array of "bone lookups", this is just an array containing indices to the previous bone struct. (a value of "5" in this array refers to the fifth bone in the "bones" array)
- in your geoset (inside .skin), you have the properties "bone offset" and "bone count". "Bone offset" is an offset into the "bone lookups" array inside the m2 file, and "bone count" is how many of those bone ids this geoset uses. What this effectively does is specify what set of bones this geoset uses at all, and is used as a basis for all the vert properties that it contains
rektbyfaith
04-18-2022, 06:55 PM #6Archived author: <o> • Posted: 2022-04-18T18:55:05.642000+00:00
Original source
oh right, retroporting is out of my paygrade all i can give is some very quick theory:
- in your m2 file, you have an array of "bones", these are the actual bones in your model
- in your m2 file, you also have an array of "bone lookups", this is just an array containing indices to the previous bone struct. (a value of "5" in this array refers to the fifth bone in the "bones" array)
- in your geoset (inside .skin), you have the properties "bone offset" and "bone count". "Bone offset" is an offset into the "bone lookups" array inside the m2 file, and "bone count" is how many of those bone ids this geoset uses. What this effectively does is specify what set of bones this geoset uses at all, and is used as a basis for all the vert properties that it contains
Original source
there might be a much easier fix with this specific tool, but i don't know how it works
rektbyfaith
04-18-2022, 06:56 PM #7Archived author: <o> • Posted: 2022-04-18T18:56:10.207000+00:00
Original source
there might be a much easier fix with this specific tool, but i don't know how it works
Original source
Just for a simple example, if your model has 500 bones and its bone_lookup array looks like this: [5,25,8,6,4,9]
and you have a geoset with bone_offset=2 and bone_count=3, then your geoset uses bone ids 8,6 and 4
rektbyfaith
04-18-2022, 06:58 PM #8Archived author: <o> • Posted: 2022-04-18T18:58:17.556000+00:00
Original source
Just for a simple example, if your model has 500 bones and its bone_lookup array looks like this: [5,25,8,6,4,9]
and you have a geoset with bone_offset=2 and bone_count=3, then your geoset uses bone ids 8,6 and 4
Original source
for any vertprops in your skin that belongs to this geoset, bone id 0 refers to 8, bone id 1 refers to 6 and bone id 2 refers to 4
rektbyfaith
04-18-2022, 06:59 PM #9Archived author: <o> • Posted: 2022-04-18T18:59:01.835000+00:00
Original source
for any vertprops in your skin that belongs to this geoset, bone id 0 refers to 8, bone id 1 refers to 6 and bone id 2 refers to 4
Original source
i think it was alastor who told me once, but the issue is in the m2?skin? you gotta change the value of nbones from 0 to something else in the header so it can attempt to find it
rektbyfaith
04-18-2022, 07:01 PM #10Archived author: tester • Posted: 2022-04-18T19:01:06.980000+00:00
Original source
i think it was alastor who told me once, but the issue is in the m2?skin? you gotta change the value of nbones from 0 to something else in the header so it can attempt to find it
1 Guest(s)
1 Guest(s)