Short:        Smart by Elven 11. 5th place at Symposium/Mekka 97.
Author:       Manta/Elven 11 <aspano@dsi.unive.it>
Uploader:     Manta/Elven 11 <aspano dsi unive it>
Type:         demo/aga
Architecture: m68k-amigaos



MISC:

Elven 11 present Smart. 5th place at Symposium/Mekka party 97.
Release date: 31st March 1997.
No assign needed. Put Smart.exe and Smart.data files in the same directory.


CREDITS:

Main design:		Manta
Additional design:	Mat/Vajrayana - Slat - Parsec
Main Graphics:		Mat/Vajrayana - Rio
Additional graphics:	Manta - Slat - Vision-X/Degeneration
Main Coding:		Manta - Slat
Additional Coding:	Dip
Soundtrack & SFX:	Parsec


FEATURES:

- VLS1.0 OS-friendly Violent Loading System.
- Motionblurred starfield.
- Masked bumpmapping.
- ColorBumpmapped tunnel.
- Glassmapped tunnel.
- 2x1 24-bit truecolor motionblurring crossfade.
- 2x2 24-bit truecolor blurred plasmarotator while crossfading.
- Oldstyled copper faked effect
- 1x1 18-bit truecolor: bumpmapping.
- Glass-breaking envmapping.
- Wideangle colormatrix-transparency distortion.
- Unlimited ColorBumped tunnel.
- Deinterlaced scrolltext ;)
Plus...hardware transparent sprites...;)


SYSTEM REQUIREMENTS:

You'll need to run it after a clean boot if you have only 4MB of Fast, else
run it from everywhere you like, assuming you've at least 1.4 MB of free
decently unfragmented Chip RAM, and a 2.2MB-wide free contiguous Fast chunk.
It requires at least an A4000/030 25 MHz to work synchronized, but a CPU card
without the A4000 bus bug is reccomended, since most code makes lot of memory
accesses (if you have an A4000/040 25 MHz keep datacache copyback on): looks
better on a Blizzard 020/28 MHz than on an A4000/040 (a factory that
doesn't think about caches burst is worth failing)...
It works on every 020+ CPU, anyway.
Maybe, there will be some bugs on old CyberStormMKII 060 cards...nobody knows
why, so fix it by yourself...:)


SUGGESTIONS:

If you use Executive rescheduler, remeber to keep HD processes at a high
priority (renice them till they reach a priority of +10), otherwise you'll
desynchronize the demo on loadings.
If you try to put Smart code or data hunks in virtual memory (using VMM or
similar programs), it probably won't work because only loading and decrunching
is done in a multitasking enviroment, while the FX are OS-fucking. Turn VMM off
or tell it not to page Smart memory hunks in the prefs program.
Remember to turn Enforcer (or similar debugging tools) off before running
Smart, otherwise you'll get some read hits in bumpmapping routines: nothing
system-crashing, but it will slow down execution due to MMU exceptions.
MCP may cause troubles if the Stonecracker crunchpatch is set, since Smart
datafile is made up of executables and STC-crunched files: turn that patch off.


HOW TO CONTACT US:

For congratulations or 060 boards:

Manta:		aspano@dsi.unive.it		(coder)
Slat:		slat@dei.unipd.it		(coder)
Mat^Vrn:	mat-vrn@freenet.hut.fi		(graphician)
Rio:		rio@freenet.hut.fi		(graphician)
Parsec:		parsec@linux.infosquare.it	(musician)
Dip:		mdipieri@dsi.unive.it		(coder)

Surely answer to everybody...