View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003051The Dark ModCodingpublic06.03.2012 07:1713.12.2022 04:58
Reportertels Assigned Toduzenko  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product VersionTDM 1.07 
Target VersionTDM 2.11Fixed in VersionTDM 2.11 
Summary0003051: Targeting a bind children causes endless "trigger" loops
DescriptionWhen you have f.i. a binary mover that targets an entity, which is at the same "bind time" (e.g. the mover is bound to it, or the entity is bound to the mover, or both are bound to the same bindmaster), then activating the mover will trigger the mover's targets, which includes the mover itself, which will result in an endless trigger loop.

If there is a mover involved, the loop will continue whenever the lever/button etc reaches on of it's end states. If this is an "instant" triggering entity, a lockup with 100% CPU will likely be the result.
Additional InformationProposed solution is to not activate a bound children if it is the same as the entity that started the activation in ActivateTargets() in Entity.cpp.
TagsNo tags attached.

Relationships

related to 0003048 resolvedtels coding for target spawn entity 

Activities

tels

tels

06.03.2012 22:35

reporter   ~0004375

The one application (lamp entities with a lever attached that targets the lamp, to toggle it on/off) works now because the loop is stopped in the script: we only activate targets when these targets where not already activated as bound children, so the lever does work correctly.

But this bug might still exist if you attach a lever to another mover, and then target one from the other. Still investigating to see if it can be triggered.
nbohr1more

nbohr1more

13.12.2022 04:58

developer   ~0015556

Fixed by Duzenko in Rev 9923

https://github.com/stgatilov/darkmod_src/commit/7a6eeb93aad43b342466b7781b31e8f0482758f6

Issue History

Date Modified Username Field Change
06.03.2012 07:17 tels New Issue
06.03.2012 07:17 tels Status new => assigned
06.03.2012 07:17 tels Assigned To => tels
06.03.2012 07:20 tels Relationship added related to 0003048
06.03.2012 22:35 tels Note Added: 0004375
15.05.2013 15:26 tels Assigned To tels =>
13.11.2014 01:42 grayman Status assigned => new
13.12.2022 04:57 nbohr1more Assigned To => duzenko
13.12.2022 04:57 nbohr1more Status new => resolved
13.12.2022 04:57 nbohr1more Resolution open => fixed
13.12.2022 04:57 nbohr1more Fixed in Version => TDM 2.11
13.12.2022 04:57 nbohr1more Target Version => TDM 2.11
13.12.2022 04:58 nbohr1more Note Added: 0015556