very interesting nodes here.the extent data looks a little similar to the pilot mesh extent tree. here's a node breakdown:

<pre><font size=1 face=Courier>Particle Event>
>particle1.def(unsure)
>animation library(say whaa?)
>XP_HERM
>texture count(integer)
>frame count(integer)
>frame rects(unsure)
>texture library
>XP_HERM0
>U wrap mode(integer)
>V wrap mode(integer)
>MIP0(of
>image X size(integer)
>image Y size(integer)
>palette 8 bit
>palette color count(integer)
>palette RGB 888(unsure could be float or integer from all i can tell)
>image indices(unopenable except as empty string)
>scale(float)
>point extent(integer?)

[URigid Body[/u
>Mass properties(floats)
>Mass
>Center of mass
>Inertia tensor(float array)
>Extent data (all floats)
>Bounding volume
>Sphere
>center
>radius
>Box
>center
>half x
>half y
>half z
</font></pre>

hopefully this is helpful for our ALE decrypters


Edited by - Cold_Void on 6/1/2005 9:39:14 PM

PTE was in fact a predecessor format to ALE used by DA at some point (much like the way they went through at least three CMP incarnations, only those were all kept), but, as its structure is different, doesn't really say a lot about the latter, unfortunately.

All right, but is there any way to IMPLAMENT this .pte file? As it stands now? Because it seems interesting. And, furthermore, if we can get .pte files to work, couldn't it be a back-door solution to modifying .ale files?

MK

Actually the .pte seems useless and seems to be some leftover file they forgot to delete when they sent the file package to the burners. I would have to agree with Nephilim that it appears to be the precursor to the ALE format. However, if you have been looking at the thread here - you can see I've made substantial progress on decoding ALE files and I hope to have documentation (and hopefully more.. but i'm not making any promises..) in the next few days on these effects. I have more or less figured out the whole format with exception of some minor things I haven't quite figured out yet. I'll keep you all posted.