try reading 

[i]1: Make your arch.

2: Rotate your arch 45 degrees.

3: Scale your arch in the X/Y plane by 1.060606... , OR up so the bounding box is 1.5 times larger than the original arch.

4: Snap to grid 1/4 of what the original arch snapped to (IE if the original was on grid 8, snap to grid 2)[/i]

This was the only reply that made any sense and seemed concise that even a n00b could follow. Problem is I did this and the gap was not filled.

You can either be a prick or tell me what I'm doing wrong. 

If your gap is x wide (orthogonally), the starting arch needs to be 4x/3 wide.

In your screenshot the gap is 80 units wide, which is not divisible by 3, which is terrible. Make the gap 72 or 96 units wide instead, which would make the starting arch 96 or 128 units wide respectively. 

Does anyone know where I could get a hold of "items.wad"? It's one of the standard id wads I believe but my googling is coming up dry. 

aren't all the bsp item textures like ammo box in the normal id1 TEXTURES.WAD?
And the mdl models then have their own texes inbuilt. 

None of the four standard id wads have those. You can extract them from the item bsps in the paks though. 

I extracted them from my own megawad:

http://shub-hub.com/files/gfx/items2.7z

There may be some missing, because I did it manually, but I think that's all. Also, the exlobox's aren't there.

Quaddicted also has a big list of wads, but I didn't want to download the full id wad just to check if its inside there.

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

Tripping over ourselves to answer that one. 

Also you get funky Items tex in Worldcraft3 combo!! 

Thanks for the responses guys, very much appreciated! 

And to add a little more info ... Yes, Quake101.wad has them in there but I was hoping that the actual items.wad was floating around somewhere. However, extracting and creating a custom wad from that one would be a problem for me because, remember, I'm on a Mac here. ;)

I think I've got it from here. Thanks again! 

Hi dear mappers.

I am in need of knowledge. I am trying to build a tool that would automatically sort maps by "type" based on differences.

I think I understood that ALL of TF maps have a in_tfdetect entity, but is there anything that particular for the other types? CTF/RA/CA/regular DM and such? 

I think is the name.

I think there must be at least some special spawns in RA for the players waiting if not anything else... 

A spot of Doom style blasting!

Plenty pine-apples, plasma battles and powerups!! 

How does the undo function in bspeditor work? For now I can only undo few steps. Is there any way to change it? 

Hello, Im having an issue with a fresh install of Quake on an older pc (pent 3 with gf3 ti200) where no version of glquake will run.

First both fitzquake and glquake could not find glide2x.dll so I downloaded a copy of that, now both programs will launch but then fall back to the desktop with the error "genport I/O initialization error" and then something about a non existent SST before a final error message telling me to run in the correct colour depth or something...

Anyone got any ideas? 

Just delete all the dll files in the Quake directory (unless you installed some more engines who brought their own). 

Yup that worked, thanks Spirit :) 

I thought it was just a case of dividing a brush into a mesh of vertices and then dragging the verts around to make some interesting mountains and terrain. But the mesh tool is only in 'Hammer' editor, and even that sucks ass.

Is it just just a case of building up a wall of multiple squares and matching up the corners with each verts are varying heights? 

I guess I was right in that last paragraph. Kinda made something that resembles a rocky wall using that method. 

That's generally the way it was done in Quake engines, yeah. Be aware though that if you put that sort of thing on the floor it can lead to a lot of sticky collision and weird sliding if you're not careful. In my experience, anyway... 

or 'flat triangular prisms' rather than squares, cause if you have a 'square' face that isnt straight, or on one 'plane', then it is an illegal face. But if you use triangles you cant have an illegal face...

Or am I on a completely different topic? 

It's still possible to make illegal or non-vis (the solid shape is treated as a leak - pointfile line goes right through the middle) prisms. Alot of the time now I use four sided pyramids just to avoid that. Maybe going to extremes but it tends to work.

Typically you get broken collision (player gets stuck on an invisible wall when walking from one direction but not another) when the brushes are misaligned, maybe by 1 or 2 units, making the difference invisible in most editors. Normally you must delete the offending brush and all adjacent and rebuild.

Wierd sliding tends to be caused with how you've built the geometry. Basically you learn what shapes the bbox's of Quake don't like to collide with. Typically it means not making the player walk along acute angles or severe angle changes. 

I made a tunnel in my current map with a curved cieling - the tunnel also curves round a corner and drops a total of 64 units on the ground too (ughh). If it didnt slope downwards it would be OK, but because it does I had to replace all of the 6 sided brushes which comprised the cieling with FOUR 4-sided pyramids (I think there is some sort of gap in the middle of each group of four) because bsp.exe was building the original set up with gaps between brushes by the time it had corrected all of the illegal faces!

I'm just glad to hear that someone elso uses a similar technique, cause I thought it was probably considered to be shit practise! 

The idea is not to have empty spaces in between brushes cos vis'll hack it up.

You can correct it in a drawn out way by turning the curved upper part of the tunnel into func_wall, then putting a real ceiling above that, so the map doesn't leak. The func wall receives collision and light, but doesn't cast shadows. That shouldn't matter because it'll have a false ceiling above, and the ends of the tunnel you can leave as real geometry since they don't curve.

As a further geometry hack / fix you can make the curves func_illusionary, then put simpler clip brushes so the player or monsters (especially fiends) don't get stuck.

As to it being bad practice, I think that's the only way you can make a downwards sloping curve. It makes a hell of a mess and produces some weird bsp errors but it works, sort of.