View Issue Details

IDProjectCategoryView StatusLast Update
0020921Runner[All Projects] ObjectsPublic2021-07-28 15:30
ReporterTimocopAssigned ToCoreTech 
PriorityMediumSeverityC - GeneralReproducibility100%
Status ResolvedResolutionSuspended 
PlatformWindowsOSWindows 8OS Version
Product Version 
Target VersionFixed in Version 
Summary0020921: Objects: Deactivated Object Parents won't activate in the same frame/step
DescriptionIf you deactivate all instances of an object then reactivate them all within the same step the child object gets reactivated on that step but the parent objects don't. At the start of the next step the parent object is reactivated as expected but this seems inconsistent and I'm not sure if this is correct.

Attached is a sample which creates the child instance and then deactivates everything on creation, at the beginning of the step everything is activated and then at the end of the step everything is then deactivated. At the beginning of the next step the values shown last step are stored for comparison.

Also instance_count always returns zero, which seems like a bug too.
Steps To Reproduce1) Run the sample project
Additional InformationOriginal helpdesk ticket:
1.4 Found In1.4.1749
2.x Runtime Found In
2.x Runtime Verified In


Stewart Bishop

2016-03-30 11:14


ParentActivationProblem.gmz (70,480 bytes)


2016-05-25 20:20

Reporter   ~0043494

I did some testing.
Object Parents are 'not accessable/still accessable' when 'activating/deactivating'.
It doesnt matter if you de/activate the parent or childs of the parent, the parents wont update its activation state in the same frame.

The code attached works fine in legacy Game Maker 8.x versions and below!

Its realy hard to develop a game with this broken system :/
And a workaround to get all last childs from a parent is too ressource expensive.


2016-06-20 08:15

Updater   ~0044035

Last edited: 2016-06-20 08:26

View 2 revisions

Related? #20284


2021-07-28 15:30

Developer   ~0066524

Have moved to the current bug database now, as still happens in v2.3.3.