I'd start with the engine code as a base, since it turns the bsp into a giant list of polygons that share edges and vertices. From that point it's just a matter of spitting out what's in memory into a standard 3d mesh format. UVs could be retained, as could references to textures/materials.

Not saying this is a trivial job, but it seems mainly like a question of learning the file format you need to output. 

I sent the program as a zipped attachment, but got back a postmaster response that the zip has kooties are something. I checked it with several commercial and free antivirus programs and nothing turns up. I suspect the filtering processes being deployed are growing more bullshit oriented by the day.

So this should be just as useful:
www.codeproject.com/tools/prjconverter.asp 

www.codeproject.com/tools/prjconverter 

thanks for the replies guys. I guess it seems there's already ways of getting a .map extracted from a .bsp and then turning the .map into a mesh - although I can imagine this would result in a rather messy mesh, retaining all the brush polys that would normally get culled during the bsp stage.

metlslime's idea sounds promising - use a modified engine to spit out just a nice clean mesh of the visible hull that I could get into .ase format to import into DOOMEdit, which I could then show/hide to act as a visual guide to the layout and scale whilst I create the new brushwork. 

use a modified engine to spit out just a nice clean mesh of the visible hull that I could get into .ase format

as overkill for what you are trying to accomplish. 

I have one entity brush on which the textures are misaligned by 16 units when in-game compared to the editor view. No other entites are affected in this way (or have ever been).

Anyone any clues? 

could it be the -oldaxis thing? 

is it on a surface angled 45 degrees? 

if all he's trying to do is convert the map to a more recent id engine game, using a mesh in any stage of the process is silly.

Just do bsp2map and open the map in doomedit. Or, wait for Romero to release the maps, and open THAT map in doomedit. 

Thump!

I'll have a look-see... 

Neg!ke: tried the -oldaxis but it didn't make any difference but did mess up some 45 degree textures.

Metlslime: no, this is not a 45 degree surface 

Are you using Worldcraft/Hammer?

Is the texture rotated?

Also, boxers or briefs? 

maybe there is a duplicate brush (with misaligned texture) which isn't clearly visible in the editor but gets visible in the engine? 

generic: I use BspEditor (latest) and the texture is not rotated or off-set in any way. Oh, and commando!

Ankh: when I read your suggestion I thought you had got it as this brush does come from another map and I could have double-pasted. But no, not to be.

It appears to be off-set 13 units. Perhaps I'll just have it unlit and nobody will notice! 

the whole commando thing ;)

Mike, if you offset it 13-units in the editor, does it fix it in the game?

Have you copied the brush elsewhere in the map to see if it still draws funky?

Does it matter what texture it is?

Well... 

Yes, I off-set in the editor and it looks OK in-game. The minnor problem is that the entity brush is set amongst ordinary brushes with the same texture so it looks stupid in the editor.

Ho hum, I'll carry on.

(OK, if not commando perhaps directoire?) 

I can sympathize with your texture trouble. In my yet-to-be-released mini-marcher speedmap, I had some rotated textures looking rather sweet in the editor, but they looked very poop-ish in game. It turns out I was rotating them by fractional degress which Quake, apparently, does not do :| 

rather sweet in the editor, but they looked very poop-ish in game. often with my set up as well. Easy enough, once you get use to, it to watch for in a full map, but really inconvenient for a speed map.

Uh, boxers -- the boys gotta beathe, but commando causes too much straffing with heavier fabrics. 

I'd be worried about more than my underwear fit if my genitals had the ability to bunnyhop. O_o 

it's a Latin thing, and the Ladies love it! 

I just remebered that in the Bsp.ini file (I use BspEditor) there is a setting to resolve the 45degree problem.

In version .94, I noticed that it is switched off by default: texture_alignment=0. So you need to change it to texture_alignment=1 and that avoids the problem.

Obviously, only relevant if you use BspEditor. 

using the latest bspeditor for texturing because of those discrepencies. In GTKRadiant the texturing tool, the surface inspector, is geared towards q3map2 capabilaties, and when I see everything looking hunkydory in the editor and then screwed up in game, it is a bit of kneebiter. 

In 1.4, edit this line in local.pref

<epair name="Q3Map2Tex">true</epair>

In 1.5, I think it's an option in preferences. 

<epair name="Q3Map2Tex"> true </epair>

With no spaces. 

I've tried that and I've been making a test map. The way it works reminds me of good old QeRadiant, but that is what I need!