Delete scene does not clear object/behaviour name memory
-
Create a scene, place an object and/or a behaviour in there, give the object and/or behaviour their own names. Then create a second scene, attempt to make an object/behaviour with the same name as the one in the other scene. It won’t let you because the object already exists. Now delete the scene with the custom name object/behaviour, and try to make an object with the name of the object in the deleted scene. It still won’t let you, even though the scene with that object has been deleted.
-
-
Lol. This is nice, now I’ll go through the SQLite file and 1 by 1 delete all the old objects I know aren’t in my active scenes. And probably free up over 5mb
-
Apparently my project Meteor also has over 8000 behaviours, I definitely should not have that many after deleting a scene, but I find it hard to imagine that even my old scene had 8000 behaviours, could it be possible that deleting objects also doesn’t delete the behaviours in it? @Hamed
-
Bumping this because it's a pretty big bug and admins haven't responded: @Jack8680 said in Delete scene does not clear object/behaviour name memory:
... I see object names that don't show up in his scene.
-
@Jack8680 said in Delete scene does not clear object/behaviour name memory:
it's a pretty big bug
Huge, actually.
Literally and figuratively.
-
Hmm. The reason it was designed this way was to make deleting a scene instantaneous ( a loooooong time ago), it shouldn't have affected naming...
Will fix this.
-
@Hamed So you will have it delete all the objects and in a deleted scene and delete all the behaviours in a deleted object? One of the problems with the way it is now is that game files become larger than normal (my Meteor project probably has like 5mb of deleted stuff, it is a few years old).