Oh, and one more thing... The deadline would be good if we had the whole summer, like Kihaji said...

And I think Matrix made quite a good point...

quote:

---

Original post by llvllatrix

But what about us art challanged? If I can only use art I create I hope ol mr stickman is good enough, because thats about the extent of my art skills.

---

could submit code?

Wouldn''t the whole demo be considered original code then? I could probably come up with something to use if I can''t use copyrighted material, like a terrain or building demo….

Going to try to recap a few things:

So the average post say anywhere from 5 - 10 megs is a good limit. So is 7.5 megs too big or a nice average? I''m thinking 7.5 megs for the demo itself in zip format... code shouldn''t be much larger and of course the source/demo will be split when the entries are put online.

Basecode... You all know my opinion... I really don''t care as long as source is included with the demo and it compiles without the need to download additional libraries (nothing worse than hunting for a custom library just to make something work).

The date I was thinking was the end of August... seems most of you are saying September so how about Sept 1st?

Copyrighted material... I really don''t know what to say right now. I would recommend that any images you use, you get permission from the author of the image. For things such as textures, and random graphics, as long as you are not using tiles ripped from a commercial game, or someone else''s game (ex. they are misc graphics you could find on just about any web site), I don''t see a problem. One thing I do not want to see is models or levels ripped from a commercial game. Might look nice, but everyone immediately notices, and no matter how good your demo is, it probably wont win.

As for overused effects... there were a few really good posts on the topic. You might see a ring in the first demo you watch and go "wow, that''s really nice"... but then you watch the second demo and see... "A ring"... then you watch a few more (no rings), but along comes a third... and god... you just want it to end Basically what I am saying is use an effect if you think it helps the demo, but try to get in the mind of your competitors... think hard about the effects you plan to use and think to yourself... "if I''m thinking of doing this... I wonder how many others are as well". If the effect comes to you the minute you sit down, it''s probably come to others as well

The theme of course MUST be two towers... either the book or the movie (although most people will relate to the movie more)... got to love mass media.

The program MUST render with OpenGL (this should be a given).

Full / ready to compile code MUST be included (the point of the contests is to make new code available to the site visitors). This means YOUR code can not be hidden or precompiled into a library.

Disclaimers must be included of course. This site is not responsible for user submitted content, so protect yourself.

If you submit no win32 code, I will more than likely NOT convert it to win32 for you... keep this in mind when you''re wondering about the size of your audience.

Demo must run 100% without interaction (aside from a setup screen or welcome screen). You can add an interactive mode if you wish, but the default should be a standalone demo (running from start to end with no keyboard interaction required). Demos must also provide a method to exit the demo aside from CTRL-ALT-DEL

Anything I missed? Should I solidify the rules above?

Solidfy them Nehe. Look pretty good.

There should be a readme.txt or similiar that specifies how to build the code also.

Looks good, only thing I see missing are the judging criteria.

I get to choose the winner

All the rules mentioned looks good. The file size as well as the deadline looks good too IMO.

Perhaps something should be said about fullscreen mode ? I''m not sure though.

The demo should probably run at least on PIII 600MHz with TNT2. For people interested with fancy OpenGL extensions, keep in mind that the demo must run on any OpenGL-compatible card. For each scene that uses an extension, if the extension is not supported then the scene may either be cut or the quality may be decreased, but it must not crash. Additionaly you can mandate a "minimum requirement" (for instance : the demo will not start if multitexturing is not supported) but by doing so you can reduce your audience, more or less significantly depending on what you set as minimum.

I agree about the readme.txt file. Entries should also contain en entry form, be it in the readme file or not.

Source code, Data and Executable should be in separate folders. I think it''s better if Data is a subdirectory of the Executable directory.

Looks like most people agree on the rules, and so do I.

Oh, and NeHe_Lover, what was your favorite scene in the movie ...

heheheehe .... and the bribbing starts at

Well, Evil, it was worth a shot! Hehe...