AEon wrote:
Tried to download the map twice... size 2774413 bytes, the pk3 file is corrupt and will not load.
Are you sure you tried it in Quakelive and not Quake 3 ? I've tried to download it and play, it seems to work. I just want to be sure before I re-compile/re-encode/re-upload.Kaz wrote:
I really like what you've done with the stairs and some of the way things are layered... reminds me of UT99 pretty strongly. Might be able to DL later...
Thanks. The map is indeed inspired from dm-peak, aka the most irritating map in UT99. Aside from that, the gameplay is completely different, well I'd better hope it is 
Eraser wrote:
Wow, this is your first Q3 map? Do you have any experience doing level design for other games? As a first map (even with prior level design experience), this is truly exceptional.
Thanks. Yes I mapped until around 2005 for HL/HL2 with Hammer. I haven't done anything else since then, I had a nasty computer crash. In fact, this map is a remake of an unshown map I made in 2005, luckily I found it stored in an old gmail address shortly after I began gaming again. Fortunately, the textures set in QL is much more pleasant to work with.Eraser wrote:
You can create a brush and apply the "playerclip" shader found under "common" to create invisible brushes that block player movement. You can recreate the non-solid bits with brushes textured with the playerclip shader to make them appear solid again. Additionally, to block weapon fire, use the "weapclip" shader in the same way to block weapon shots and projectiles.
Also, it's always a good idea to run through your map sliding along walls. If there's any uneven vertical trims that stick out as much as a single unit players tend to get stuck behind them. It's a good idea to use playerclip to smooth out wall surfaces so that movement-wise, the walls appear smooth. It may sound odd, but it's best for gameplay and feels more natural than getting stuck behind small trims all the time. In some of the id Software example maps, you can see they're often clipping off walls with as much as 16 or even 24 units. Sometimes you can also create a triangular brush with one surface at an angle with the wall so players kind of glide along the clipbrush away from the wall if they run along a wall and might get stuck behind some detail brushwork.
Thanks for the tip. I didn't know about the weapclip, I just found it in the texture browser thanks to you. The weird thing is that the transparent blocks around RA seem to block -vis because when I toggle r_showtris 1, I see no polygon behind it. I've deleted those blocks and replaced them with new ones but the error persists. Besides the obvious bugs I mentionned, playerclips are already setup for most parts, for walls at least although I might have missed some spots. I will probably use them for ceilings too since players getting bounced around with a RL might easily get stuck there.
Also, it's always a good idea to run through your map sliding along walls. If there's any uneven vertical trims that stick out as much as a single unit players tend to get stuck behind them. It's a good idea to use playerclip to smooth out wall surfaces so that movement-wise, the walls appear smooth. It may sound odd, but it's best for gameplay and feels more natural than getting stuck behind small trims all the time. In some of the id Software example maps, you can see they're often clipping off walls with as much as 16 or even 24 units. Sometimes you can also create a triangular brush with one surface at an angle with the wall so players kind of glide along the clipbrush away from the wall if they run along a wall and might get stuck behind some detail brushwork.