News | Forum | People | FAQ | Links | Search | Register | Log in
Mapping Help
This is the place to ask about mapping problems, techniques, and bug fixing, and pretty much anything else you want to do in the level editor.

For questions about coding, check out the Coding Help thread: https://www.celephais.net/board/view_thread.php?id=60097
First | Previous | Next | Last
 
Put them inside a func_wall made out of clip brushes, but whose corners (BBOX extents) have a tiny normal brush inside.

Those normal brushes tell Quake that the clip brushes are there.

Then remove the func_wall when you want them to be active.

Never actually tried it, but should work. 
Hmm 
are the non clip brushes supposed to be in the Func_wall or out of it, because it dosent work when there in it and when they're out i get this error:

*** ERROR 13: Line 2131: Entity with no valid brushes or textures

1 warning

Elapsed time : 0:00

Peak memory used : 1.8 MB

!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!
Build failed, because it did not create the (+BSP) file: C:\Users\alex\Desktop\q
uake\tmpQuArK\.\maps\mstart.BSP 
 
That's why he said to include a tiny, real brush somewhere within the func_wall entity. Quake won't complain if you have at least something in the entity with a texture on it. Hide it in the map itself by making sure it's inside of a wall or something. 
Yep 
 
Circular Jump Pads 
Remember those wicked jumppads in some Q3 maps that had you fly in a curve? The same is possible in Quake. Pretty obvious, but I only just thought of it again.

Take a look at this test map: http://www.quaketastic.com/upload/files/misc/pushtest.zip

The trick basically involves pushing the player towards a curved clip surface that determines the direction of the flight. The clip curve has to be fairly smooth so the player doesn't fall down prematurely. In the test map the small jump (1/4 of a circle) has 8 faces, the large one (3/4 of a circle) has 24. The map is pretty crude (but you'll get the idea) - it takes some experimenting with the pitch angle and the push speed. The larger such a push is (radius and distance), the uglier it becomes, because the clip wall and the pitch have to be a lot higher.

Now there aren't really that many situations where such a push would be useful. Imagine perhaps a castle with push-connected towers. Or a deathmatch map, although then one has to take into cosideration that NQ and QW handle the speed values in different ways.

At any rate, such a push can at least make for some funny wheee! effects. 
Hmm 
What about making a map where you fly along wind tunnels between different rooms and use keys to unlock new tunnels? Mebe with some water. And in brown... 
Like... 
... antedeluvian map ? 
QuArK And Changing Entities 
i has...have these new stuff in my progs that need entities placements on the map, but im finding that when i add an entitiy like ambient_drone i can't changeit, to something like ambient_front242. but i remeber doing it before somehow :S

the only solution i have is to edit it in the .map with a text editor but i find this somewhat of an out of the way solution

...i wonder if this makes sense 
Or 
why don't you just add the entity,
click on the object list,
and change your classname to monster_xxx? 
Oh...your Progs.dat 
search and replace function? 
Ya You Had It 
quark won't let me change classnames and i don't know why is what i meant with that paragraph and a half

and its kind of annoying because i could do it before i think 
 
QuArK lets you change classnames easily. Either slow double left click in the tree or edit in the detail view. 
State File Does Not Match Portal File 
A VIS error I could not find any documentation about. Does anyone here know what it means ?
It's a real error, not just a warning, no VIS is preformed. 
Ron: 
probably vis is trying to finish a partially-completed job, but you've changed the bsp since then. I think you'd just need to delete the state file, but i don't know what the filename would be (never used that feature myself.) 
 
I didn't know about this feature at all.
Anyway, reading your reply made try and just rename the map,that worked ! Thanks !
I've just switched to the WC 3.33 version so I might come back with some dumb questions later ... 
Surpsisingly... 
... aguirRe's tool tip does not mention this error :/ 
State File 
I think you just have to delete the vis file to that map your compiling and aguirre's vis will make a new one. I get this while updating and changing texture names in a wad file. 
Monster Count 
While betatesting my level I came up to some errors I forgot how to avoid them.

First there's the monster count eror. I assumed they were caused by the fish, with its double swimmonster_start in the qc. Strangley it didn't help help deleting it, because I still get a double fish count.

Second is the strange habbit of some zombies.
Their heads seems to run on while being killed, which is rarely difficult to trace while they're in slime.
I got the effect earlier with bones. I can't find a reason for it. 
Breakable Crates 
Do I remember breakable (not exploding) crates for Q1?

If so, does anyone know where I can get the qc/mdls from, if available? 
Quoth's Got Breakable Crates... 
Mounds don't :-) 
Extras 
Supports as well - Quoth's are simpler to use though. 
Crates 
Quoth code not been released so I'll look at Extras 
See If There's Been An Update On The Source Chode Thread 
Ahem.

What extras has is model swapping and emissions. So you can swap a mesh in the map for a broken one (external bsp) and spawn a spray of emissions at the same time - these can be sprites, models or other external bsps.

It's not really tied up into a ease of use package though - you'd need a few seperate entities for it to work. 
Although 
Emissions are well worth having - a very powerful tool. 
Mike 
Do you want our source? It's got extras inside, but also alot of other stuff. We're not supporting it (heavily commented) though, so you're probably better off with base extras. 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.