ForOhFor's Python Nest [Collisions to shadow system program released! 10/11/11]

[DarkPikachu]

heh... actually 404...
all your program does is delete the 3 unk offsets,
and then adds 'FFFFFFFF' * 3 to the end of the header. (before the pipelines)

then it changes the header length with a hard-coded length

and I believe that's it...
the string offsets arn't modified >_>

you can look at my MDL0 resource thread for detailed info on the format ;)
(including v11 header info)

[ForOhFor Error]

Hmm.

Anyway, update! New program in progress!

Collisions to shadow system:
Adding the shadow system to a stage is time-consuming and annoying. I'm making a program to streamline the process, by making the shadow system follow collisions.
-----------------------
I've gotten it parsing all the collision data I'll need!

[DSX8]

Hmm.

Anyway, update! New program in progress!

Collisions to shadow system:
Adding the shadow system to a stage is time-consuming and annoying. I'm making a program to streamline the process, by making the shadow system follow collisions.
-----------------------
I've gotten it parsing all the collision data I'll need!

and how does this work exactly? O.o

[ForOhFor Error]

It will open the collision data, and read all of the points and planes. It takes every plane that is the floor type, and outputs a flat shadow model positioned correctly for that plane.

Anyway, my output for the function which parses the collision data:

Sorry but you are not allowed to view spoiler contents.

The floating point hex isn't converted because I can't find a python method to do that :/

[DSX8]

It will open the collision data, and read all of the points and planes. It takes every plane that is the floor type, and outputs a flat shadow model positioned correctly for that plane.

Anyway, my output for the function which parses the collision data:

Sorry but you are not allowed to view spoiler contents.

The floating point hex isn't converted because I can't find a python method to do that :/

hmm i see... very useful program i say ;D

[ItalianStallion]

Man this thread is so full of win, and so interesting. After lunch, I will read every [censored]ing line.

Collisions to shadow system:
Adding the shadow system to a stage is time-consuming and annoying. I'm making a program to streamline the process, by making the shadow system follow collisions.

*Gives you all my weed*

[SmashClash]

I want your program! ;D

[ForOhFor Error]

Mewtwo2000 is helping me out. I just need to figure out how to edit verticies manually in hex.

Then I can make my program do it XD

The current version is outputting some sort of triangle bull[censored].

[DarkPikachu]

It will open the collision data, and read all of the points and planes. It takes every plane that is the floor type, and outputs a flat shadow model positioned correctly for that plane.

Anyway, my output for the function which parses the collision data:

Sorry but you are not allowed to view spoiler contents.

The floating point hex isn't converted because I can't find a python method to do that :/

hey 404... use the struct module ;)

import _struct as St #_struct is 1 step faster than struct
float32 = chr(0x3F)+chr(0x80)+chr(0x00)+chr(0x00)
print St.unpack('>f',float32)[0]

you can even import the needed functions:

from _struct import unpack as U

use unpack when reading from a file,
and use pack when writing to a file. ;)

check out my cmn.py module for more ;)
(my module for my converter)

[ForOhFor Error]

hey 404... use the struct module ;)

import _struct as St #_struct is 1 step faster than struct
float32 = chr(0x3F)+chr(0x80)+chr(0x00)+chr(0x00)
print St.unpack('>f',float32)[0]

you can even import the needed functions:

from _struct import unpack as U

use unpack when reading from a file,
and use pack when writing to a file. ;)

check out my cmn.py module for more ;)
(my module for my converter)

Actually, I have already ;D
I found a function online :D

[DarkPikachu]

Actually, I have already ;D
I found a function online :D

IMO you should prbly use my code as it's worked alot better than using int(v,16) based codes
(don't give me credit as anyone can write it) :)

I would end up getting invalad conversions or a value='' result when it should be value='....'

so yea...
only use int(v,16) code for small things.
(16 variables to set is a large thing)

[ForOhFor Error]

I'm using int(x,16) only for 2 small things (the number of points, and the number of plains)

also, I've gotten Mewtwo's MShadow tool to say the points are in the correct places... but there are many differences, and they crash BrBx.

[DarkPikachu]

I'm using int(x,16) only for 2 small things (the number of points, and the number of plains)

also, I've gotten Mewtwo's MShadow tool to say the points are in the correct places... but there are many differences, and they crash BrBx.

I'm up early as getting back to sleep seems to be quite a hastle D:

anyways...
those are ok I guess...

oh yea...
the error was with the bone translations on my old melee code.

as soon as I switched to my ru32() function, it worked near perfect :)
(you saw the best result I got)

[DarkPikachu]

BUMP!
hey 404...
how good are you at understanding Python classes??

I need to understand them as I'm creating widgets for the plugin settings.
(reference the widgets and define the logic in your plugin)

the actual result will display on the viewer
(another reason I need to know classes)

[ForOhFor Error]

You can think of them like a list, sort of. They contain variables unique to one instance of the class, and have their own methods associated with each class type. You start with a Class <Name>: statement, then use def __init__(self,<other arguments>) to set any local variables contained within the class. you then use def <method name>(self,<other arguments>): to make a new method, and you use self.<var name> to reference the variables in the classes.

That's about all I know :/