 |
Any changes should continue to honor this setup: 1 - WIP lives in "Doom 3/mymission/" 2 - start TDM using this command line: "C:\Program Files (x86)\DOOM 3\TheDarkMod.exe" +set fs_game_base darkmod +set fs_game mymission 3 - in the TDM console, enter dmap mymap 4 - dmap compiles the map and places the output files in "Doom 3/mymission/maps/" The "darkmod/fms/" directory isn't involved in any of this. |
 |
We have been talking about removing support for loading things from "doom3/mymission" completely because it can hit people ater upgrading (when there are left-over files there that interfere). Just saying. |
|
|
That's been my work setup for the past 2 years, and I remember it as described/recommended on the wiki. It keeps my work separate from the darkmod folder. Does the command line then need to change to: "C:\Program Files (x86)\DOOM 3\TheDarkMod.exe" +set fs_game_base darkmod +set fs_game darkmod\fms\mymission and will TDM and dmap understand that? |
|
|
No, as far as I understand, you would use "+set fs_game mymission" as usual, but things are now always located in "darkmod/fms/mymission" (the PK4, savegames etc are already all loaded from there, and the map compiler now puts the .lin file there, too). Basically, instead of using "doom3/" as "base", it will use "where_ever_tdm_is_installed/darkmod/fms" as base and then append the "mymission/". The reason is that: * putting arbitrary folders under "doom3/" can conflict with other mods (this becomes less a problem if TDM goes standalone) * reading things from "doom3/mymission" has a high chance to pick up things left-over from old installations * putting things into "doom3/mymission" can fail if this directory isn't even there (the mission is installed under "darkmod/fms/mymission" by default) * putting things into "doom3/mymission" can confuse (there are now two locations to look for things) |
 |
Should be resolved in Revision 5479. |
- Anonymous
