Doom3world

Make a shortcut to the editor using this properties:

Doom3.exe +set r_fullscreen 0 +set r_multiSamples 0 +wait +wait +wait +editor
// edit by Goliath

We had this problem during leak times (the failed openGL calls resulting in various wgl.. errors) and now it seems to solve the annoying and often reported mouse cursor missing error.

Also disable Anti Aliasing - this is known to cause errors more frequently than not.

the r_fullscreen 0 variable means that the editor runs windowed on your desktop. That allows you to use it at desktop resolution and you can nicely maximize it for a larger work area.

A lot of sites and people repeatedly demand their readers to add a r_mode value - don't do that, it's not neccessary.
You will most likely want to run it windowed.

DOOMEdit will most likely not work. Consider to switch to Win2k or XP. If for Doom or not the upgrade is absolutely worth it. Not sure about WinME, but most people told me stay far away from it.

You can either lower the console and type "editor" or make a copy of the shortcut to the Doom.exe and add "+editor" to the properties - it'll start up seperately from the game then. The properties will look like "C:\DoomIII\Doom.exe" +editor where +editor has to stand outside the quotes. If you editor doesn't start up, then add two or three +wait calls before the +editor.

If you don't know that you should read our basic tutorials listed in the sticky "Tutorial Listing" thread in the Level Editing Forum. Link below.

view > show curves

The map must be sealed from the void - see below :"map leaked"
You need to put at least one info_player_start in the map

Save it somewhere below your maps directory.
Either in a seperate folder, or just populate your "maps" folder to get lost and disorganized as fast as possible...

This is dangerously common. Anyways, there should be a backup on the root of your C drive, as "autosave*.map".

Start up Doom  and type: "dmap maps/yourpathinfo/yourmapname" or press the bsp button in the editor.
That's it. Doom will compile your map in a few seconds and you're ready to walk through.

Well, your map has a leak :)

That means it's not a closed hull. If you use patches instead of brushes as walls, your map will leak.

Patches do not block vis. "Vis" determines what the engine considers as structural, hence blocking it.

If the engine can't see the void from any given point and viewing angle in your map it's a closed hull. If you feel unsure - just make a box the size of your entire map and place it in.

Other reasons for leaks can be entities (lights, spawn points, mapobjects, speakers...) which reside outside your map.

You will also make sure, that your map contains at least one "info_player_start" - that's the place where you first appear when you start your map.

If you get this leak message, but you can sware it's enclosed, you might have used a shader, or better "material" which has the surfaceparm "nonsolid" or "trans" (not yet sure which ones are present here).

If nothing hels - go back to the editor and select "pointfile". You'll see a line appear zickzacking through your map. Usually the line starts at an entity like a light inside the map and points to somewhere outside the map. Follow the white rabbit, err, pointfile line and you'll find the cause or your leak.

Your compile went well, no leak, only a few error messages?
Great - now type "map yourmapname" in the console and it'll load up.
Play it for what it's worth!

Yes you can, but it needs a little work.
First, as usual, make a backup.

Then resave the map using the "brush primitves" format.
Remove all entities (lights and stuff, you will want to rework the whole thing anyways).

That's all - will load now nicely into DoomEdit, yet ALL textures have to get reworked (search and replace works like a charm) and ALL texture scaling data will get lost when switching from the normal map format to the brush primitives format (it's not a bug).

The level editing (le) forum is best suited for this, please limit your images to a width of 480 pixels, you can still provide a link to your highres shots...

Start a thread in the level editing (le) forum and announce it with a proper headline like "username_map_1 is finished"

Maps WIP for Work In Progress to get feed back and Maps Final when you're finally done

PK4s are just zip files with a renamed extention. Use WinZip or WinRar to extract them. Extract them to a folder outside the doom3 directory to avoid conflicts with custom content.

Run the editor in windowed mode. Ensure you have the main editor window active when you press "J"

Set the "model" key/value pair to the name of the trigger.

Set the key/value pair "s_waitfortrigger" to 0.

They are settings you can use to control a specific entities properties

There are material shaders in the game that reference files that don't exist. These shaders are scraps left by the developers.

Open regedit, search for "DoomRadiant" and delete the key.