| Additional Information | see bug discussion: http://modetwo.net/darkmod/index.php?/topic/10148-doors-staying-frob-lit/
I could investigate this issue today, and it seems this is a defect of the code keeping up with the entities' "am I frobbed" state.
The problem depends on several conditions:
- The frob-highlighted entity A has frob peers
- The frob trace seamlessly transitions from entity A to entity B.
- The newly frobbed entity B updates its frob status before entity A (basically a race condition)
Reason: the frob highlighting code regularly checks (each frame) whether it is frob-highlighted or not. To determine this, it compares the CDarkModPlayer::m_frobEnt pointer with "this", which is not reliable in the case of frob-peered entities. When entity A is highlighted, it propagates its frob status to entity C which is frob-peered to entity A. Hence the check fails (either this or the check using m_frobEntPrevious fails). So the code decides not to de-highlight and the door stays brightly lit.
This is not an easy fix, and I'll have to re-design this algorithm a bit, considering frob_peers (a single frobEnt pointer is not suitable for this kind of check). This is going to need some serious testing afterwards, as frobbing is a critical function. |
|---|
