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
Tron 
whoa - that would kinda help things i guess :} 
Um 
doesn't DUBSP.EXE output a <mapname>.max when it compiles a .MAP file ? I am assuming that is a 3dsmax .MAX format file but I've never tried opening one. So all you need to do is use BSP>MAP converter and then compile with DUBSP.EXE

This is all theoretical of course :) 
BSP>MAP 
Hmm 
I've seen a tool that can export q3bsps to VRML, so if you can go to q1bsp->q3bsp somehow you may pull it off without having to write a line of code.

A breif google didn't turn up any easy way to do that, though. 
Kinn 
Most of those command line editors have some severe limitations to them.

I would recommend using Id's Quake 3 Arena tool BSPC to decompile the bsp into a map file (it works on all Quake formats) and then use a utility like 3d Exploration to convert the map into an obj or 3ds file. There is a non trial period version of 3d exploration floating out there, but I haven't seen it since in several months.

Baring that, you can convert the .map file into an .ase file using q3map2. 
Anyone? 
Is it possible to compile Q3 or any of its tools with Visual Studio 6.0? If so, could someone please point me to a resource that lists out the steps necessary to accomplish this?

I am such a Visual Basic/non-C++ person (n_n)

Thanks in advance (^_^) 
Hey Generic, 
You need a simple command line tool called prjconverter (I'm sending a copy to your email address in a second). Drop the VC7 project file into it and it'll pop out VC6 dsp and dsw files. From there it compiles like a breeze. 
Kinn: 
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. 
Generic , 
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 
Errr. .. 
www.codeproject.com/tools/prjconverter 
Cool 
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. 
It Strikes Me 
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. 
Texture Alignment 
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? 
Mike: 
is it on a surface angled 45 degrees? 
Well Yeah... 
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. 
Cheers... 
Thump!

I'll have a look-see... 
Texture Misalignment 
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 
Mike... 
Are you using Worldcraft/Hammer?

Is the texture rotated?

Also, boxers or briefs? 
Maybe 
maybe there is a duplicate brush (with misaligned texture) which isn't clearly visible in the editor but gets visible in the engine? 
Texture Misalignment 
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! 
Weird... 
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... 
Generic 
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 Don't Know About Directoire But... 
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 :| 
That Happens 
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. 
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.