seriously, you should check out custents, it has everything you are talking about.

you can specify a train to move so that it gets at it's destination in a specific time instead of telling it to move at a speed, and there is a setting to remove the delay when it hits a corner. 

Thanks! Looks like it might work!

ijed: shhhh! It's a surpise! No nothing as simple as alien birds. 

 

Thanks, I've been looking for that option. 

Hey guys,

I'm designing a map called "maw of madness" and as the title of the map suggests I want to give the player the feeling of being swallowed by madness.

As such I want to use the waterwarp effect in certain sections of wall. However, I don't want the wall to be traversable / swimmable. Is there a way to make completely (not semi) transparent walls? a brush with no texture or an opposite of func_illusionary?

Thanks in advance,

Ben 

You have two methods to choose from.

1 - Clip brushes

Make a brush and give it the clip texture. The player will not be able to pass through this brush, and they will not be able to see it.

One bad way of making a ladder is to make a detailed ladder as a func_illusionary. Inside the ladder make a set of steps that are 1 unit wide, and put it inside the ladder. When the player walks into the ladder they are instantly transported up the invisible staircase (just like a normal staircase, but all of the steps are within boundaries of the ladder's space, so the player moves upwards).

2 - Skip Texture

Make a brush and create a texture with the name 'skip'. Apply the texture to the brush. The brush will still be there, but it wont be drawn. You can use this tool on individual faces too. And you can apply it to brush entities, like doors for example. This can be used to do all sorts of things in Quake.

When you compile the map, you have to run the newskip tool to remove the faces. Created by Metlslime: http://www.celephais.net/files/newskip.zip 

Then run newskip or compile the map with these tools to have the skip texture removed automatically. 

You can shoot through them. They are great for putting diagonal brushes against pillars, for example, at the side of a corridor, sticking out of a wall.
Ever start shooting a monster in a corridor and you are moving backwards and sideways and you get stuck on a light or something? And you die because you got stuck and pwned? A well placed diagonal brush can prevent this from happening as easily, because you just glide over the thing that is sticking out of the wall.

I should do this more often :D 

or jsut make the water out of func walls with water texture on them -- it will be solid and block bullets but render as water. 

Thanks guys, learning all the time :)

In a few days I'll throw a deathmatch map I've been making up for critique. The basic geometry is done, entities are done and lighting is getting close.
I'll upload with the mechanics all finished for critiquing before finishing the texturing and decorative brushes. 

 

 

 

 

 

Warning: 256 Models Exceeds the Standard Limit of 256.

Okay, so what is it really? 255? Or do I actually have more that 256 and it's just not telling me? 

It will still load in unmodified ports despite the warning. You just can't add any more if you want to keep it vanilla.

If this or any of the other limits become a serious problem in your map, feel free to give me a shout. It seems I'm getting pretty good at optimizing these things... :P 

func_illusionary details, try grouping some of the ones that are close together into one model. 

I well understand the limits and have gotten pretty good at optimizing stuff. What I was pointing out is this:

256 exceeds 256

Which it actually does not.

I'm guessing it has to do with counting that starts at zero instead of one. I probably have 257 models.

I've been adding one unnecessary func_wall off and on over the last several builds just to see how close I was to the limit.

I'll take one out now and the warning should go away.

Nevertheless, 256 is not more than 256

The good news is, I still have 5 or 6 models left to play with :) 

It's probably a counting issue and a bug of that message. The index would 0-255, the range of that is 256 items. So the model with index 256 would be one over the 0-255 range as it is actually the 257th model. 

negke: are you sure > 256 models loads in engines that don't support it? i remember having to remove bmodels from some maps like nesp09 because there were over 256 and it was crashing the engine. 

What I meant is that a map with exactly 256 unique models will still load despite the warning in Fitz and BJP. Anything above that number will cause a crash. 

It might load, but I suspect that you'd have problems with model 256. The limit is because vanilla quake sends the model value as a single byte over the network. If you try and send 256, the server's going to send 0 instead - and 0 is interpreted by the client as "no model". As long as you're happy with the last model only being visible in engines with higher model limits, you can have 256. 

the message is slightly buggy i think. The true limit is that a model with index >255 will break the network code on protocol 15 (you'll have some invisible entities.) So 256 models is okay, 257 is bad.

The bug in fitzquake is I used >=256 instead of >256 as my check for displaying that message. 

As we were talking about it in the thread of mfxsp6 and in others, i became more curious about it, and want to know more before i get this one in my maps. So i ask:

What is HOM exactly? What causes it? How do you fix it?