You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deleting an object that has been assigned as the object following for a view will corrupt the project, making it give compile and project load errors
#8652
If you assign an object as the object for a view to automatically follow and then delete that object, the reference to the object in the room files will not be cleared. This makes it so the project cannot be compiled, and if you close it and attempt to reopen it, it will give project load errors. The only way to recover the project is to manually edit the .yy file for every room the object was used for view following in.
Steps To Reproduce
Create an object
Open up a room's view settings and assign the object under Object Following
Delete the object
The project is now broken
Which version of GameMaker are you reporting this issue for?
IDE v2024.1100.0.703 Runtime v2024.1100.0.719
Which operating system(s) are you seeing the problem on?
Yes.. the project is broken because of this.
It will need more thought on how to fix this as the serialiser has failed it on loading, because it cannot find the resource reference.
It is also part of a GMRView which is not a resource itself, so our normal way of repairing these cannot work.
Description
If you assign an object as the object for a view to automatically follow and then delete that object, the reference to the object in the room files will not be cleared. This makes it so the project cannot be compiled, and if you close it and attempt to reopen it, it will give project load errors. The only way to recover the project is to manually edit the .yy file for every room the object was used for view following in.
Steps To Reproduce
Which version of GameMaker are you reporting this issue for?
IDE v2024.1100.0.703 Runtime v2024.1100.0.719
Which operating system(s) are you seeing the problem on?
Windows 10.0.22631.0
48e9a486-b132-4fbb-831c-690d9a9a833b
The text was updated successfully, but these errors were encountered: