pouët.net

Wow, he seems proud of doing something we all knew were possible but chose not to do because the demoscene features a certain amount of respect for others people work. But hey, it's probably worth creating a fake user and brag about it, right?

you got me wrong. this wasn't meant to be seen about "bragging and decoding it". I'm not stupid. I rather thought about an example to see how the "tricky things" been done in there. this's cause of the non existent documentation of the tool. so...

and I sure have big respect of the farbrausch peoples doing.

gloom: From what I can see, the Farbrausch guys don't particularly feel that their wishes are being disrespected here...

whats the point in "hacking" a demotool ?

why not write your own ? instead of spending time dissasembling this one ?..

each big group made his own demotool..

The point? Playing with other people's tools (in a non-sexual way) is great fun and you can learn a lot, whether you're making your own tools or not. I regularly download new demo tools and have a quick look at them at least. I'll take a look at wz3 some time too.

Then again, I wouldn't go to the trouble of reverse engineering any of them ;)

sure right. hacking the tool to perfection doesn't work and isn't worth it. also takes way too much time. that's what I alwaysy knew too. WZ3 has some simple issues to be fully functional, that could be easily fixed by a experienced coder/haxorer (which is not me)... but it's easier to 'recode' it.

So far... this just playing with it, learning and doing something else.

release werkkzeug v4, will ya.. might be slightly more interesting if at all interesting.

Wery well, I shall welease Werkkzeug!

I spent only two hours disassembling WZ3 to extend its functionality.

Are you werkkzeug hacker too?

Sanity- Demo or Die!

"I spent only two hours disassembling WZ3 to extend its functionality."
ahem. you didn't extend any functionality, just unlocked the functionality that's already there. :)

Sauron, go play with rsi demo maker will ya.. ;)

ryg: he did say he was going to announce something big with it, so I'm hoping for some nifty extended functionality still. If, on the other hand, this is it.. um, yeah. Oh well. :)

lol @ryg. sure right. but question:

if I manage to get full or funtionality even new things done, will I get sued when I release the modification? I mean, using it and a releasing a non-FR WZ3 demo sure will get me only tons of thumbs down on pouet cause of the general opinion of werkkzeuged demos and that's it... but if I do something else ??...

Anyway... I didn't feel like managing it yet, but just in case...

Amiga? No...

werkkzeug 3 configuration file format released!

http://werkkzeug.wallst.ru/index.php?q=wz3format/config.page

heh, here's ANY fileformat released. This includes werkkzeug 3, 4, and future versions.



There!

the "MDIMode" is actually "showTitlebar" for the fullscreen window. but I'm sure you know that. ;)

Just to mention. I finally love that tool. Not that it murdered my system only like the 1.2 version did - which is easier to fix. No. That bugshit triggered a kernel fault to get rid of all my partitions the time it exploded. Really nice. I think save code is somewhat else. Boooo. Not that "users" haven't been warned !?! But that shit is a grave for my code. Thx alot. -.-

Well thank Windows and your graphics drivers - there's nothing in the whole wz (1,3 or 4) codebase that could even remotely be responsible for a fuckup like this.

Of course, bugs that send garbage data to DirectX are entirely possible (even though we normally run everything against the debug runtime now and then), and with a shitload of bad karma (eg. GPU DMA going rogue while it was the HD controller's turn) those can lead to system or even FS corruption. But that's entirely to blame on WDM, and there's no single line of code we've written that would even attempt to go that deep. In the end it's a demotool: load (or generate) some stuff, do lots of calculations with it, and then send it off to Direct3D and DirectSound. No black magic involved. And no, ASM is just another programming language.

So please refrain from any "werkkzeug will trash your system" FUD, thank you very much. The same can always happen with any other demotool, demo, game, 3D or pro audio tool or any other kind of "multimedia" software that tries to squeeze some performance out of the computer.

Unless of course you get your executables from $RANDOM_GUY_FROM_THE_INTERNET. In that case every can, and will, happen.

Stay cool KB. I've already recovered most of the basic stuff. and...

This was just a random rant about what happened. I don't care what you think the bug came from or how you really did code carefully. So...

and I just thought... I'll have to rewrite most of the code to a better anyway. So... this half bad.

I feel motivated to do something more. ;)

*Should I use more childish txt smilies to show that I'm not really serious about something?*

No, it wasn't:



That's not a description of what happened. That's pointing fingers. What happened is that your computer experienced a fatal crash while wz was running. That's all you could report: Your PC, possibly running with the GPU and mobo maxed out for hours (which doesn't happen too often if you're not a pro gamer), died on you. You know, I had a computer die on me while running the demo that was used for the big screen during the scene.org awards show. Live at Breakpoint, on the fucking big screen. I could have logged onto pouet and ranted about how scene.org (or random demogroup that did that thing that year) destroyed my PC and my life, but guess what? All I did was install the stuff on another computer and run it AGAIN. Because the thought that it could be the software's fault did not cross my mind even once.

In the last 10 years as professional game developer I had lots of code written by me bounced back by our QA department because it worked like shit. So has every other programmer in my company (and probably every programmer in the industry). Now guess how often one of these bugs resulted in someone having to reinstall his computer: NEVER. Because if you're writing simple user mode software its really, REALLY hard to destroy anything if you don't attempt it very deliberately. Actually I really would need to dig deeply into MSDN now to find out how the hell I'd be supposed to delete the partition table at all.

And just believe me: Most demotool coders don't ever implement that "randomly kill Windows" feature because it's just such a bitch to debug. :)

kb: Dude, Quisten intentially destroyed your computer.

Way to undermine my argument there. What do you people still want from me? BLOOD? :(

another track even more epic than the fr-08 one and BLOOD. :D