This is an old question and the answer is simple,
NO.
WHY? Because the BSP file does not have this information.
In reality, BSP files only have the list of WAD files it uses and the names of the textures, but it does not have information to which WAD file a particular texture belongs. The names of these textures are unique within a BSP.
---------------------------------------------------------------------------
The way GoldSrc (CS 1.6) works gives the false impression that it "knows" which WAD files are needed. But not quite...
To understand how GoldSrc (CS 1.6) works, let's imagine the following scenario: You have loaded a BSP file, but you have not made any of the referenced WAD files available...
Code:
[...]
"wad" "\programme\valve\valve\thwc_hl.wad;\programme\valve\cstrike\sourcebuero.wad;\programme\valve\cstrike\villaggio.wad;"
[...]
... in the "cstrike" or "valve" folders.
So, still within this scenario, let's imagine some more situations to demonstrate how GoldSrc (CS 1.6) would act when trying to load each of the textures pointed at in the BSP file:
- Attempts to load all referenced WAD files that are in the "cstrike" or "valve" folders. Cannot load any;
- Tries to load each of the referenced textures. Can't find the first one;
- Search the list of WAD files and notice that the first one is not loaded. Then it warns that this file is missing (message box);
- The user makes this WAD file available in the "cstrike" folder and tries to load the BSP again;
- Loads all the referenced textures that are in the available WAD file, but realizes that there are still unavailable textures;
- Asks for the next WAD file in the list;
- And so on...
---------------------------------------------------------------------------
PLUS: POSSIBLE SOLUTION (A LINUX APPROACH)
The only possible solution to programmatically determine (via BASH script, for example) which WAD files are needed is to export the list of textures from a WAD file with a utility like "HLExtract.exe"...
EXAMPLE
Code:
WINEDEBUG=-all wine "<PATH>/HLExtract.exe" -p "<PATH>\SOME_WAD.wad" -l | grep -i ".bmp" | cut -d\\ -f2 | cut -d. -f1 > "SOME_WAD_TEXTURES_LIST.txt"
... and based on the obtained list check each of the textures inside the BSP using a utility like "strings"...
EXAMPLE
Code:
strings "<PATH>/SOME_BSP.bsp" | grep -iw -- "SOME_TEXTURE_NAME" >> "SOME_BSP_TEXTURES_IN_USE.txt" 2>&1
... so that if located, then this WAD file is in use by the BSP file.
NOTES:
- The first command lists all textures in the "SOME_WAD.wad" file and outputs to the "SOME_WAD_TEXTURES_LIST.txt" file. The second command checks if the texture name is in the file "SOME_BSP.bsp" and outputs to the file "SOME_BSP_TEXTURES_IN_USE.txt" making an append if it already exists - useful for executing the same command in sequence;
- A BSP file can have its textures embedded in it so that it will not need the referenced WAD files;
- A WAD file can have textures that have the same name as textures in another WAD file. The precedence of loaded textures is always by the last loaded WAD - the order followed is the same as the "wad" attribute which has the list of referenced WAD files. This can give the false impression that a WAD is not needed if a previous one already has textures with the same name, however this can result in the wrong textures being loaded.
Thanks! 🤗
Linear Mode
