Problem description: (This issue did not occur in previous versions; additionally, this error does not affect game execution.)
After upgrading to the new version, if an object is generated directly under the root scene, an error appears when opening the project.
(Through investigation, the specific location of the error was identified.)
Generating BaseSettings under the object produces 2 lines of errors.
Generating CollisionShape2D under the object produces another 2 lines of errors.
If BaseSettings and CollisionShape2D are deleted, the errors no longer occur.
If not deleted, running the game with F5 stops the error reporting, but restarting the project still results in errors.
This is considered a bug.
Problem description: (This issue did not occur in previous versions; additionally, this error does not affect game execution.)
After the new version upgrade, if an object is directly generated under the root scene, an error message appears when opening the project.
(After investigation, the specific location where the error occurred was found)
Generating BaseSettings under the object produces 2 lines of error messages.
Generating CollisionShape2D under the object produces 2 more lines of errors.
If BaseSettings and CollisionShape2D are deleted, there will be no more errors.
If not deleted, running the game with F5 will also stop reporting errors, but restarting the project will still result in errors.
We found this last night and it is definitely being looked into. You are correct this didn’t happen in previous versions so we are treating it as a bug.
It shouldn’t affect the game, it’s only console errors which is annoying
If you want to get rid of the errors, you can save that Game Object as a scene and the errors will go away. I know not all scenarios can do that though
That is essentially the issue, AGMaker is erroring out Game Objects that aren’t saved as scenes, so we will look into and hopefully fix it.
Some _variable’s are not accessible, but if it not suppose to be then they at least need to be hidden. We should try to make is possible though.
You are correct; if the object is saved as a scene, this error does not occur. (In my original project, there was an object scene, and when I instantiated it in the main scene, no error was generated.)
However, from a long-term perspective, issues will arise.
(1) There are many such objects that serve as temporary controls within the scene. If every object is saved as a scene, the project will require saving a large number of objects as scenes, which creates significant redundancy.
(2) If we ignore this issue, constantly dealing with a large volume of errors will be very frustrating. In another of my project files, opening it triggers over 100 errors because too many of these temporarily generated objects have been placed.
Therefore, I still hope the official team can provide a better solution.
(1) I saved all temporarily created game objects as scenes, eliminating all errors.
(2) Currently, this solution has resolved the issue without significantly impacting the project.
(3) It now appears that the correct approach for using game objects is to directly generate “object scenes” through the entry point provided by AGM, and then apply them to the main scene. This is a solid usage strategy. If you need to dynamically generate a game object in the main scene, simply save it as a scene, and that will work without issues. At present, this is the optimal solution.
This bug has been resolved in V1.1.1; generating unsaved objects directly in the scene no longer causes errors. Thank you to the official team for the swift fix!
This bug has been resolved in V1.1.1, and generating unsaved objects directly in the scene no longer generates errors. Thank you for the official quick fix!
