They can, because all i am doing is replacing warp2.Enjay wrote:That would be cool but am I right in saying that they couldn't actually be added to the game as additional choices rather than replacements?
For lava, I imagine that something quite subtle like a heat haze effect might be quite neat.
Yes, that's what I meant. All that's happening is that WARP2 is being replaced. So, I no longer have WARP2. I have WARP and WARP2.1 only. I don't have WARP, WARP2 and WARP3.krumzy wrote:They can, because all i am doing is replacing warp2.
If I understand that correctly, the application is done from within GLDEFS as opposed to ANIMDEFS for custom shaders.ZDoom Wiki wrote:The second step to implementing custom fragment shaders is to define a HardwareShader entry in GLDEFS. Only one shader can be defined per valid graphic. A definition takes the following form:
[Type] is an optional and is one of either Flat, Sprite, Texture. This is useful to prevent ambiguity if the same name is used by several graphics of different kinds. <LumpName> corresponds to the graphic to which it is applied. <File> corresponds to the text lump containing your Process function. <Value> is a floating point value that defines a multiplier to be applied to the timer uniform.Code: Select all
HardwareShader [Type] <LumpName> { Shader "<File>" Speed <Value> }
So for <File> i put the file name and it came up with this:Blue Shadow wrote:If I understand that correctly, the application is done from within GLDEFS as opposed to ANIMDEFS for custom shaders.ZDoom Wiki wrote:The second step to implementing custom fragment shaders is to define a HardwareShader entry in GLDEFS. Only one shader can be defined per valid graphic. A definition takes the following form:
[Type] is an optional and is one of either Flat, Sprite, Texture. This is useful to prevent ambiguity if the same name is used by several graphics of different kinds. <LumpName> corresponds to the graphic to which it is applied. <File> corresponds to the text lump containing your Process function. <Value> is a floating point value that defines a multiplier to be applied to the timer uniform.Code: Select all
HardwareShader [Type] <LumpName> { Shader "<File>" Speed <Value> }
Code: Select all
Unable to load shader func_warp3::colormap:
Unable to load 'func_warp3'Yes.krumzy wrote:Do i have to add the location of the file as well?
You make a fork of Zandronum in which you port the relevant code from GZDoom.krumzy wrote:(also i know that zandronum doesn't define hardwareshaders so how could i convert this to zandronum?)