Radiant Error - "null shader name"

(MrLego) #1

I am getting the following error message during the -light stage of my compile.

"null or empty shader name."

The light stage hangs for a minute or so before resuming.

I think that it is associated with one of the misc_models but I cannot be sure. I have been unable to find the creator of this.

Using brush cleanup does not help - it does not seem a problem with the brushwork.

Any suggestions?

(MadJack) #2

I remember getting that error but in radiant and after that, it was impossible to work, brushes were losing their texture turning white as you would move around the 3D window. The good part is it stopped doing that after closing and reopening radiant.

Thinking about that, I think there was a mention about space in a shader name too… Oddest thing is I don’t have any shader with a space. It’s probably not related to your problem but I thought to mention it.

(sock) #3

I am getting the following error message during the -light stage of my compile.
Code:
“null or empty shader name.”

The light stage hangs for a minute or so before resuming.

Try posting in the q3map2 forum as this is a compiler warning and someone might know exactly what is causing it. In the mean time go back to a previous version of the map and see if the error is still in previous versions. Also check your shaders directory for new files or recent changes as this might have been caused by a shader change. Sorry for not knowing the exact cause but hopefully these suggestions might help.

Sock
:moo:

(MrLego) #4

Thanks Sock - I posted there as well and received a reply from ydnar.

I have narrowed it down to the models used in a constructable MG42.

I suspect that it is the crates because they sometimes have a missing shader texture in radiant.

Once I removed all of the third party .pk3 files it showed up as a missing texture.

Now I just have to find the proper “_remap” shader to insert in that model definition.