Messages

I dont't see where talent is needed for to do those things you've described above. The fileformats are all well documented and if they weren't it would just take some hacking to explore them. Afaik in stuntsfiles is nothing encrypted or encoded to complicate reverse-engineering like it was done in Master of Orion 2 for example - I needed nearly a week to completely crack their graphic-libs.

The bot that drives stunts instead of a human being would be surely an interesting project but I'm very short on time these days - so I think I'll have to wait til summer-vacation with that...

i dont know about you happy worm, who are you?

joined ZakStunts-Competition a few days ago and startet digging through old threads here to get a picture of the community here...

i tried to decompile the sources until it gave asm.

in my terms "decompile" means that you reverse the binary back into the plain source-code it was written in - MS-C in this case. Just make asm of it i used to call "disassemble"

its not going anywhere because its compressed.

I've just sent any game-executeable through a disasm and it worked without warnings. iirc - it used to complain if code was packed. So either it just missed something or the files are not packed. Could you name the file(s) from which you assume it is packed?

CTG and his stupid replay coding program idea.  

what is stupid about that? I would have used an other approach where I don't need the sources but I think in general it should be possible

since when you are watching a replay, Stunts regenerates the whole physic happenings, collisions, acceleration, jumps, etc, everything, it's impossible to do a separate RPL viewer/editor without the sources of the original stunts physic engine.

if we'd have the sources it'd be not that hard to code an optimized replay searcher/writer, so let's celebrate we dont have the sources.

well you have at least the possibility to write a wrapper that hooks into the replay-engine  when stunts is loaded to memory and directly passes commands at the engine and fetches the result. of course this would be not very nice but I think it'll work.
second thing would be to reverse-engineer the whole program, first use a decompiler (if I remember correctly stunts was written in Microsoft C 5) and then translate the remaining asm-code per hand - time-consuming but a chance to get the code