OBD talk:Oni Binary Data: Difference between revisions

OBD talk:Oni Binary Data (view source)

Revision as of 11:05, 1 February 2007

2,021 bytes added , 1 February 2007

m

misc, enjoy

Geyser

Administrators

5,389

edits

@@ Line 44: / Line 44: @@
 ::;ssg
 :I'll have a look at the hidden doors in level1. Fixing them is all the more appealing as now we can fix the BNVs, too...
-::Thanks for the two IDs: they're a good start. I'll try to cath'em all (when I get some free time, heh).
+::Thanks for the two IDs: they're a good start. I'll try to catch'em all (when I get some free time, heh).
 :::Collision is probably defined separately from the visible geometry (in the AGQC rather than in the AGQG).
 :Unfortunately, '''env_show''' only works for "objects" (static bike, van, truck, etc). Same for '''env_texswap'''...
 ::[[User:Geyser|geyser]] 15:37, 26 January 2007 (CET)
+:I've had a look at those doors. Rather than making them invisible (what for? no one said invisible walls don't block you), I made those walls into a floor and ceiling, by swapping two pairs of vertices.
+:For the floor, I edited the AGQC accordingly. Since the now-horizontal quad still thought it was a wall, I had to (un)set the appropriate flag(s) in the bitset.
+:It looks and feels quite nice since there is a doorsill now. Wonder if pathfinding will work when the grid is fixed...
+:Is there any way to look up the ID of a quad in Oni other than by browsing '''env_highlight_gq''' values?
+:I'm interested in the quad just above the original 18454, but couldn't find it after a quick search.
+::[[User:Geyser|geyser]] 12:05, 1 February 2007 (CET)
 ----
 ==File names==
@@ Line 79: / Line 83: @@
 ::;ssg
 :Re:Obviously, I don't want to argue about this forever. I'll reformulate when I get the chance.
-:My basic point is that there is no "0" bit, and no "option" corresponding to it, and that anything stating otherwise, e.g.
+:My basic point is that there is no "0" bit, and no "option" corresponding to it, and that anything hinting otherwise, e.g.
   option 1; it's a bitset; the following options are possible (values in dec):
-  - none
+  - none          <<<<<<<<<<<<<<<<<<<<^^^^^^^
   - unknown
   - ghost
@@ Line 90: / Line 94: @@
 - unknown
 - unknown
-:is... pick your own word. ^^
+:is... is... whatever. Pick your own word. ^^
 ::[[User:Geyser|geyser]] 20:15, 30 January 2007 (CET)
 :Anyway, I'd suggest to leave "dec" alone altogether, and to write:
@@ Line 104: / Line 108: @@
 :Love it or leave it, of course.
 ::[[User:Geyser|geyser]] 13:54, 31 January 2007 (CET)
-:Oh, and a priori I don't WTF "ghost" is, so in case you know better, a few words of wisdom are always welcome.
+:Oh, and a priori I don't know WTF "ghost" is, so in case you know better, a few words of wisdom are always welcome.
 ::[[User:Geyser|geyser]] 13:56, 31 January 2007 (CET)
@@ Line 132: / Line 136: @@
 :Be careful not to overwrite new information with older stuff, or anything like that.
 :I'd really appreciate if you put a list of field types [[OBD:Data types|HERE]], for example.
-::IMO that's absolutely not "rhetorical". Whatever you think "rhetorical" means... ^^
 ::[[User:Geyser|geyser]] 20:15, 30 January 2007 (CET)
@@ Line 148: / Line 151: @@
 :My a priori guess would be the ONOA, and the IDXA therein. 3003 could refer to the unknown ID stored inside an ONOA.
 ::[[User:Geyser|geyser]] 20:15, 30 January 2007 (CET)
+:OK, I found where the 3003 is mapped to 3058 etc. I'd have been quicker if you hadn't flagged AKEV as "done" :P
+:Because it's in the AKEV. Well, not in the AKEV "selbst", but in its specific IDXA.
+::(but they're just ''links'', of course, so we don't consider them as unknown AKEV data, right? ^^ )
+:Anyway. The first IDXA lists the quads (AGQG, AGQC and AGQR entries) that can be turned on and off.
+:The second IDXA lists the "gunk" IDs in parallel. The same "gunk" ID can be assigned to several quads.
+:The two IDXA can be used for two-way lookup. Only gunk -> quad is used when you use '''env_show''' etc.
+::[[User:Geyser|geyser]] 12:05, 1 February 2007 (CET)
+:As for the ONOA, that one is related to the unknown field of the AGQG (the one which is not always 0xFFFFFFFF).
+:That field is an object ID, looked up in the ONOA. Several quads can belong to the same object (same ID).
+:The IDXA next to the ID (in the ONOA) lists the AGQG belonging to every object. So, two-way lookup.
+:The high byte of the ID is an object type. 0x05 is furniture, 0x03 is doorframe, 0x0D is trigger guide, 0x0F is console, etc.
+::[[User:Geyser|geyser]] 12:05, 1 February 2007 (CET)
 ==Generic files==
 ===VCRA===
@@ Line 155: / Line 170: @@
 ===IDXA===
 :Used by M3GM (1 lists triangles as strips, 2 assigns face normals to triangles) (1 has a specific format (high-bit))
-:Used by AKEV (role?)
+:Used by AKEV (1 lists script-hideable quads) (2 lists the IDs used by '''env_show''' etc)
+:Used by ONOA (an "object ID" is associated to an IDXA listing the AGQG of that object)
 :Used by AKOT (role?)
-:Used by ONOA (role?)
 :Is that all?
 ::[[User:Geyser|geyser]] 20:15, 30 January 2007 (CET)