Game Development Community

Discovering Leaks

by rennie moffat · in iTorque 2D · 04/16/2011 (8:41 am) · 4 replies

Edit:
I found the reason for my games slow performance. I had forgotten that with enough objects on screen and Collision Bounds in view, that that can slow the game down quite a bit. Feel free, if you have tips, for looking leaks to leave some. I have not yet gotten into the XCode tools, but perhaps this thread can help. Regardless, thank you.

/////
HI there I have a general question on programming. If, for some reason, my game has slowed down quite a bit and I am unsure why. Are there tools that will/can help find this "leak" or whatever it might be? I am looking for tips beyond going over the scripts? Are the tools in XCode the best bet?

I am just looking for other ways to help optimise games, discover "leaks", areas of drag.



Thanks in advance.



rennie moffat's profile picture
Torque Owner rennie moffat
Renman3000

About the author

My thanks to Garage Games and the Garage Games Community combined with owned determination I got one game up, Temple Racer and I am looking to build more interesting, fun games for the mass market of the iOS app store.

Recent Threads

  • is it just me or is onPositionTarget sketchy?
  • Ben Kenobi
  • Installing Box2D Today
  • An Unknown Error Has Occured
  • object reading others behavior?
    • NextNext Thread
    PrevPrevious Thread
    More from iTorque 2D


    Torque 3D Owner Marc Dreamora Schaerer
    Gayasoft
    #1
    04/16/2011 (2:46 pm)
    XCode offers various instruments, including memory instruments to instrument object creation and destructions as well as leaks.

    Just use them while debugging on the device and you should be able to find out where it leaks.

    As first step though I would use the static analyzer (its one of the build options in xcode 3.2.x, unsure where its hidden on xcode 4) which will tell you where you generally basing just on code flow, are potentially leaking objects

    Torque Owner rennie moffat
    Renman3000
    #2
    04/16/2011 (5:04 pm)
    Great. Thanks Marc.

    Employee Michael Perry
    ZombieShortbus
    #3
    04/17/2011 (9:19 am)
    I second Marc's suggestion. The first stop is using Xcode's built-in tools.

    Quote:As first step though I would use the static analyzer (its one of the build options in xcode 3.2.x, unsure where its hidden on xcode 4)
    They made it part of the build options. When you click and hold down on the Run button (looks like a play symbol), you can switch to Analyze. When you run using the Analyze scheme, it will run the static analyzer stuff.

    Torque Owner rennie moffat
    Renman3000
    #4
    04/19/2011 (8:04 am)
    Thanks for the reply Mike. I did a test on it, just to check it out. Seems it is posting "notes" on the engine. Things not so related, in fact, nothing I have written. So, as a result I wouldn't know what to ask. If in the future, it posts things related to my scripts I may have a clearer understanding of what it is saying.

    Is there anything I should expect? Use it when (x situation)? etc?



    Cheers
    Ren