we have an issue showing up with git builds, even with nexcompat enabled: some custom maps won't load some textures. curiously, it's mostly quake banners & annoying animated pads underneath weapon spawns. for example, at qzdm7_q3, we get a message:
Code:
MQC Build information: xonotic-v0.8.2-2574-g2f86afcef
Switching to map qzdm7_q3
"maxplayers" set to "16"
loadimagepixelsrgba: corrupt or invalid alpha image textures/sfx/portal_sfx_alpha
maps/qzdm7_q3.bsp: could not load texture "$lightmap" (frame 0) for layer 1 of shader "textures/ad_content/2x1"
maps/qzdm7_q3.bsp: could not load texture "$lightmap" (frame 0) for layer 1 of shader "textures/ad_content/1x1
this issue does not exist with official stable binary build (linux).
FSMP ☠ ♩♪♫ мµѕιcgoαт[91] ♫♪♩says you people have got to know what this is all about. bug or not bug, can we please just get some info on this? we tested with (linux x64) git build and autobuild justa a few days ago, and still some banners on some legacy (usually quake) maps are showing checkers. stable 0.8.2 shows banners ok. we really want to understand how we can fix that server-side. these are our options, as far as we can tell, so what do you think is the best way forward, or are we missing anything?
1. do nothing and wait till next xonotic release, because this is a known regression which will be fixed at some point
2. do some magic in configs or data/ dir to replace or disable the checkers somehow
3. fire up netradiant and replace the non-showing textures for good
please help
we can't sleep anymore, that's how much these checkers are bothering us.
Guys I have a fix,
sk.void told me about it. So heres what you do:
1. use the terminal to go to the xonotic folder (for me it was msys: cd xonotic)
2. type in:
Code:
touch data/xonotic-nexcompat.pk3dir.yes
3. then type:
Code:
./all update -l best
4. then run:
you should be good the textures should be back to normal