.theprodukkt ...will make you happy
home · .theprodukkt · faq · making of · mobile · contact
.debris · .werkkzeug 3 TE · .kkrieger · .werkkzeug1 · demoscene

downloads

pno0002_werkkzeug1_v1200.zip (629kb) the .werkkzeug itself
pno0003_the.popular.demo_datafile.zip (7918 kb) the .werkkzeug file for fr-025: the.popular.demo

these files are hosted by scene.org



about .werkkzeug

ever wanted to create your own demo or intro, just as farbrausch's the.popular.demo or candytron? this is your chance to get your hands on the technology behind these productions.

this release is equipped with everything needed to produce high quality realtime demos:
  • extremely fast and powerful 3d engine
  • advanced texture and mesh generator
  • wysiwyg in all areas
  • image post processing (ipp), render2texture effects
  • timeline to arrange animations and scenes
  • full realtime playback within the editor
  • simple spline editor
  • complex particle systems
  • optional pixel shader 1.3 support (bumpmapping, anisotropic lighting)
  • jpg import
  • dotXSI import
  • lwo import
  • export as windows executables, as small as 64kbytes
  • export as .kk1 (for use with the .kkino-player)


links and community

as more and more people are using the .werkkzeug1, some users start their own websites and forums. you can go there and share your experience.

as a special event, we will be giving a seminar at the assembly 2004 seminars in helsinki, there you can meet us, see us explaining our tools, and ask questions.

  • vectronix.org forum: an open forum for all kinds of questions
  • workthings wiki: a growing collection of tricks and facts
  • erbsen: a german translation of the .werkkzeug1 tutorial
  • assembly 2004 seminars: see us explaining the .werkkzeug1, and ask questions face to face.
    the assembly 2004 will be held 5th to 8th august 2004 in helsinki.


screenshots

compose textures, meshes, scenes and whole demos out of simple operators
import jpg's, softimage|xsi and lightwave scenes where procedural approaches seem difficult
animate your scenes and compose the demo.

(click thumbnails to see full-size version)



frequently asked questions

we will report workarounds and missing documentation here until we have the time to fix the problems in the code and update the tutorial. so we hope this faq will shrink again.

please read the tutorial. it's long, but there's no way explaining such a complex and different software in a few words. it also pays to look in all the menus.


Q: what features can I expect with the next update?

A: you should expect a small service release this year. it will contain:

  • export of textures in some simple format like .bmp or .tga
  • the ":cubemap" crash and some other bugs will be fixed
what we're not going to do in the foreseeable future
  • support for loading 3dmax scene (it's too much work)
  • documentation for .k1 and .kk1 data files (they are too complex)
  • any form of localisation. (maybe "better" english is possible)
  • ports to other operating systems (it's too much work)
  • releasing .werkkzeug3 (this is our priority, but it's a long way)
  • releasing sourcecodes / open source (our small team is trouble enough)

Q: how do i navigate in the 3d-window?

A: try pressing 'o', 'p' or 't' while dragging with the mouse. 'wasd' fps-like controls are also available. there is no way to change the keyboard layout.


Q: how do i import files?

A: it's best to have the werkkzeug1, your .k1 file and all files you import in the same directory. then you should use relative paths (without c:/) to refer to the file, because paths are limited to 31 characters. yes, the file requester is very bad :-)


Q: my demo crashes with ".\playermain.cpp(325) : assertion"

You need to have music in your demo, at least a metronome.


Q: my demo crashes with ".\doc.ccp(3473) : assertion"

this is a bug we have no workaround for. it happens when an operator has a very long list of parameters, and one of the lower parameters is animated. for instance, everything below (and including) "Rot Speed" in the particle operator. to make things more confusing, the order of operators displayed is not always the internal order :-(


Q: how can i display a picture in a demo?

You should know that you can't simply connect a texture to a demo operator. If you want a 2d-layer, you will need a material operator (green), a layer2d operator (yellow) and a camera (gray), and connect everything correctly. This allows you to position the layer and animate it's color, and to select a correct blending mode. You should use the same camera for 3d and 2d layers, but if you want to have two independent 3d scenes, you need a second camera with "Clear Mode" set to "Z" or "Off".




Copyright © 2004 .theprodukkt - all rights reserved. disclaimer