I'm trying to set up a Fast HTTP Download server for DoD Retail 1.3, with some of the old Beta era maps, like Valley, for instance. When I used Resgen to make a .res file for each map, it listed a lot of wads that I don't have, so the Fast HTTP Download fails and it reverts to the slow version. This would make me think that I need to find those wad files for the server.

However, if I put the dod_valley.bsp file directly into my Steam client and then connect to the same server, it only had to download a couple small sound files and then the map started right up.

This makes me think that the wad files it looks for must be somehow bundled right into the bsp file. Am I correct?

If this is the case, how do I figure out which wads are bundled into the bsp file? Is there a quick way to do this?

Thanks!

AFAIK, it's the mapper that includes the texture files into the map via "-textureinclude" before compiling the map. However if the mapper used common DOD1.3 textures in their map (textures that *may* not be default, but nearly all maps have them anyway), then the mapper would not use the command and just have the map reference a .WAD file in which the required texture is contained.

On your end, you can only extract the textures from the map... not include them. However, I think there might be a MAn or a Pakrat-type program available.

Otherwise, I suppose you could just attempt to find ALL the wads known to humans and save those onto your server...

but if the textures are compiled into to map there should be now need for the wads, on the client or the servers

I had the same problem when I converted the old maps to work with the new v1.3 DoD. dod_valley was an original 1.0 -1.0 Beta map.

Not all of these maps had textures in them and there was an array of wads that they used. All of these are available in the original DoD package.

As far as wads go dod_valley didn't use any wads, the mapper put the textures in the map but Hammer still referenced them and that data still appears in the map. I use a program called wintextract to find out what textures are missing from a map. Take a look at dod_mainz_classic. I found all the missing textures and made a new wad for it. This minimises the size of the download for any given map.

None of MY classic maps will now work for the original version of DoD they came with, that's why I renamed them.

You need to get a hold of the Original version of DoD to get the correct wads, unless you can find them on the internet somewhere.

Google by the wad name including the extention, you sometimes find a copy floating around somewhere.

If this is related to your Beta 1.3b server then I would have thought you had everything to get this working?

Thanks for the info!

Actually, Haircut, I'm not getting much traffic to the 1.3b server, so I am trying to port the DoD Beta 1.3b maps to DoD Retail 1.3 and set it up for fast HTTP downloads.

The beta maps do work in DoD Retail, as long as you make sure all of the sounds and wads and sprites and such are copied over. Some of the wads referenced in the map file, like cs_bdog.wad for Valley, is not anywhere in the DoD folders. However, if you have the dod_valley.bsp file, the game loads right up, which is why I think it has something to do with the wad files being compiled into the bsp file, or perhaps not even being needed.

I think I've got most of the files I need taken care of, though I will try a search. I'm also trying an experiment to comment out the references in the res files for the bundled wads. This should allow the fast http download of the bsp file. I did a small test yesterday and it seemed to work.

Please let me know if you see any problems with my thought process here.

Thanks!

Originally posted by Wabbit
Some of the wads referenced in the map file, like cs_bdog.wad for Valley, is not anywhere in the DoD folders.

Yes, it's just the reference from Hammer when the mapper made the maps. He would have taking the textures from those wads and compiled them into the map, the reference to the wad will stay in the map.

wintextract confirms this.

My converted dod_valley_classic (dod_valley from Beta 1.1) won't have those wad references because I edited the BSP and took them out. This makes setting up a .res file a lot easier.

Just PM me here or on Mardy if you need any help finding old files. like I said, I've got all the mapping files for every Beta version of DoD.

I think I have fixed the issue. I went through all of the res files and commented out the references to the wad files that are not included in DoD Beta 1.3b, Vavle or DoD Retail.

If anyone has the time, I'd appreciate it if you could please fire up your DoD 1.3 Retail or Gold version (not Source) and take a few minutes to log on to the server, "Classic DoD Maps! Fast HTTP Downloads!" at IP address: 24.39.54.73. Downloading the maps should be very quick now, and the server is very stable. All the good fun is there! Please let me know of any issues.

I'd really appreciate it. Thanks!


Oh, and here are the files that I commented out of the res files:

halflife.wad
cs_bdog.wad
cstrike.wad
arbor_arch.wad
ashkan.wad
caenwad.wad
flak38.wad
hillassault.wad
lvpc.wad
m10.wad
m1_stuart.wad
mattcdod.wad
megamikedeus2.wad
murs_tiger.wad
prefab.wad
punkass-masakoswad.wad
sdkfz_251.wad
bush.wad
cf_mansion.wad
dod_bridge.wad
fearme.wad
machinegun.wad
mikey5.wad
texpack1.wad
tfc.wad
tfc2.wad
train.wad
tree101.wad
urbanizized.wad
vn61.wad
dod-wad.wad
jap.wad
japwad.wad
outdoor-war.wad
something.wad

Thanks!