TextureAttrib of loaded .bam file randomly ignores off-stage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Panda3D |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When loading a .bam file containing a hierarchy of 2 GeomNodes, where the child GeomNode has a TextureAttrib that turns off specific texture stages used by the parent GeomNode, it can happen (randomly, it seems) that one of the stages is set to "on" for the child - at least in the *net* render state, even though in the local render state it is correctly turned off.
So if the texture stages used for the parent GeomNode are called "stage1" and "stage2", then the expected results for the child GeomNode would be:
child texture stages off: ["stage1", "stage2"]
child texture stages on: []
And while that is indeed always the case for the local render state, it can happen that for the net render state I get this:
child texture stages off: []
child texture stages on: ["stage2"] # this should be empty
Related topic containing more info and sample code can be found here:
https:/
As mentioned before, it can take a few runs of the code to see different results.
Changed in panda3d: | |
status: | Fix Committed → Fix Released |
Closing as this was fixed on GitHub: /github. com/panda3d/ panda3d/ issues/ 179 /github. com/panda3d/ panda3d/ commit/ 42f8978236147d8 743a6a75190e465 fa6b1f862c
https:/
https:/