OBD talk:Instance file format: Difference between revisions
Jump to navigation
Jump to search
(questions) |
m (+cat, wiki touchup) |
||
| Line 1: | Line 1: | ||
I | I want to raise a couple of questions about the instance files as they occur in Oni's original resources: | ||
*As mentioned [http://ssg.oni2.net/subfold/datfile/chap2p1.htm HERE], the "flags" bitset in the instance descriptor for non-empty files are actually '''0x01 00 10 00''', '''0x09 00 10 00''', or '''0x00 00 30 00'''. I've added a mention of those other 2 bits (0x00 00 '''10''' 00 and 0x00 00 '''20''' 00), but since they occur systematically, it would be nice to know why, or at least to confirm that the current engine ignores those two bits. | *As mentioned [http://ssg.oni2.net/subfold/datfile/chap2p1.htm HERE], the "flags" bitset in the instance descriptor for non-empty files are actually '''0x01 00 10 00''', '''0x09 00 10 00''', or '''0x00 00 30 00'''. I've added a mention of those other 2 bits (0x00 00 '''10''' 00 and 0x00 00 '''20''' 00), but since they occur systematically, it would be nice to know why, or at least to confirm that the current engine ignores those two bits. | ||
*Do we have a list of files (instances) that are both unnamed and unreferenced? (and will thus be discarded by OniSplit's '''-export'''? At least one known example of such "orphan" files are the unnamed TRCM of level0_Final. Has anyone come across any others, I wonder. | *Do we have a list of files (instances) that are both unnamed and unreferenced? (and will thus be discarded by OniSplit's '''-export'''? At least one known example of such "orphan" files are the unnamed TRCM of level0_Final. Has anyone come across any others, I wonder. --[[User:geyser|geyser]] 12:47, 21 May 2018 | ||
{{OBD}} | |||
Latest revision as of 16:14, 4 May 2022
I want to raise a couple of questions about the instance files as they occur in Oni's original resources:
- As mentioned HERE, the "flags" bitset in the instance descriptor for non-empty files are actually 0x01 00 10 00, 0x09 00 10 00, or 0x00 00 30 00. I've added a mention of those other 2 bits (0x00 00 10 00 and 0x00 00 20 00), but since they occur systematically, it would be nice to know why, or at least to confirm that the current engine ignores those two bits.
- Do we have a list of files (instances) that are both unnamed and unreferenced? (and will thus be discarded by OniSplit's -export? At least one known example of such "orphan" files are the unnamed TRCM of level0_Final. Has anyone come across any others, I wonder. --geyser 12:47, 21 May 2018