- — File Parsing Boot Camp — - (Some file structures added)

[DarkPikachu]

ok...
so I've put a message in my template:
"if_you_are_seeing_this_contact_me(Tcll5850)_immediatly"

I couldn't use proper punctuation as I put it over a var

but you will see it if you have data for the unknown list offsets.
(I'll post an img of what you'll see once I release)

[Xiggah]

Your template, eh? I do a fine job of finding the Brawl files I'm looking for, so I'd be great at helping. I eagerly await your template.

[DarkPikachu]

Your template, eh? I do a fine job of finding the Brawl files I'm looking for, so I'd be great at helping. I eagerly await your template.

yeh...
I'm only 3 TODO's away from an excelent release though
(right now it's only decent)

1 - implement a better method for reading from the resource groups
2 - update the vertex colors to the current method (should look like the vector groups)
3 - implement a mature method for reading from the TEV structures
(currently just reading a specified count for the registers)

but that's all

I hated restructuring the MDL0 map the most D:

but yeh...
I can pretty much call this thing done for a decent release
now if I can get to a compy with net XD
(wish the wii could UL) >_<

[Xiggah]

I can't wait, especially if it helps Brawl's mdl0 format a bit. One hunch I have is to search that Trace trophy, that misrendered trophy is just asking for an examination.

[DarkPikachu]

I can&#039;t wait, especially if it helps Brawl&#039;s mdl0 format a bit. One hunch I have is to search that Trace trophy, that misrendered trophy is just asking for an examination.

IKR XD
it's bugging me too

I've never seen an MDL0 with that many primitives before >_>

[DarkPikachu]

just found a small (nothing to worry about) problem with my template...

while reading the registers,
instead of the register being called "BP_MASK", the register will take on the name of the child register...

so you'll end up having:
BP "KSEL[7]"
  BP "KSEL[7]"

the first register is really the mask >_>

again... nothing big...

I have work to do on the section anyways so... blah...

[DarkPikachu]

well I'm at least doing something IK I can do before releasing my template...

I'm UD-ing the color values to read based on the format...

UUGH!!!
I have to decode RGB565/RGB5A3 data again DDX
I HAAATE that format...
but at least that's the one I got working in my REFT viewer >_>
(it's CMPR that never got finished) DX

anyways...
you should be able to see the actual color values in the structure before the values...

eg:
----Color R,G,B,A = ( 255 , 255 , 255 , 255 )

and also...
unlike the vectors that only parse the first vector,
I'm parsing all the colors as the most I've seen was near 50...
(shouldn't affect the template load time by much at all)

EDIT:
wait...
I got that mixed up...
5+6+5 = 16

I was thinking of RGB5/RGB4A3
(the 16th bit declares the format)

[DarkPikachu]

I'm currently running tests on different MDL0's and adding extra display data...
(just so you don't have to open the header to see the data)

so far I've had no errors

and I've changed the "Is_XYZ" data in the vectors back to "has_bounds"

so now that's displayed for Verts, Normals, and UV's.
(all 3 use the same structure)

I've added alot of (but not all) support for float values...
(can't use Design mode to edit my template (have to copy/paste the text))

all that's left on my TODO list is a better method for the Resource Groups, and reading the register data correctly...
(also have to look into the unknown data)

all in all...
this release is about 94% ready =D

[BlackJax96]

Tcll, for a second there I was trippin' ballz n thought this was one of your threads.
Maybe you should let someone else post.

[DarkPikachu]

Tcll, for a second there I was trippin&#039; ballz n thought this was one of your threads.
Maybe you should let someone else post.

lol...
it's been "my" thread for nearly all day
(nobody's posted)

yeh...
sry for multi-posting though... heh [/bamf]

[DarkPikachu]

all night and no reply

anyways...
in the material header...
has anything been figured out about the P4 and P6 offsets??

[Sky Grounder]

all night and no reply

Well you're mostly talking about MDL0, and MDL0 is so freaking advanced/complicated, so most people don't know much about. That's why they don't reply much.
Thus you always talk about your template

[DarkPikachu]

Well you're mostly talking about MDL0, and MDL0 is so freaking advanced/complicated, so most people don't know much about. That's why they don't reply much.
Thus you always talk about your template

alright... I'll give ya that then... heh...

and yea...
I'm talking about my template because it's now 96% ready for release
(just have a few more things to declare and redefine)

I'll talk more about other stuff when I finish my template

actually... I'll be talking more about UMC development ideas,
but I'll try to keep that more directed to my thread...
(nobody seems to have any ideas to offer though) >_>
^just want to know what to implement to make a decent release is all...

EDIT:
98% ready

just have a little on materials, textures, and pallets to finish

[DarkPikachu]

hey Xiggah...
I think I've just looked upon something that's delayed my template...

in the shader (material data) you have the texture clamps and texture matrices...

first off...
I think I have the texture clamps correct in their read order as the data seems to fit...
here's the structure I'm going by:
Angle = f32()
MaxX = f32()
MaxY = f32()
MinX = f32()
MinY = f32()

Min# and Angle are always 0 in the MDL0's I've tested...

anyways...
the texture matrices don't seem to fit the layout >_>

here's what I have:
unk1,unk2,unk3,unk4 = f32(),f32(),f32(),f32()
matrix = mtx_3x4()

I'm getting NAN values that look like they should be:
v1 = s16()
v2 = u16()

note: those values appear randomly throughout the layout...


you can read the brbx src better than me...
so I ask:
what is the proper data layout for both of them??

[Xiggah]

Well you're mostly talking about MDL0, and MDL0 is so freaking advanced/complicated, so most people don't know much about. That's why they don't reply much.
Thus you always talk about your template

I know, we could always talk about your event match files. That sounds interesting to look into.