all-in-all texture stage support is a bit iffy. I had problems with extra texture stages being passed onto text and stuff. But putting this aside a hard call to clear all the texture does not work either … there appears to be no way to remove a texture stage after is been given.
before texture clean
TextureStage glow
TextureStage color
<type 'libpanda.TextureStageCollection'>
after texture clean
TextureStage glow
TextureStage color
<type 'libpanda.TextureStageCollection'>
////////////////////////////////////////////////////////////////////
// Function: NodePath::clear_texture
// Access: Published
// Description: Completely removes any texture adjustment that may
// have been set via set_texture() or set_texture_off()
// from this particular node. This allows whatever
// textures might be otherwise affecting the geometry to
// show instead.
////////////////////////////////////////////////////////////////////
void NodePath::
clear_texture() {
nassertv_always(!is_empty());
node()->clear_attrib(TextureAttrib::get_class_type());
}
////////////////////////////////////////////////////////////////////
// Function: NodePath::clear_texture
// Access: Published
// Description: Removes any reference to the indicated texture stage
// from the NodePath.
////////////////////////////////////////////////////////////////////
void NodePath::
clear_texture(TextureStage *stage) {
nassertv_always(!is_empty());
const RenderAttrib *attrib =
node()->get_attrib(TextureAttrib::get_class_type());
if (attrib != (const RenderAttrib *)NULL) {
CPT(TextureAttrib) tsa = DCAST(TextureAttrib, attrib);
tsa = DCAST(TextureAttrib, tsa->remove_on_stage(stage));
tsa = DCAST(TextureAttrib, tsa->remove_off_stage(stage));
if (tsa->is_identity()) {
node()->clear_attrib(TextureAttrib::get_class_type());
} else {
int priority = node()->get_state()->get_override(TextureAttrib::get_class_type());
node()->set_attrib(tsa, priority);
}
}
}
Note that clearTexture() only removes the TextureStages that have been applied at that particular node. If the TextureStage has been applied at a lower level, or if you applied it at that node and that moved it to a lower level with one of the flatten calls, then clearTexture() will not remove it.
The purpose of clearTexture() is not to turn off TextureStages. Its purpose is to remove any texture specification you have previously applied to that particular node.
If you want to turn off a TextureStage from a parent node, the method to use is:
node.setTextureOff(stage, priority)
where priority is whatever priority level you need to override the lower attribute.
The RenderState contains a TextureAttrib. The TextureAttrib defines a set of texture stages to be applied to the Geom.
The net RenderState (and hence the next TextureAttrib) to be applied to the Geom is accumulated by composing RenderStates from the root of the graph.
At any given node level, the RenderState might apply a new TextureAttrib. The new TextureAttrib is composed to the working TextureAttrib so far accumulated from the root. By the time you reach a Geom, the final TextureAttrib is the result of all of the accumulations of TextureAttribs at that node and above.
Each TextureAttrib can add a certain set of TextureStages and/or remove a certain set of TextureStages from those specified above. Also, a low-priority TextureStage will not affect a parent TextureStage with a higher priority.
So: at a particular node, you can turn off the TextureStage you don’t want and add the TextureStage you do want. Or, you can replace the texture associated with a particular TextureStage with a different texture.
If you also specify a priority on that node, then no lower TextureAttribs will further influence the resulting texture combination, by either adding or removing TextureStages. This is helpful when you want to shadow a TextureStage that is enabled at a lower level, but this trick cannot be used to shadow just one TextureStage while allowing other TextureStage changes to also be applied from a lower level.
So, if you want to remove just one particular TextureStage from the final state, but leave other TextureStages alone, it’s best to do it on the node that specifies this TextureStage, or somewhere below that node, and not specify a priority.
Is there some performance problems i should be aware of? This works for me except when shader get disabled but that is ok because my game cant really be run without shaders any ways.
I don’t see a problem with that. You’re just telling the shader precisely which textures you want to use, stepping around Panda’s built-in mechanism. Only downside is that Panda won’t know which sets of UV coordinates to send down, if you are using multiple UV coordinates, but maybe that doesn’t matter to you.
Well i am not using multiple UV cords so i guess i am set. Could i also name my data tables so that i can get them through shader. Thanks David! You are awesome.