View Issue Details

IDProjectCategoryView StatusLast Update
0031511RunnerObjectsPublic2019-11-21 09:40
ReporterDanAssigned ToCoreTech 
PriorityLowSeverityC - GeneralReproducibility100%
Status AssignedResolutionOpen 
PlatformWindows VMOSWindows 10OS Version1903
Product Version2.2.4 
Target VersionFixed in Version 
Summary0031511: Objects: Combining instance_change() and instance_deactivate() can cause the re-activated changed object to always Step twice
DescriptionAs you can see from the attached sample, combining instance_change() and instance_deactivate() can cause the re-activated changed object to always Step twice as often as normal. It's seemingly not creating a clone, as the ID is the same.

You end up with the following (the number is the Step event counter variable for that instance):

**********************************.
Entering main loop.
**********************************.
MANAGER 100000: 0
PLAYER 100002: 0
PLAYER 100002: 1
MANAGER 100000: 1
PLAYER 100002: 2
PLAYER 100002: 3
MANAGER 100000: 2
PLAYER 100002: 4
PLAYER 100002: 5
and so on...

Expected:
**********************************.
Entering main loop.
**********************************.
MANAGER 100000: 0
PLAYER 100002: 0
MANAGER 100000: 1
PLAYER 100002: 1
and so on...
Steps To Reproduce1. Run the attached sample.
2. Observe the output window log looks like the above.
Repro: 100%
Additional InformationAlthough this was only found in 2.2.4, 2.2.2 at least has this same issue, so this isn't a new break.
TagsNo tags attached.
1.4 Found In
2.x Runtime Found In2.2.4.374
2.x Runtime Verified In

Activities

Dan

2019-11-20 10:40

Adminstrator  

instance_change_bug.yyz (22,932 bytes)