OBD talk:M3GM: Difference between revisions

m
+cat
m (M3GM talk moved here)
 
m (+cat)
 
(2 intermediate revisions by 2 users not shown)
Line 5: Line 5:
::;geyser
::;geyser
:M3GM contains only links, so it's done. (I don't look to the hierarchy.)
:M3GM contains only links, so it's done. (I don't look to the hierarchy.)
:VCRA and IDXA ==> [http://www6.fh-eberswalde.de/user/dkriesch/oni/werte.htm Any ideas?]
:VCRA and IDXA ==> <nowiki>http://www6.fh-eberswalde.de/user/dkriesch/oni/werte.htm</nowiki> Any ideas?
::;ssg
::;ssg
:IDXA and VCRA (and PNTA, even) are generic: they get interpreted in different ways depending on where they're linked to ''from''.
:IDXA and VCRA (and PNTA, even) are generic: they get interpreted in different ways depending on where they're linked to ''from''.
Line 13: Line 13:
::(and in other cases, the high bit will mean something completely different)
::(and in other cases, the high bit will mean something completely different)
:Knowledge about IDXA etc should be detailed specifically to the resources that link to them: for example, the M3GM.
:Knowledge about IDXA etc should be detailed specifically to the resources that link to them: for example, the M3GM.
::Look at your [http://www6.fh-eberswalde.de/user/dkriesch/oni/werte.htm werte.htm] again. See how all the generic sub-resources of an M3GM are connected? They simply don't make the same sense when considered out of the M3GM's context...
::Look at your site <nowiki>http://www6.fh-eberswalde.de/user/dkriesch/oni/werte.htm</nowiki> again. See how all the generic sub-resources of an M3GM are connected? They simply don't make the same sense when considered out of the M3GM's context...
:That's why I say M3GM is not "done": because [http://www6.fh-eberswalde.de/user/dkriesch/oni/werte.htm THIS] is missing knowledge relative to ''M3GM'', ''not'' VCRA or IDXA...
:That's why I say M3GM is not "done": because <nowiki>http://www6.fh-eberswalde.de/user/dkriesch/oni/werte.htm</nowiki> is missing knowledge relative to ''M3GM'', ''not'' VCRA or IDXA...
::Sometimes the hierarchy is crucial, i.e., you have to consider a file together with its children/parents.
::Sometimes the hierarchy is crucial, i.e., you have to consider a file together with its children/parents.
:M3GM: Again, they contain only links, so it's done. I know that there're different IDXA and VCRA files, so they are not done, because there is still no differentiation between the different files.
:M3GM: Again, they contain only links, so it's done. I know that there're different IDXA and VCRA files, so they are not done, because there is still no differentiation between the different files.
Line 23: Line 23:
::[[User:Geyser|geyser]] 19:30, 30 January 2007 (CET)
::[[User:Geyser|geyser]] 19:30, 30 January 2007 (CET)
----
----
:Most of the stuff is as ssg says [http://www6.fh-eberswalde.de/user/dkriesch/oni/werte.htm HERE].
:Most of the stuff is as ssg says here: <nowiki>http://www6.fh-eberswalde.de/user/dkriesch/oni/werte.htm</nowiki>.
:*PNTA, TXCA, first VCRA: vertex map (XYZ, UV, vertex normals). Vertex normals used for Gouraud shading.
:*PNTA, TXCA, first VCRA: vertex map (XYZ, UV, vertex normals). Vertex normals used for Gouraud shading.
:*Second VCRA: face normals, for flat shading (not sure the engine ever switches from Gouraud to flat) and specular effects.
:*Second VCRA: face normals, for flat shading (not sure the engine ever switches from Gouraud to flat) and specular effects.
Line 39: Line 39:
:door example: I don't agree with you, that they are "strips".
:door example: I don't agree with you, that they are "strips".
:Biturn says, that they're triangles and you have to read the first IDXA in this way:
:Biturn says, that they're triangles and you have to read the first IDXA in this way:
http://www6.fh-eberswalde.de/user/dkriesch/oni/doorcode.gif
<nowiki>http://www6.fh-eberswalde.de/user/dkriesch/oni/doorcode.gif</nowiki>
:grey = high bit, red = same as the first column, yellow = same as the first row column but first and second value switched
:grey = high bit, red = same as the first column, yellow = same as the first row column but first and second value switched
:If you read it step by step (I used Rhino3D), you get this:
:If you read it step by step (I used Rhino3D), you get this:
http://www6.fh-eberswalde.de/user/dkriesch/oni/door.gif
<nowiki>http://www6.fh-eberswalde.de/user/dkriesch/oni/door.gif</nowiki>
::;ssg
::;ssg
:That's ''exactly'' what strips look like. I couldn't have illustrated them better myself. Thanks. ^^
:That's ''exactly'' what strips look like. I couldn't have illustrated them better myself. Thanks. ^^
Line 81: Line 81:
::[[User:Geyser|geyser]] 19:30, 30 January 2007 (CET)
::[[User:Geyser|geyser]] 19:30, 30 January 2007 (CET)
::As for the first VCRA: they are vertex normals (basically, averages of the face normals for the adjacent faces). Normalized.
::As for the first VCRA: they are vertex normals (basically, averages of the face normals for the adjacent faces). Normalized.
:::Oni (OpenGL) uses them for [http://en.wikipedia.org/wiki/Gouraud_shading Gouraud shading].
:::Oni (OpenGL) uses them for [[wikipedia:Gouraud_shading|Gouraud shading]].
::;geyser
::;geyser
:I'm not sure why so many entries are necessary for the PNTA and the first VCRA. To fix vertex lighting?
:I'm not sure why so many entries are necessary for the PNTA and the first VCRA. To fix vertex lighting?
Line 92: Line 92:
:Regardless of technical issues, they have to duplicate PNTA entries because a vertex can have different UV and normals depending on what face it belongs to. And since all 3 arrays run alongside each other (indexed by the same ID in the first IDXA), PNTA has to be extended accordingly.
:Regardless of technical issues, they have to duplicate PNTA entries because a vertex can have different UV and normals depending on what face it belongs to. And since all 3 arrays run alongside each other (indexed by the same ID in the first IDXA), PNTA has to be extended accordingly.
::[[User:Geyser|geyser]] 19:30, 30 January 2007 (CET)
::[[User:Geyser|geyser]] 19:30, 30 January 2007 (CET)
{{OBD}}