Chimera
Your best friend
Chaos Knux said:Hyper Shadic X said:If not already done, I think that you should set a thing in the MD2 model code where a player's model is specified by it's skin. For example:
Code:PLAY PLAY.MD2 3.0 0.0
That's the default, right? How about...
Code:PLAY KNUX.MD2 3.0 0.0 KNUCKLES PLAY TAIL.MD2 3.0 0.0 TAILS
See what went on there? why don't you set it where a "PLAY" sprite set only loads a player model for a certain character (in this case KNUX.MD2 for Knuckles) if the skin of a character is specified at the end of the code line? That would work out for people who want the dynamic trio in 3D without screwing up. Also, putting "SONIC" at the end of the first code line I specified would only load the sonic model (PLAY.MD2) if the skin was SONIC, whereas added character WADS won't mistakenly have Sonic's model overlay their sprite set?
Ideas ideas. :P
And if I may add, I think it would be cool (however really annoying to program) if there could be something like this:
Code:PLAY PLAY.DAT 3.0 0.0
and in PLAY.DAT...
Code:PLAYA STAND.MD2 1.0 0 PLAYB--PLAYC BORD.MD2 0.5 0 PLAYD--PLAYK WALK.MD2 1.0 3 PLAYL--PLAYO SPIN.MD2 1.0 0 ...
Let me explain what this would do. For the player model, in MD2.DAT, one would specify the game to read PLAY.DAT. Why? PLAY.DAT specifies what goes on with the character's frames. For the PLAYA (standing) frame, PLAYA.MD2 would be drawn. This way, the model could actually seem to have life, such as moving up and down, breathing, etc. For the PLAYB and PLAYC frames, those are overlayed with the boredom model. For the walking frames, those are overlapped with the walk model, etc. The "--" specifies which group of frames is replaced with a model, like the walking frames. For this, the model would continuously loop.
Now I should specify the numbers. The first set represents the speed the model is looping. 1.0 means it loops the same amount of speed the walking frames loop when one starts to walk (was it 15 tics?). 0.0 means each frame loops the same amount of time each sprite frame loops. This could be good for further customization in how a character walks.
The second number in a code line represents which frame the model starts looping. Useful if a character pushes off the ground before he/she starts walking/running.
This meethod could probably also work for other random models to make them look more accurate (like the digger enemies in 1.1's (not so) Arid Canyon Zone-- making them slowly fall froward before they dig back into the ground).
I end my wall of request here. :3 (and yes I know that the second method would require multiple models. :U)
That would be awesome, if you don't by Monday I'll quote it in.
Well, posted it CK. :P
Also, about the second MD2 idea, why not also allow putting in state names, that way a character can have flexibility in super sprites and such.