Created attachment 2022[details]
solution
Shader hash chains should be stored in reverse order to allow more recent (custom) shaders to be used instead of default shaders with the same name.
Comment 1Zachary J. Slater
2009-03-25 17:15:36 EDT
Not a bug, this is standard quake3 behaviour and was never changed in ioquake3 in the first place.
If you want custom shaders with the same name to replace the default ones, just make sure the corresponding pak files get loaded before pak[0-9].pk3
If we were to change this now, god knows how many quake3 installations would be broken due to some mappers being careless and having shaders with default names in their maps.
(In reply to comment #3)
> Not a bug, this is standard quake3 behaviour and was never changed in ioquake3
> in the first place.
> If you want custom shaders with the same name to replace the default ones, just
> make sure the corresponding pak files get loaded before pak[0-9].pk3
> If we were to change this now, god knows how many quake3 installations would be
> broken due to some mappers being careless and having shaders with default names
> in their maps.
If you mean ioquake3 as standard quake3 then yes, but if you mean 1.32[b,c] then definitely not - just put custom console shader and check it
Created attachment 2022 [details] solution Shader hash chains should be stored in reverse order to allow more recent (custom) shaders to be used instead of default shaders with the same name.