any wads besides rune.wad that have any? 

You'll have to use texmex to get the burmal quest textures afaik. I'm working on some custom snow textures, based on some hexen 'german medieval' textures. 

i'll have to look over hexen textures i guess, i didn't remember there were any. thanks!

looking at the screen, that looks like the hexen textures right?

don't really tile all that well, do they? :S
will have to experiment. 

looking at the screen
referring to the screenshot of brumal quest (alk15) on quaddicted. 

Daikantana has good snowfiles. I can remember there was a daikantana.wad on quaddicted. 

There are 4 daikatan texture set, one per episode.
You will need DKT3.wad for snowy texture ;) 

forgot alll about dkt! :D 

ogro + snow

it was in a dm map a while back. long while back actually. i can't remember for the life of me who it was by or what it was called though :( 

http://www.quaddicted.com/wads/clockwork.zip 

http://mpqarchive.pauked.com/index.php?view=viewcomments&review_link=16955

great map btw 

looks like that map was made for glquake clients... fullbrights on the snow kind of ruin the look now. :P

still, not too hard to palette swap a few pixels around. thanks :) 

Still need those Ogro textures fixed for fullbrights? 

yes please! do you have them or need sending? 

and I'll give them a try. 

Cause they're everyone's favourite. Hipnotic ones of course.

So I'm trying to trap the player in what is essentially a rectangular room that's rotating on a point at one end, and after a lot of fiddling I've got it down to just having a lot of narrow movewalls. The problem is it works for the longer walls sections, but if they run all the way to the end (furthest from the point of rotation) they easily push the blocks out of the way and fall out. Any thoughts? :E 

hmm okay I've done a bit more investigating, and it seems like the problem is corners. As soon as the player is pressing on two walls on opposite sides they push them apart... guess I'll have to rethink this sequence :E 

in my experience, it's best to stay away from what you're describing because func_movewalls are just not that reliable when implemented that way.

as you've noticed, if two movewalls are pushing the player, the collision can't be resolved properly which allows the player to sort of wiggle through between them.

the best you can do is to make them insta-kill, either with straight up high damage or setting the movewalls to damage on touch rather than block. 

Yeah I'll have to just bin the sequence, or rather, use it later when I can just place it over lava so there is no need for walls anyway. With the area it's set I can't really just kill the player if they touch it :(

Oh well, the section should be fun as it is anyway :E 

There is a way of doing it without movewalls. Never used it myself (yet), but;

http://kneedeepinthedoomed.wordpress.com/page/3/

Scroll down. You'll need to do some legwork and use a custom progs though. RMQ will work, but the gameplay changes maybe aren't what you're after.

What you're describing sounds like the opening bit of The Pit and the Pendulum... 

...so can't really use any different progs.

I'm over it now though, it's just another thing to add to the 'do in a later map' pile, which is getting pretty big now :E 

Just trying out different engines at the moment, and Fitzquake throws up a fair list of exceeded warning messages when loading my current project. Nothing is crashing or glitching, but I'm curious as to what a couple of them are:

marksurfaces
signon buffer 

I'll answer the latter:

The signon buffer is the first real message message that gets sent to the client. It tells the client the initial state of the world, which means it must contain all of the static entities in the world. It also contains a list of all the visible entities that exist once worldspawn has been run.

The most common reason that people exceed the signon buffer is adding too many static entities to their map. So getting rid of some is one way to fix this issue for old engines. For other trick I'm going to be lazy and refer you to an old post I made:
http://www.celephais.net/board/view_thread.php?id=4&start=8227&end=8227

Have fun... 

hmm, cheers. Doesn't sound like something I'll worry about too much :)

Also have to giggle at myself. Map is full of trigger relays, at lot of which I could bin... cough I forgot Quoth allows multiple targets cough 

It means the amount of triangles in the mesh of the world model. Including bmodels. You can go up to 32767 before you break the limit. You can actually go slightly over this limit without breaking older engines, but only by a very few. 

If you do want to overcome the marksurfaces limit, and you would be under the limit without the bmodels in your map, I have an idea which I have not yet tested (I don't have a large enough map to try it out on).

The idea is to move the bmodels into external files. You'd need some way to create func_ entities which can have external models, which is a very simple QC job if the mod you're using doesn't support it. The hardest part is probably making sure the new models are properly aligned with the position of their original counterparts.

I admitted that I haven't tested this as a way of getting round the marksurface warning. The uncertainty I have is whether marksurfaces are truly limited per bsp file, or whether they are actually a global resource in the engine which cannot be exceeded by the sum total of all bsp models loaded. So if you try it then report back!