xyz I was trying to do this and then found out that if I delete the AnimatedSprite2D of the pickup or delete the sprites of the enemies, the freezing goes away. Maybe the issue is from animation instead of enemies changing state, but that doesn't explain why it only happens when there's two different enemies and a pickup, unless the issue is that the file sizes are too big and the engine chugs trying to animate them, but I don't think I'm even at the scale where that's possible yet, especially with only two enemies.

  • xyz replied to this.

      Camp Well only remove the resources (images, textures etc...), not the nodes themselves.

        If I delete the SpriteFrames resource from the pickup and keep the textures of both enemies, the game still freezes. If I delete the texture of one enemy and the SpriteFrames of the pickup or delete both enemies' textures and keep the SpriteFrames, it doesn't. I also tried deleting the player's texture and that also fixed the freezing.

        • xyz replied to this.

          Camp It doesn't matter what does what. If you want to get it looked at and the project is too big, first try to delete the .godot, if still too big delete all scenes except the relevant one, if still too big resize all the images to 1/16th of their size, or smaller. The point is to reduce the size of the project for posting.

          • Camp replied to this.

              xyz What I'm trying to say is that when I make the project smaller the bug stops. If I did resize the project, there would be no bug. This is why I think the freezing could be coming from the animations, not the state machine.

              • xyz replied to this.

                  Camp Well then remove things one by one and the last thing you removed before it started working is likely the cause.

                  • Camp replied to this.

                      xyz I did that and I found that removing different things would make the bug stop. I'm thinking it has to do with the number of textures being loaded / the size of them?

                      • xyz replied to this.

                          Camp Use the profiler and debugger monitors to surveil what's happening with system resources at runtime.

                          • Camp replied to this.

                              xyz The process time seems to be what's causing the freezes, but what does that mean? I've never used the profiler before so I don't know what I should change.

                              • xyz replied to this.

                                  Camp If you suspect the memory is getting eaten up then you need to look at monitors tab in the debugger. If you've never used profiler/monitors, then read about it in the docs. Those are essential tools.

                                  • Camp replied to this.

                                      xyz All of the memory graphs look constant so I don't think that's the issue. None of the other graphs seem to be spiking or dipping like the FPS graph. Here's a screenshot of all the graphs I thought were unusual, though.

                                      • xyz replied to this.

                                          Camp Look at the frame time in the profiler and visual profiler, switch states and see what consumes the majority of time in spikes.

                                          • Camp replied to this.
                                              6 days later

                                              xyz I replaced the textures with smaller ones and my issue went away, so I guess that's what the problem was.