I like the feel of those texture sets too. I'm curious, do you plan to use the base Quake monster set, or a mod with tech oriented monsters? 

For the moment I didn't yet thought neither about monsters placement, nor items placement... I only started the architecture design... I also guess Quake base monsters should be enough, while I'm seriously thinking to use a CyberDemon for the last boss.... I get a mod where there is CyberDemon monster model, and I found it not bad at all (if I remember well, I find it in a Doom level remake named "Tower of Babel" done by Marc Fontaine... BTW who's this guy ? I never heard about him... )..
Anyway, I will see later how it could fit with the map.... and then I will decide if I include a (or more) cyberdemon in the map... 

I actually bothered to look online and found some helpful tutorials. It turns out that I don't have to move vertices with the crappy spraycan, and can use vertex edit mode to move them instead. Should be good! (proably crap though, I'm guessing)

Screens look interesting. Are you making a cs:s map? 

ok, so I was wrong about the vertex edit thing. You CANT edit the vertices directly, just use this stupid paint geometry shit, which doesn't even make sense. Why the hell to the vertices not move along the face normal when "face normal" is selected? Why can't I just position each vert where I fucking want them? Why do the verts move at about 5000 million miles an hour when I try to move them?

Ugh. 

i found it!
the crashes were indeed related to the teleporttrain. for it has to be triggered (be moving on its path) BEFORE it can be used as a teleport destination (at least with the mentioned engines).
but there is another catch: it has to be triggered some time before the teleportation, so just placing a trigger_once in front of the trigger_teleport won't do. apparently there has to be a delay of at least .2 or .3 between the triggerings, otherwise the game will crash.
i more or less fixed it with some temporary solution in the map, but it will work fine if it's used like in end.bsp. 'more or less', because the game still crashes with the same error message when the player comes too close to the moving teleporttrain in the tunnel (shoudn't happen though, because of spawning monsters).

this is probably not rooted in the progs.dat, i assume, as this bug only occurs in some engines and not in others, but i couldn't tell for sure. maybe it's just logically obvious - i don't know...

btw. aguirre: the map loads correctly and works in winquake-bjp's window mode, but it still crashes with "unbalanced unlock" in fullscreen mode for whatever reason. 

this is probably not rooted in the progs.dat, i assume, as this bug only occurs in some engines and not in others, but i couldn't tell for sure. maybe it's just logically obvious - i don't know...

Is this the one you said wasn't a bug in fuhquake? Well, fuhquake has a totally different progs.dat becuase it's a quakeworld engine. 

... latest mappage; BSP signals "Solid BSP", calculates Hull1, begins to calculate Hull2 then indicates a leak. First time I've come across this particular order of things. I've gone back in and simplified the geometry in the indicated area, no change. Pointfile only passes through brushwork at one place... the middle of a large solid floor brush?

Any ideas? 

http://www.iddevnet.com/quake4/LevelEditor

must read for q4 (and d3 too ) mappers 

You seem to have a hull 2 leak. Take a look at my Q1 ToolTips: http://user.tninet.se/~xir870k .

Basically, the leak isn't visible and only shambler-sized ents will be able to detect it (by e.g. falling out). Inspect the brushes that intersect with the brush that the leak line penetrates. It's probably one of them that "pokes" a hole, especially if the intersection is non-axial.

If you wish, you can send me the zipped map+wad and I'll take a look at it. 

hello i'm new here but i was wondering if there where some jungle, grass textures out there i could use or even maybe some prefabs jungle wice like say leafs and trees and such
if someone is wondering i'm trying to make a unusual quake dm map... as i always do ;) if you guys want to have a look at my previous maps go here http://www.geocities.com/elvstrom
hope someone can help me it's kinda hard to do stuff when your not sure what your doing ;) 

o.k i�ve learn somethings and i already make some mapping... but got a problem what is rvis??? how to use it? i put the light�s and all the stuff but dont know how to use this...

any help? 

id provided quake with three programs to compile maps to bsp:s with:

qbsp.exe - this makes the bsp
vis.exe - this makes the bsp faster to play by making it so that rooms not visible from the current room are not drawn. If map has leaks, vis aborts (sort of). If vis is not run, the map has really bad fps unless it's very small and simple.
light.exe - makes lightmaps for the map. If this is not run, the level is ugly fullbright.

rvis is another alternative for vis.exe. I think aguirre's utils have the actual filename as vis.exe. You just edit your editor's settings to use the aguirre's tools instead of the ones that came with the engine. You can read the readmes in the zip for how to use additional features.

Read the basic tutorials please. 

... my first Hull2 leak :) I'll check (and simplify) all contact with that floor brush before I send through a map + wad. 

You're probably out of luck on doing that style...the closest thing I can think of is take some textures from Vondur's Uzuldaroum http://wp.vondur.net/index.php?page_id=15

Quake isn't great at handling high-poly models without using a custom engine, and you would definitely need some custom code to get any sort of grass/leaf/tree models into the game in the first place. 

thks bambuz, then i just have to run rvis :) is not something i have to add to the map :) the other stuff i think i�m making better every day... just wait for my next speedmaps :) they are getting better everyday!

did sm109 = crap
sm110 = less crap
sm111 = almost crap but not crap :)= 

All necessary files at:
http://skynet.campus.luth.se/~chosen/bam/spir/

The map is just a 12-sided spiral where the floor is split into triangles. Just 24 triangles per circle.
It's pretty big.

1) I find that qbsp (fail to remember if it's tree or tx) really fucks up my map, it makes all kinds of crazy excess amounts of triangles from flat four-sided polygons (the walls of the spiral). Too bad I don't have a shot here, but if you load that spi7.bsp in fitz and put r_showtris 1, you'll see what I mean.

2) vis doesn't block other parts of the spiral very well, although it's absolutely clear that they can't be visible from the current location. I've run fullvis but not -level 4. Vanilla id vis gives a playable map only at even smaller map sizes (spi7van.bsp).

3) if the map gets big, neither fuh or fitz will load it, they complain of some malloc overflow or something similar. I have to put about three quarters of the map inside a solid cube for it to load. The original map is very high but it should not have big continuous areas. It does have brushes spanning almost the whole height of the grid (the outer and innver walls of the spiral) but they should be broken by qbsp anyway.

What to the help? Sky textures? I tried that on the outer wall, but it didn't help, at least not noticeably. Upscaling textures?
This morning (haven't tried it yet) I came up with a way to reduce some brushes (floor can double as the below-roof if I make the brushes thicker), but the result should be identical after the qbsp phase.

Why does it crash?


- And sorry metl for not investigating that plat thing further, it was a speedmap that I then abandoned since it was getting so much out of hand in idea and style. I don't have internet on my own computer so handling files is always a little hassle. 

if qbsp tried to make the minimum amount of triangles, every 12-sided "storey" would only have 24 floor tris, 24 roof tris, 24 outer wall tris and 24 inner wall tris, that is total of 96. 

it seems it's treeqbsp and aguirre's vis uses testlevel 4 by default if i read the logs right. 

It sounds like you have ye olde AllocBlock: full error in Fuh/Fitz. Take a look at my Q1 ToolTips for hints, engine section. Also, my engines can usually load such maps and they'll tell you how many lightmaps that are required.

And yes, my RVis defaults to level 4. Qbsp has nothing to do with vis levels. 

I loaded your map into darkplaces, and looked around a bit with r_showtris 1.

1) Those aren't "excess" triangles. QBSP's subdivide size usually defaults to 256, and it appears to me that the massive surfaces of your structure were, for the most part, neatly subdivided into 256*256 blocks, each of which are further divided into two triangles for rendering. It just looks like the subdividing went crazy because your surfaces are so huge. You can change the subdivide size from qbsp's commandline, but I think if you set it really high, like 1024 or so, you'd get other errors besides the malloc/allocblock thing (maybe a subdivideface: didnt split the polygon?)

2) That's vis for you. sucks, doesn't it? You may be able to cut down on that very long visible distance if you put in some periodic retaining walls that radiate out from the center core of the spiral.

3) I ran into this with a similar map. My layman's guess is that some engines just hate large brushes, even if qbsp is supposed to subdivide them. Try breaking those brushes that are the size of the whole available grid into about 4 subsections and see what you get. 

Thanks for the help guys, I have a few more questions.

1) Lightmaps
Would it reduce them if I made more of the textures as sky? That isn't lightmapped, correct? I can also increase the tex scaling by 2 in both directions easily in the floor.

2) Triangelization or however it's written..
Well I'm still not at home and can't post shots, but it seems at times, a 4-sided polygon is taken from one corner and divided into twenty thin triangles or something.

3) How do I increase the subdivide size in qbsp? Didn't find any docs. Aguirre you could really compile even a short list of switches into the readmetree and readmetx files.
-subdivide 1024? 

and/or increased tex scale will help reducing lightmaps. As for subdivide size, you set it with the -subdivide x option, although I definitely do not recommend messing with it.

You can get a brief option list with any of my tools by just running it without any parameters, results end up in the console window and in the log file (if any). 

I increased the floor and roof tex scale to 4 in both directions and now it compiles and runs at full 77 fps in fuh (and 72 in fitz). I also removed some flat areas from the map and further reduced the brush count (151->102)...

Now this
http://skynet.campus.luth.se/~chosen/bam/spir/fitz0098.jpg
still happens, but what can you do... :/

Neatly subdivides into 256 blocks since I was using 256 grid. 8)
The new version is in the dir as zip http://skynet.campus.luth.se/~chosen/bam/spir/sispi7.zip 

checking out the spi7 map, I'd suggest that you try to avoid sky brushes touching solids outside the map. Load up the map in my GLQuake, noclip outside and you'll see what I mean; huge textured faces covered in sky that probably generate a lot of lightmaps.

You should always avoid having visible faces outside a map, especially if they're big. 

I wondered the same too... I only changed them to sky because the map didn't run, i might be able to avoid it now.