some good stuff here. Individual comments :

pushcoag : very nice. Decent architecture and texturing and nifty lighting. The gameplay's pretty sweet and it's an original idea done well. Probably the best of the pack. Major gripe is stuttering framerate.

tyrcoag - I really wanted to like this but the tightness in some areas and the ease with which one can fall into the void brought it undone for me. The brushwork and texturing are fantastic, without much of a hit on the framerate. Lighting is excellent, very old skool in parts but excellent in general. The dark, moody lighting did make it a bitch to spot scrags though, since they disappear in the black background sky anyway. The tightness, as mentioned before, made the gameplay frustrating parts IMHO but maybe I'm just not good enough.

discoag2 - too easy. That's basically the only fault of the level. Texturing is fantastic, far from the chaotic look of distrans' first and only prior level. Lighting and architecture are decent enough too. Some decent gameplay ideas here but since you couldnt fall into the void that easily, maybe more enemies would have made the gameplay more challenging.

jesus - I didnt like this at all. Crude texturing and average lighting with some rather basic architecture. Framerates were low throughout and the gameplay didnt seem planned out at all.

nesp10 - Like his previous coagula map, this just doesnt work for me. The architecture has some inspired work with numerous angled, detailed wall and roofwork. But overall, the brushwork feels too chaotic and randomly put together. I thought the gameplay was too difficult given the tight layout and low framerates.

chain3 - I liked this probably second best along with tyrann's and distrans' levels. Gameplay is challenging but not unfair and I like the architecture and texturing. The lighting could have done with a lot more contrast. 

UWF: If you haven't fixed the download link, do so by removing "planetquake/" from it.

Second, in Win- and Tyr-Quake, Pushplay's map crashes with "Bad surface extents." Any idea what's causing this? 

Yes, the five other maps are all good. I really liked "The Vertical Mile" - good, original stuff.

Fatty: not sure - missing a texture maybe? 

what awesome maps!
they're all really great! what fun! whee!!! :)

i'm a little pissed off though, since the original stipulations were that the map was supposed to be good in both sp and dm. and i actually bothered doing dm mode, testing, adding extra shit, etc... don't get me wrong, i'm not pissed off because i didn't win, i'm pissed off because i made an effort where none was necessary. ;) 

read the original post... the 'Rules!?' section ;) 

it was changed i tell you!!!

:D

i think i'm just stupid. ;) 

i think i'm just stupid.

That's okay; we think you're just stupid too :) 

High quality stuff here. I liked ChAiNeR's, Distrans' and Pushplay's maps best as I prefer brighter maps with more space to move when fighting. All maps were great fun though.

ChAiNeR's had too much ammo/health (at least in Normal skill) but as a player you always have a choice of not using ammo/health or heavier weapons.

I had some problems with Distrans' map as I couldn't find a way to get pass the wooden bars at the top without trick jumping from the tower. Also, the last red button couldn't be pressed or shot, so I wonder what's the deal with that? Exiting could be done without any of these maneouvers, though. What gives?

Pushplay's was very original, as mentioned above almost a Q3A feeling (or possibly SiN for the textures). Very nice. It's however not playable in Win/TyrQuake which actually was one of the requirements of the contest.

The error message "Bad surface extents" usually means that there's a missing sky/liquid texture, but FitzQuake didn't have any problems with it, strange.

I tried to rebuild the map and then it was loadable in TyrQuake so I don't know what's up, maybe a sky/liquid texture with unusual proportions? I'd suggest Pushplay might try other build tools to see if there's any difference.

Both necros' and Tyrann's maps were very dark and pretty cramped at places which made combat overly difficult IMHO. Especially in necros' map there was a severe ammo shortage at times and the Deathknights/trigger_push area was awful.

However, both maps were certainly a challenge and looked very good. Tyrann's map had several great secrets.

All in all, a great effort and well worth waiting for. 

Could you toss me a copy of your rebuilt PUSHCOAG? I'd like to have a squiz at it. I opened the damn thing in Quark and it didn't puke at all. 

My quickly rebuilt version is not cleaned up at all, I don't know if there are gameplay issues with it. However, it does load in both Tyr/FitzQuake, has no leaks and is fastvised/lighted.

In any case, wouldn't it be better if Pushplay had a chance in fixing it up using the real source map? In any case I need his permission before distributing my rebuilt version. And I rather rebuild it using the real source map if he's willing to share it. For a fast rebuild, it's only a couple of minutes.

Pushplay, what do you think? I noticed in the map that you've used the sky texture also for the large trigger_hurts, I don't know if that could cause the error message in WinQuake. It's easy to fix anyway. 

that's what i get for not beta testing at all, eh? :D

sorry about the trigger pushes everyone!

btw, does anyone know why in some places the trigger_hurt i put along the ground doesn't actually hurt the player?
i had to split the one massive trigger_hurt into tons of smaller ones, but even then some of them don't hurt the player... (try falling down between the blue wall before the exit and the silverkey island) 

Yes, I had that problem with my map too. I just played around with the triggers till it worked. I'd like to find out what the bug is though... 

I'd like to be able to say these maps were worth the wait...

...so I will. These maps were worth the wait.

Top work from everyone.

Chainer : Wow. Your mapping is really improving. I can't wait to see your next effort.

Necros : Real hard, dirty fighting, just what I'd expect from you. :-) But (to repeat everyone else) why oh why oh why oh why the push_trigger bit??

Distrans : Loved the skill 0 = no monsters touch. Beautiful architecture too.

Tyrann : I still haven't exited yet. :-/

Jesus : wept.

Pushplay : I'd love to see this map. I hope it can be recompiled for regular Quake.

Thanks to UWF for organising this little shindig.

If anyone's interested the first speedruns of these maps are already in at SDA... 

I've investigated some more and I'm fairly certain now that this is basically a missing texture problem that Pushplay might have missed in the compiler log.

There are two bad miptex entries in the bsp file that are likely to be the cause of this error. This in turn might be caused by an older compiler not handling texture names correctly.

This is also why my rebuilt map works; my rebuild process automatically fixes missing textures thus eliminating this problem.

Pushplay, a simple rebuild of the original source map with better tools might do the trick. Otherwise I can take a look at the zipped map if you send it over. 

The map was built in GTKRadiant and a wad file that I pieced together myself. I may have broken some unwritten rule in how I named files in the wad, because I'm quite certain no textures are really missing.

I couldn't test with software quake because it simply refuses to run on my system. No one who beta tested had any problems with the map, but I didn't ask which flavour they use. So if you recommend what the better compilation tools are, I'll give it a go.

As for the triger hurt, I noticed that if you jumped into the hurt and died, it may not remember to hurt you next game. My guess is it's a bug in the code where the timer betweem hurts fails to reset. I got around it by simply stacking two trigger hurts on top of one another. 

Take a look at http://user.tninet.se/~xir870k and since you're using GtkRadiant, you might want to check out http://industri.sourceforge.net/howto.php?pg=9 as well.

Let me know if you need more info or want me to fix it up (just send me the zipped map). There are apparently a number of people that are eager to try your map out in Win/TyrQuake. Let's not shut them out. 

It just occurred to me; you haven't used texture names longer than 15 characters, have you? Some of the texture names that I found in the bsp are pretty long and some ends in a '_' character, which is unusual.

Older compilers don't check for that and if you exceed this length, there might be unexpected behaviour and data corruption.

Specifically, there could be texture name mismatches that might produce these exact symptoms.

Using the tools above will tell you if the names are too long. 

15 characters, eh? That's exactly the kind of until-now unwritten rule I was talking about. A few of them are 16 or 17 chars. It's not my fault, Wally let me do it!

Fixing the texture names is easy, I can have that done by the morning, but doing a proper vising on this map takes nigh on forever. Does anyone have a super computer they can lend me? 

So it turns out that I can't count at 4 in the morning. The longest texture name is exactly 15 sans extension. The texture with the underscore is e8clangfloor04_ which I used extensively.

However, my wad didn't have the trigger or clip texture. I passed them off as only being necessary for the editor, and edited using common/trigger. Do you think that would cause the problem? 

that you rebuild it the same way as before, i.e. only fastvised. A fullvis on this map will be pretty painful; you're most likely looking at several days of processing even on a powerful machine.

Although the Win/TyrQuake guys will most certainly feel the r_speeds hit even more ... 

I'm not sure but I'd definitely make sure that all textures are included in the wad before doing anything else. Also check compiler log for missing texture entries.

Since I think that the bad bsp miptex entries I found before in fact are from the trigger_hurts, it makes sense that this is the problem. 

and edited using common/trigger

That's the trigger texture for Quake 3, not Quake 1. AFAIK you must have the trigger texture contained in your .wad - it really isn't related to the way Quake 3 handles it. Definately sounds like a likely culprit because even though the texture is missing, no-one can see the error because triggers are invisible. 

15 characters, eh? That's exactly the kind of until-now unwritten rule I was talking about.

http://www.celephais.net/stuff/texturefaq.htm

Also, you should have trigger in your wad. I don't know offhand if you need clip. 

metl: damn, I knew it all except that one.

It doesn't matter if I map with common/trigger or the new trigger extracted from my wad because the map converter strips out path names. The common version is just a lot more attractive.

I'm recompiling and fast vising with the new wad. The compile is already done. The warning count is 0 and the brush count is 2249. 

If you push them 1,2,3,4... there shouldn't be a problem.