• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
PaladinJohn

Pygame - Completely Removing a Sprite from Memory

2 posts in this topic

Hello!

I'm working on a Breakout style game, and after much testing I've pinpointed my exact problem. Sprites that I've given the .kill() command to and removed from all groups are still persistent in memory and causing issues. Below are a few excerpts of my code, and I'd appreciate if someone could point me in the direction of a better command to use, or perhaps a logic error in my coding.

 

(Note:

spell = ball

shield = paddle)

 

The root of the problem

 

I decided to add some simple items to enhance gameplay. This particular item is supposed to split your ball into three:

 

def itemEffects(self):
    if len(self.spellSprites) == 1:
        if self.spell.angle == 30 or self.spell.angle == 45 or self.spell.angle == 60:
            tempSpellx = self.spell.rect.x
            tempSpelly = self.spell.rect.y
            tempSpellSpeed = self.spell.speed
            tempSpellAngle = self.spell.angle
            self.spellSprites.empty()
            j = 30
            for i in range (0,3):
                self.spell = Spell(self.shield)
                self.spell.setStats(True, tempSpellx, tempSpelly, tempSpellSpeed, j)
                self.spell.setVelX(self.spell.angle)
                self.spell.setVelY(self.spell.angle)
                self.spellSprites.add(self.spell)
                j += 15

Directional movement is locked on 12 seperate angles, 3 for each quadrant. This code checks the quadrant, saves the current balls relevant stats to a temporary variable, clears the entire ball sprite group, then creates three new balls given the saved stats with the three angles for that quadrant. I believe the problem is that the first sprite created in this group remains in memory even after it's .kill() function is invoked.

 

Ball Death

 

Here is the code for when a ball meets it's untimely demise:

 

for theSpell in self.spellSprites:
    if theSpell.rect.centery > 540:
        if len(self.spellSprites) <= 1:
            LIVES -= 1
            self.loadLives()
            self.shield.reset()
            theSpell.kill()
            self.spellSprites.empty()
            self.spell = Spell(self.shield)
            self.spellSprites.add(self.spell)
            self.itemSprites.empty()
            if LIVES < 0:
                SCORE = 0
                LIVES = 2
                self.showTextScreen('Game Over!', 'Press Escape to Quit or Any Key to Play Again.', 2)
        else:
            theSpell.kill()

I thought this would be sufficient to destroy a ball and make everything work ok. Instead, it would appear that the first ball stays in memory.

 

I came to this conclusion because when there is one ball remaining, and the length of the spellSprites group is equal to 1, occasionally when I obtain a power up to split the balls, the current ball will disappear and a life will be lost as if the ball was out of bounds. It is my belief that the extra balls are spawning off of the primary spell who's location is far below paddle, thus instantly trigerring a loss of life as all balls are lost.

 

The Question

 

Is there a way to permenantly delete a sprite out of memory? If not, is there a way that I can access specific sprite objects within the sprite group when they all share the same name? If that's not possible either, is there some other way I can go about trying to solve this problem that I may have overlooked?

 

If there is any other information or code necessary to provide in order to solve this issue, let me know. Thank you for your time and I greatly appreciate any help you are able to give!

0

Share this post


Link to post
Share on other sites

Edit: I realized everything I said before was based on the assumption spellSprites is a list. It's not. It's a pygame sprite group. Sorry!

 

In any case, check to make sure you're not tucking away any references to these sprite instances anywhere else in your code. If you are, then this could be the source of your leak. As a diagnostic, call gc.collect() after your clean-up method. If the sprites are gone out of memory after a collection, then you could have created a circular reference somewhere between the sprite and some other object. Python uses reference counting to know when to clean up an object, but it also has a garbage collector that runs periodically that can recognize and collect objects lingering only due to circular references.

Edited by smr
2

Share this post


Link to post
Share on other sites

Edit: Removed misleading information. What happened to deleting posts?

Edited by smr
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0