Невероятно, сногсшибательно, уму непостижимо, но факт остается фактом. .kkrieger - настоящий, полноценный шутер от первого лица весом 96 килобайт.

И это не какой-нибудь клон Wolfenstein 3D. Талантливые энтузиасты из коллектива .theprodukkt сотворили современный шутер с поддержкой DirectX 9, пиксельных шейдеров, единого динамического освещения, бамп-мэппинга и еще целой кучи "пальцатых" технологий. Толпы монстров, пять видов оружия и девять уровней уместились в размер скриншота из какого-нибудь Doom 3. Невозможно поверить, если не увидеть своими глазами.

Впрочем, получится это не у всех. Несмотря на свой крохотный объем, бета-версия игры требует наличие мощного процессора, 512 Мб памяти и видеокарты с поддержкой пиксельных шейдеров версии 1.3 (всякие GeForce4 MX и младшие модели Radeon отпадают). Еще раз взгляните на скриншоты, скачайте, выпейте чайник холодной воды и приготовьтесь к необычному путешествию в мир цифровых сверхтехнологий...

.kkrieger requires a relatively high-end machine to run properly. To be
precise:

- A 1.5GHz Pentium3/Athlon or faster.
- 512MB of RAM (or more)
- A Geforce4Ti (or higher) or ATI Radeon8500 (or higher) graphics card
supporting pixel shaders 1.3, preferably with 128MB or more of VRAM.
- Some kind of sound hardware
- DirectX 9.0b

Они что на объеме экономят?

1. about .kkrieger
------------------

The project was started two years ago and since then many, many hours of our spare time went
into developing .kkrieger. Still, in the end we didnґt have time for the most important thing:
gameplay. So expect some major improvements in our next releases.
However, we enjoyed making .kkrieger a lot and are quite satisfied with the end result and now we
are eagerly awaiting your comments So if you have any feedback, may it be acclaim, critique or
bug reports - please feel free to write us. Every email is highly appreciated!
(No, wait - donґt send us bugs until the final version - we know enough already

We will definitely release an uncut "final" version with some more kb, enhanced content and less
bugs, soon. (The first thing we'll do after this release is relax for some time, though .

.kkrieger is designed as a trilogy. At the moment we can not tell if and when we will find the
time to develop the next chapters, though. We will keep you informed on our homepage...

In general, if you have any technical questions concerning .kkrieger, either refer to our
web site or contact us via email. However past experience shows that there are some rumours
and misunderstandings about our work that are very hard to correct, so we'll state the truth
here, in written form, for all the world to see

- We do .not. have some kind of magical data compression machine that is able to squeeze
hundreds of megabytes of mesh/texture and sound data into 96k. We merely store the
individual steps employed by the artists to produce their textures and meshes, in a very
compact way. This allows us to get .much. higher data density than is achievable with
normal data compression techniques, at some expense in artistic freedom and loading times.
- .kkrieger is not written in 100% assembler/machine language. Not even nearly. Like the
vast majority of game projects being developed today, .kkrieger was mostly written in
C++, with some tiny bits of assembler where it is actually advantageous (notably, there
are a lot of MMX optimisations in the texture generator).
- A kilobyte is, historically, defined to be 1024 (2^10) bytes, not 1000. Thus .kkrieger is
a game in 96k even though it's actually 98304 bytes.
- The concept of the texture/mesh generators was developed by fiver2. We do .not. want to
claim that the techniques we used to develop .kkrieger are new inventions. Itґs rather a
selection of useful operations and their parameters to optimise the results.

We've done some testing to ensure it runs on all hardware meeting those
requirements we could get, and we checked it runs on all major supported
configurations with current drivers, but with some graphics card/driver
combinations it might screw up. In case you have problems, please try
getting the most recent driver release from your vendor, and only if the
problem persists contact us (refer to the contact section).