830
edits
Talk:Importing character models: Difference between revisions
explanation
(note to Ed) |
(explanation) |
||
| Line 52: | Line 52: | ||
:Oh, and Ed: you're saying confused/confusing and possilby wrong things up there about not messing up file sizes. The header of an .oni file doesn't actually know or care about the total file size. The only thing you should care about for an ONCC is the offsets of the names of the dependencies, at the end (one offset for every name). That's where you can't allow to make the name of the linked-to TRBS longer without shifting all the following dependencies of the ONCC and updating their name offsets consistently. As for the name of the ONCC itself, you can rename the file to anything at all, like ONCCgriffin_generic_fubar.oni : OniSplit will ignore the internal name of the root instance and use the filename instead. And as for the ONCC name in [[CHAR]], it's a fixed-size array (char[64]), so virtually any new name will work, as long as you take care of the null char after the ONCC name. | :Oh, and Ed: you're saying confused/confusing and possilby wrong things up there about not messing up file sizes. The header of an .oni file doesn't actually know or care about the total file size. The only thing you should care about for an ONCC is the offsets of the names of the dependencies, at the end (one offset for every name). That's where you can't allow to make the name of the linked-to TRBS longer without shifting all the following dependencies of the ONCC and updating their name offsets consistently. As for the name of the ONCC itself, you can rename the file to anything at all, like ONCCgriffin_generic_fubar.oni : OniSplit will ignore the internal name of the root instance and use the filename instead. And as for the ONCC name in [[CHAR]], it's a fixed-size array (char[64]), so virtually any new name will work, as long as you take care of the null char after the ONCC name. | ||
::[[User:Geyser|geyser]] 21:57, 5 June 2008 (CEST) | ::[[User:Geyser|geyser]] 21:57, 5 June 2008 (CEST) | ||
:::Maybe I'm confused, but, if you look at offset 0x0030 in an ONCC or TRAC .oni file, I thought that offset pointed to the end of the file. For example ONCCkonoko_generic.oni has 8017 and that points to 0x1780, ONCCbarabus is A016 that points to 0x16A0. Also, that's what I documented at http://wiki.oni2.net/OBD_talk:TRAC and if that point was incorrect, I'm sure someone would have corrected it. So based on that information, I made the statement about not messing up the file size, while using a hex editor. Also, I knew about being able to rename the file to anything else, that's what I did with the files related to the Motoko character. | |||
:::[[User:EdT|EdT]] 23:00, 5 June 2008 (CEST) | |||