q3map2 2.5.16.2 (reyalp) BUG

(Twisted0n3) #1

— LoadMapFile —
Loading C:\Program Files\Quake III Arena\baseq3\maps wq3tourney5.map
entering C:\Program Files\Quake III Arena\baseq3\maps wq3tourney5.map
Shader textures/twq3tourney5/black1 has
NM textures/twq3tourney5/resources/bump.tga
Shader textures/twq3tourney5/black2 has
NM textures/twq3tourney5/resources/bump2s.tga
Shader textures/twq3tourney5/black2_brick64 has
NM textures/twq3tourney5/resources/bump2_brick128.tga
************ ERROR ************
LoadTGA: Only type 2 (RGB), 3 (gray), and 10 (RGB) TGA images supported

I double checked and bump2_brick128.tga is in fact a 24 bit RGB TGA, same as plenty of files q3map2 accepts without trouble. So either it’s erroneously choking on a valid TGA, or it’s indicating the wrong TGA as the one that caused the problem. Either way it’s a bug.

Any suggestions/known workarounds?

(Twisted0n3) #2

Addendum: I checked all the targas referenced by the shader file and found bump_brick128 was greyscale, not RGB as intended. I changed it to RGB and tried the compile again and it worked. So it is two separate bugs:

[ul]
[li]It erroneously indicated bump2_brick128.tga as the problem file when it was bump_brick128 (no 2).
[/li][li]It erroneously claims to support greyscale TGAs when it obviously does not.
[/li][/ul]

Please fix at earliest convenience, especially the first one. I don’t relish having to go over every tga with a fine-toothed comb manually. I want to be told which one REALLY has a problem whenever one of them does, instead of having to guess or check them all, because next time there might not be a handful there might be a hundred.

(SCDS_reyalP) #3

I haven’t touched the image loading code at all.

(Detoeni) #4

Its because he is using an 8/16bit tga

(Twisted0n3) #5

A greyscale TGA will be 8 bit as a matter of course. In any event the major issue is that it doesn’t correctly identify the problem file – it indicated bump2_brick128.tga as the problem when it was actually bump_brick128.

I don’t suppose you did change the image loading code; I was just indicating exactly what version I was using since that’s normal bug reporting practise. I guess the bug exists in ydnar “official” q3map2s as well then.

On the other hand, this might be an excellent reason to start changing the image loading code, so that it correctly identifies the file that caused the problem in future versions. Because I don’t relish having to check or blindly re-encode every tga in a directory every time it does this. :slight_smile: