pouët.net

... and i'd like to add the following things as mandatory for an engine:
- resolution selection (320 to 1280 is nice)
- windowed mode (preferably with optional always on top)
- datafile instead of cramming the stuff in a directory
- a loading bar. demos/intros not having loadingbars should be reconsidered to be shown by the prejury.
- possibility to quit the demo at _any part_. yes this DOES include the precalc.

Gargaj: why is a loading bar so important? isnt it good enough to have a text saying "wait bitch, still loading" ? :)

a loading bar.
even if it has no other role than keep the user waiting for 100 * rnd(2000) millisecs, as the demo could start immediately?

i don't think a loading bar is that important, as in it being a bar showing progress... but I agree something should move on the screen, even if it's only to indicate the fact that something has not crashed :-)

i would like to add the following things as mandatory for an engine:
- staples
- carburetor
- oil

Better make intro/demo engines that doesnt take hours to load instead of making a loadingbar. Its not like its hard to cut down loading time in intros nor demos.

yeh, stop generating!

how about this, lator?
PLASMATEXTURES STORED AS RAW DATA?!
it would load really fast AND look like shit!

yay flatshaded cubes forever!

kusma: YEAH WITH L33T WAVELET COMPREXXION!!1

jcl: my point exactly, even tho i like to see if whether i have the time to eat a dinner while the stuff is loading :)

Yeah, indeedy. I sense a lot of BAD BAD BAD BAD coding these days, really BAD. Worse than I did in the years before :)

gargaj: it's been a very long time since I don't trust loading bar speeds... like, it might take 10 minutes for the first 5% to move, then the other 95% takes 2 seconds... or those progressbars that end up at 35% or something and make you feel something is wrong =)

And yes, I agree demo loading times should be cut, it's a demo, and 10Mb demos are ok, so go ahead and store everything :-)