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
And Again... 
i still like quarks texture applying. 
Moving Platforms 
I tried messing around to figure out how to do it but can't figure this one out. How do I get brushes to move around like you see in many of the areas in the game? (Quake). I am talking about things like platforms that move back and forth and also things like those those cubes at the end of E1M2 that move around. How do I create those? 
Hakkarin 
thats a lot of questions..
head over to:

quakewiki.org/wiki/mapping

in entities you'll find what you looking for

googling the unofficial quake specs should be helpful too. 
Hakkarin 
func_train and Path_corner to be more unprecise 
Moving Platforms 
For platforms that only move in one direction like back and forth, or up and down, you can just use a door. For more complex motion you'll need to use a func_train with multiple path_corner entities. 
That's One Question To Be Precise 
Moving platforms are func_train entities. They move along an interlinked set of path_corner entities. The plaform starts at the path_corner it targets (if it has a targetname itself, it will only start moving after being triggered); each path_corner targets the next one, and the last one the first. If the platform is supposed to stop at the last path_corner, set "wait" "-1" there. 
Da Fuk 
Slow typer... 
Random Marksurfaces 
OK, my next foray into the realm of messing with BSP compilers, and the first real success (sort of).

http://tomeofpreach.wordpress.com/2013/06/07/random-algorithms-and-bsp/

Now with graphs! Yes graphs! 
 
Very interesting research into the BSP process, Preach.
It's weird how the results we so different from a box map and a full size one.

Have you tried this test with maybe some small maps like DM maps? 
Other Tests 
Afraid I didn't try any map in-between. I'd go and give it a shot now, although I expect that the result would be more like the latter than the former. Unfortunately I can't do that easily right now, because I've been revising the code for a future post, and don't have the original compiled at the moment... 
 
I was mainly interested in pinpointing where it started to become 'bad' and to try to pinpoint what it is about full maps that don't show up in box maps. 
Cutoff Point 
I may have some insight into that from the new tests. It seems like there's a very fine balance to strike with random input - it seems to work best for trying out different ways of resolving "ties". I guess that in the simplest of test maps there really isn't any difference between just tie-breaking and randomising everything - but I think as soon as you add any real detail then the difference matters. 
Just To Say 
I'm following this as well, thanks for the work.

Nothing solid to add though. 
Ijed 
is it possible to make rmq using some modern free engine?

i remember i've seen e1m1 on crytek eng 
Shit Wrong Thread 
 
And That Promised New Method 
http://tomeofpreach.wordpress.com/2013/06/09/quasi-randomised-algorithms-and-bsp/

So here's the way I was talking about, it gets you some improvement, even in the average case, over the deterministic compile run. I'm pretty sure that because the randomness is so low level, it's almost always a case of multiple tying brushes, and the randomisation changing how the tie is broken.

It's not mentioned in the post, but I did check and this version also performs well on the simple test map file. We achieve the same minimum of 160 (over 100 tests), and I'm beginning to suspect that can't be bettered. The graph shows an improvement in the average case, similar to the one that's in the article. So that's reassuring. 
Not Ijed 
is it possible to make rmq using some modern free engine?

that would end up being a free quake replacement, and zenimax would probably sue you for theft of IP. 
Not Sure I Understand The Question 
It's on a free engine... if you mean porting it to something like Unity or sauerbrauten then yes it'd be possible, but in that case it'd be better to make a standalone brand new FPS game using the same ideals as Quake.

Making a classic FPS game isn't too taxing in terms of asset and feature creation, as long as you make a feasible plan and still to it.

An idealistic FPS is almost impossible to make :)

And a AAA FPS would be a great big waste of time.

It also depends how much of a hobby or job the project is in terms of both your own time and if you can pay others for theirs. 
Prevent Monster From Running Off High Edge 
I have a thin and narrow platform (shaped as a square) that monster_ogres run around. It's over 256 units high from the ground, supported by 4 pillar/beams.

When monster_ogre sees the player, they run off the edge, dropping down to the floor below.

I was surprised to see this. I thought monsters don't do this.

I can't seem to find any information on this in google or quakewiki. 
Figured It Out 
The problem is the UI bounding box for the entity (in TrenchBroom) is misleading/inaccurate. I made my platform as wide(or narrow) as the entity's box, so the entity falls off the edge.

To prove this, I surrounded my platform with walls, and the entity was stuck.

Same issue with the monster_dog box. I put a monster_dog in the corner, and it's stuck. I had to move it 8units away from both walls (of the corner) for it to work.

Pretty annoying. 
 
the engine checks for collision in a >= way (as opposed to > ) so monsters have to be at least 1 unit away from walls to avoid getting stuck and have to be on platforms at least 2 units wider to avoid falling off.

note also that narrow pathways will be very difficult for monsters to move into because the checks for movement are done in discreet steps. 
Thanks 
I added your information to http://quakewiki.org/wiki/Entity_guide

Feel free to adjust, or find better place for it in quakewiki. 
Max Leafs Visible 
"max leafs visible: 416 near (-832 -2824 576)"

Although this doesn't appear to be a warning or error message, I still see it as one. I wasn't getting it before, and now I am; and I have no idea what it means.

I've googled it a number of ways, and getting no good results.

What does it mean, and how do I troubleshoot it?

Does it mean too many polys for a certain area of the map from point to point? 
Nah It's Not An Error Message 
It's just a report

It tells you that of all of the places in the map, the one with the most leaves visible to it (as in when the player is stood there) has 416 visible to it. You can go WAAAYYY higher than 416. The other three numbers are the coordinates of this position. 
How Do I Use Quoth Content In My Quake Levels? 
So I heard about this awesome content pack called Quoth that adds a lot of stuff (monsters, weapons etc) into the game for modders to use in their levels. However, I have no idea how to make any of this stuff show up in NetRadiant (the level editor I use) or appear in-game. How do I load these custom resources into the editor and use them? 
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.