John Rohlf (jrohlf++at++tubes)
Sun, 30 Oct 94 12:12:44 PST
pfLights are "reference-counted" by the GL when they are bound
to a target like LIGHT1. Performer does not keep track of these references
so if you delete a currently-bound light you will have problems.
This is why calling pfLightOff( light ) before pfDelete( light ) helps.
The remaining problems might be due to pipelined multiprocessing
where the pfLight is in use by later pipeline stages for a couple of
frames after you delete it. The workaround is to pfLightOff() then
wait a couple frames before deleting. However, I will investigate the
possibility of pfDelete() automatically delaying the deletion for you.
Note that pfDelete already does this for pfNodes.
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:37 PDT