Recomendations for map inspection software?

[Enjay]

What I'm looking for are tools that can read WAD/PK3 files, interrogate the maps therein and give me some kind of searchable output to tell me what is present on a map by map basis.

What I mean by that is - I run the tool on a particular map set and I could, say, get a text file liting all the texture names used on a map by map basis, or perhaps a list of ednums used on (again) a map by map basis.

With ZDoomHexen format maps, I can use DeePSea, but I'm pretty much leaving that format behind now. In the past, If I have been altering resources, I have found it very useful to be able to search through a map set to find which maps contain the altered resource. Then I can open those maps, and only those maps, in the map editor and check whether I am happy with the result without having to manually search through every possible map in a set "just in case".

Here's an example output for part of doom.wad from DeePsea that shows the kind of thing I mean:

---

Code: Select all

C:\Doom\IWADS\doom.wad       

     Level       E1M1
       

== Textures ==       

   1. BIGDOOR2
   2. BIGDOOR4
   3. BRNBIGC
   4. BRNBIGL
   5. BRNBIGR
   6. BROWN1
   7. BROWN144
   8. BROWN96
   9. BROWNGRN
  10. COMPSPAN
  11. COMPTALL
  12. COMPTILE
  13. COMPUTE2
  14. COMPUTE3
  15. DOOR3
  16. DOORSTOP
  17. DOORTRAK
  18. EXITDOOR
  19. EXITSIGN
  20. LITE3
  21. NUKE24
  22. PLANET1
  23. SLADWALL
  24. STARG3
  25. STARGR1
  26. STARTAN1
  27. STARTAN3
  28. STEP1
  29. STEP6
  30. SUPPORT2
  31. SW1COMP
  32. SW1STRTN
  33. TEKWALL1
  34. TEKWALL4

       34 unique Textures used
        
 == Flats ==       

   1. CEIL3_5
   2. CEIL5_1
   3. CEIL5_2
   4. F_SKY1
   5. FLAT14
   6. FLAT18
   7. FLAT20
   8. FLAT23
   9. FLAT5_5
  10. FLOOR1_1
  11. FLOOR4_8
  12. FLOOR5_1
  13. FLOOR5_2
  14. FLOOR6_2
  15. FLOOR7_1
  16. FLOOR7_2
  17. NUKAGE3
  18. STEP2
  19. TLITE6_1
  20. TLITE6_4
  21. TLITE6_5
  22. TLITE6_6

       22 unique Flats used
        
     Level       E1M2
       

== Textures ==       

   1. AASTINKY
   2. BIGDOOR2
   3. BROWN1
   4. BROWN144
   5. BROWN96
   6. BROWNGRN
   7. BROWNHUG
   8. COMPSTA1
   9. COMPSTA2
  10. COMPTALL
  11. COMPTILE
  12. COMPUTE1
  13. COMPUTE2
  14. DOOR1
  15. DOOR3
  16. DOORRED
  17. DOORSTOP
  18. DOORTRAK
  19. EXITDOOR
  20. EXITSIGN
  21. GRAY7
  22. GRAYTALL
  23. LITE3
  24. LITE4
  25. LITE5
  26. LITEBLU3
  27. METAL1
  28. NUKE24
  29. NUKESLAD
  30. PIPE2
  31. PLAT1
  32. shawn2
  33. SLADPOIS
  34. SLADRIP2
  35. SLADWALL
  36. STARG1
  37. STARG3
  38. STARGR1
  39. STARTAN1
  40. STARTAN2
  41. STARTAN3
  42. STEP1
  43. STEP3
  44. STEP5
  45. STEP6
  46. STONE
  47. STONE2
  48. STONE3
  49. SUPPORT2
  50. SW1COMP
  51. SW1PIPE
  52. SW1SLAD
  53. SW1STON1
  54. TEKWALL1
  55. TEKWALL2
  56. TEKWALL4
  57. TEKWALL5

       57 unique Textures used
        
 == Flats ==       

   1. CEIL3_5
   2. CEIL5_1
   3. CONS1_1
   4. CONS1_5
   5. CONS1_7
   6. F_SKY1
   7. FLAT10
   8. FLAT14
   9. FLAT20
  10. FLAT22
  11. FLAT23
  12. FLOOR0_3
  13. FLOOR1_1
  14. FLOOR3_3
  15. FLOOR4_1
  16. FLOOR4_5
  17. FLOOR4_8
  18. FLOOR5_1
  19. FLOOR5_3
  20. FLOOR5_4
  21. FLOOR7_1
  22. MFLR8_1
  23. NUKAGE3
  24. STEP1
  25. STEP2
  26. TLITE6_1
  27. TLITE6_5
  28. TLITE6_6

       28 unique Flats used
        
     Level       E1M3
       
etc 
etc
etc

So, if I have altered STARTAN3, for example, I can just load the above up in a text editor, search for STARTAN3 and then only bother opening the maps that use that texture. It's not perfect, of course, it won't catch textures that change during play (via ACS etc) but it does what I need 99% of the time.

DeePsea can't do the above for EdNums, but I have a separate tool called EdNumExplorer that does something similar to the above, but for map things. However, it does not work on UDMF maps.

So, what - if any - tools are good for doing this with UDMF maps?

Thanks

[DOTHEDA]

Can you tell me what EdNums are? I'm also not sure if you also want to be able to see what assets have changed from the base IWAD or just list what assets are used in the map (or both). The reason I ask is because I can make this program for you (if you didn't already find a solution,) I already have part of the program made as I wanted to see if I could do it and I think I can, once I know what EdNums are at least.

[Enjay]

EdNums = Editor Numbers - the numbers given to things; used to place an actor in the map.

e.g. Zombieman has EdNum 3004, Imps 3001, Soul Sphere 2013, Super Shotgun 82 etc etc.

I'm not trying to compare maps (e.g. original maps versus IWAD or whatever). I'm just trying to find out if particular resources are used on certain maps.

As examples:
Imagine if I have a particular texture that I'm not happy with, so I decide to improve it. However, doing so means it looks a bit different to what it did before and therefore it may now not look quite right in some places in my maps. So, I'd need to have a quick look at it in game/in an editor to see if the new version looks right. I know that I have used the original texture in several maps in a megawad, but I'm not sure exactly which maps. I don't want to search through every map, so I use a quick inspection tool that tells me that texture is on maps 02, 07, 12... So, all I have to do is look at those particular maps to check the new texture and I can safely ignore the other maps.

In the same megawad, I have placed my own DECORATE monster. I'm basically happy with it, but I feel, just occasionally, I want to use a tougher version, so I make a slightly more aggressive one with more hit points. I don't want to replace it randomly, I want to find every instance of the monster's usage and evaluate for myself whether it should be the easy version or the tough version that appears this time. Again, I know the monster is used in several maps in the megawad, but I'm not sure which ones. So, again, I'm looking for a tool that tells me which maps to look at and which maps to ignore; this time it would do it by searching for the EdNum of the monster.

So, I want to be able to point a tool at a multi-map WAD/PK3/Directory, have the tool(s) interrogate any maps that it finds and report back which textures/EdNums are used on which maps.


I know it probably sounds like a minor-use niche requirement, but I have needed to do this many, many times over the years in my old Doom and Hexen format maps. Now that I have (finally) moved over to UDMF, I don't have any tools that can do the above for that map format. So, any help would be greatly appreciated.

[Kappes Buur]

Maybe MTrop's Doom Utilities

[Enjay]

Thanks for the suggestion. However, I just tried ThingSpy on a UDMF map and

Code: Select all

thingspy map17u.wad -s 2011
Opening file map17u.wad...
    Opening map MAP17...
    Format is UDMF...
Exception in thread "main" net.mtrop.doom.map.udmf.UDMFParseException: (UDMFLexer) Line 3192, Token "1": Expected "}" to terminate object.
        at net.mtrop.doom.map.udmf.UDMFReader$UParser.read(Unknown Source)
        at net.mtrop.doom.map.udmf.UDMFReader$UParser.<init>(Unknown Source)
        at net.mtrop.doom.map.udmf.UDMFReader.readData(Unknown Source)
        at net.mtrop.doom.map.udmf.UDMFReader.readData(Unknown Source)
        at net.mtrop.utility.doom.thingspy.ThingSpy.inspectMap(Unknown Source)
        at net.mtrop.utility.doom.thingspy.ThingSpy.inspectWAD(Unknown Source)
        at net.mtrop.utility.doom.thingspy.ThingSpy.processWAD(Unknown Source)
        at net.mtrop.utility.doom.thingspy.ThingSpy.execute(Unknown Source)
        at net.mtrop.utility.doom.thingspy.ThingSpy.execute(Unknown Source)
        at com.blackrook.utility.Utility.go(Utility.java:83)
        at net.mtrop.utility.doom.thingspy.Main.main(Unknown Source)

The same map in Hexen format works just fine:

Code: Select all

thingspy map17h.wad -s 2011
Opening file map17h.wad...
    Opening map MAP17...
    Format is HEXEN...
        Reading THINGS...
MAP17

[edit] Same result with TexSpy
Shame, because these tools are meant to do exactly what I wanted.
[/edit]
[edit2]
Same result with the jar versions. [/edit2]

[DOTHEDA]

https://github.com/DOTHEDA/ednim/releases

Sorry it took me so long to make. I will probably be asleep soon so if it doesn't work, you have issues with it or it has bugs I will get to them tomorrow.
You use this program by typing:

Code: Select all

ednim [-t/-e] [-s] wadname.wad

As an example, you want to search;
Textures:

Code: Select all

ednim -t -s="startan2" MAP01.wad

or EdNums:

Code: Select all

ednim -e -s=321 MAP01.wad

You can also list them without a search:

Code: Select all

ednim -e MAP01.wad
ednim -t MAP01.wad

DO NOT put spaces between the '-s', the '=' and the search string. This is a limitation of the library I'm using and I will fix it at some point.

It does not support PK3's yet as I don't like using libraries if I don't have to and I need to learn how zip files work to program that functionality in.

It might be confusing to use so sorry about that and I'm not sure if it will please you entirely but I'm very much so open to suggestions/critiscism.
[edit]Oh ya, it also only supports UDMF right now, but I do intend to add support for standard Doom/Hexen (once I learn how those lumps work).[/edit]

[Enjay]

I'm sorry. For some reason I didn't spot this reply until now. I've just tried the tool and, unfortunately, I'm getting mixed results with it.

Some maps seem to be doing exactly what they should - I can get a list of all textures (or EdNums), or search for specific textures (or EdNums) and get the results I expected. Other maps give me feedback like:

Code: Select all

C:\Users\enjay\Desktop\EdNimTest>ednim -t map01.wad
fatal.nim(39)            sysFatal
Error: unhandled exception: over- or underflow [OverflowError]

All maps tested have been in UDMF format and get a clean bill of health from the GZDB error checker. The same thing happens with a texture check and an ednum check. In this particular case, MAP01 is bigger and more complicated than MAP02, but both maps are within UDMF spec.

The only other (much more minor) problem is that the feedback when no textures of a specified type are found is a bit misleading IMO.

Code: Select all

C:\Users\enjay\Desktop\EdNimTest>ednim -t -s="STARTAN2" MAP02.wad
-- MAP02 --
no textures found in this map (invalid wad?)

The "invalid wad?" message part always appears regardless of whether the tool has a good reason to suspect the wad's validity or not. The above was generated when searching for STARTAN2 (which it correctly could not find in this map) but it can read the wad OK because searching for other textures that are in the map gives a valid result.

[bLUEbYTE]

Hi Enjay,
I know next to nothing about Doom editing, but I think I can help.

Seeing as how UDMF maps are just text, you can make use of the traditional unix tools to do things like the ones you mentioned. I started my exporting the map out of the wad/pk3 into

Code: Select all

TEXTMAP.txt

using SLADE. Thanks to wadext and unzip, this archive extraction can be easily automated as well. In fact, the whole workflow can be scripted - let me know how you like this approach and we'll take it from there. The unix toolset is amazingly flexible overall.

To demonstrate (Using https://www.doomworld.com/idgames/level ... u/udmforig):

Search for and list the textures used in the map:

Code: Select all

$ grep texture TEXTMAP.txt
texturefloor = "FLOOR4_8";
textureceiling = "CEIL3_5";
texturefloor = "FLOOR4_8";
textureceiling = "FLAT20";
texturefloor = "FLOOR4_8";
textureceiling = "CEIL3_5";
texturemiddle = "BROWN1";
texturetop = "BIGDOOR2";
texturemiddle = "BROWN1";
texturemiddle = "BROWN1";
texturemiddle = "BROWN1";
texturemiddle = "BROWN1";
texturemiddle = "DOORTRAK";
texturemiddle = "DOORTRAK";
texturetop = "BIGDOOR2";
texturemiddle = "STARTAN1";
texturemiddle = "STARTAN1";
texturemiddle = "STARTAN1";
texturemiddle = "SW1STRTN";
texturemiddle = "STARTAN1";
texturemiddle = "STARTAN1";
texturemiddle = "STARTAN1";

Like above, but only list unique entries:

Code: Select all

$ grep texture TEXTMAP.txt  | sort | uniq
textureceiling = "CEIL3_5";
textureceiling = "FLAT20";
texturefloor = "FLOOR4_8";
texturemiddle = "BROWN1";
texturemiddle = "DOORTRAK";
texturemiddle = "STARTAN1";
texturemiddle = "SW1STRTN";
texturetop = "BIGDOOR2";

Same thing, but only list the unique texture names used in the map:

Code: Select all

$ grep texture TEXTMAP.txt | cut -d '"' -f2 | sort | uniq
BIGDOOR2
BROWN1
CEIL3_5
DOORTRAK
FLAT20
FLOOR4_8
STARTAN1
SW1STRTN

Count the number of unique textures used:

Code: Select all

$ grep texture TEXTMAP.txt  | sort | uniq | wc -l
8

Count the number of imps in every file in current directory, with filename (only one file in this example, but imagine each map in a separate .txt):

Code: Select all

$ grep -Hc 'type = 3001' *
TEXTMAP.txt:3

What OS are you on? On Windows, you can install Windows Subsystem for Linux (google a guide). On Mac & Linux, well, you already have what you need. Let me know if you like this approach and I'll walk you through or possibly develop scripts for you.

[Enjay]

I'm on Windows (10) and being able to get text outputs (particularly useful to me would be the unique ones but all are potentially useful). I have to admit that it sounds like you are proposing installing something quite hefty (i.e. the subsystem) versus what I plan to use it for though - i.e. to run some relatively simple scripted text extractions and consolidations.

[m8f]

For trying out Unix tools at Windows, I think "Git for Windows" is the easiest way to get in: https://gitforwindows.org/
Don't mind if you don't need Git itself. This package contains Unix command line interpreter (bash) and all the things like grep, uniq, sort, wc. The installer is about 46 MB. The installation is easy, just like any other windows program. This thing won't interfere with your OS. After the installation, you will be able to launch command line with Unix tools just by selecting an item in directory context menu.

[bLUEbYTE]

Yep, good call m8f. Another similarly light option is Cygwin, but it is kinda convoluted to pick packages to install, etc. Git for Windows should do it nicely for sure.

[DOTHEDA]

I'm so sorry for vanishing for so long, I had a rut to get through, but I finally made a (hopefully) functional program for your use case. Please tell me if there are any issues, I'll try to be more attentive to this thread.

Edit:
I actually updated ednim with a from-scratch re-write, so it should function as intended this time around. Use '-e #' to search for ednums and '-t STRING' to search for textures. Syntax would be;
'.\ednim.exe -e STARTAN2 DOOM2.WAD'
for example.
Again, sorry this took so long to make.

Download:
https://github.com/DOTHEDA/ednim/releases