Speed issue with sprite update

[Windspar]

Also using Rect and Vector2 for math. Will speed up your program.

[michael1789]

I certainly need to change character movement to vectors to add better physics if nothing else. Everything thing is done with rect.x/y.

On another note, I suspect that pygame's display update might be built to ignore thing too far off screen and here's why:

I built a boss battle, and when the boss dies tumbles down rotating covered in explosions. The victory music and screen text are triggered when the dead boss sprite has fallen a certain amount. It triggers the victory stuff, and kills the sprite. What happened however, is that one time as the boss's body was falling I flew out of the room and away and the text and music didn't come. So I flew back in and the boss finished falling and the music came. It was like when the boss's body was far enough off screen the sprite didn't update, and only started again when I got close enough to it. I can replicate it and screen cap it, but I'm sure you understand what I'm saying.

Have you noticed or heard of this? Everything works perfectly if you stay in the room, near the boss sprite.

[Windspar]

Pygame.display.update() only update any rect that has change. Except when there to many and flip the whole screen. If your screen is in constant change it better to use pygame.display.flip().

That sound like something in your code. It like you stop process that data when you left. With out seeing code. I just be guessing.

[michael1789]

Yeah... I had a "in_boss_fight" tag.