Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


Engine performance optimization


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
4 replies to this topic

#1 MefistoManna   Members   -  Reputation: 139

Like
0Likes
Like

Posted 12 June 2012 - 01:25 PM

What kind of things can I do and what can't I do for earn any FPS?
Sorry for my bad English and thanks you.

Sponsor:

#2 Such1   Members   -  Reputation: 435

Like
2Likes
Like

Posted 12 June 2012 - 02:21 PM

Reduce the number of calls to drawing functions, grouping everything that has the same texture in one vertex/index buffer is one way to do it.
Organize the drawing order in a way you draw the close object first.(that way you will reduce the number of times you alter a pixel)
Limit the number of faces drawed, these one depends alot on your app.
Those are the main stuff you can do, of course there are a lot of more things you can do that I don't remember right now.

#3 Tordin   Members   -  Reputation: 604

Like
1Likes
Like

Posted 13 June 2012 - 04:49 AM

Coding both efficent and optimized on the GPU and CPU side. Arranging memory acces and waitstates.

And as such1 said, Organizing materials, rendercalls and more.
This is probably the hardest thing to just tell you "how to do", it´s more of an experiance thing. you just know how to optimize at the current situation!

But try to read some GPU architecture and some CPU architecture, those two things helps alot to understand how to optimize in a good & efficent way.
And remember to not optimze everything, only where it´s needed.
"There will be major features. none to be thought of yet"

#4 Hodgman   Moderators   -  Reputation: 31920

Like
2Likes
Like

Posted 13 June 2012 - 04:57 AM

First, get a profiler and/or use PIX to find out which parts are slow.

#5 MefistoManna   Members   -  Reputation: 139

Like
1Likes
Like

Posted 13 June 2012 - 01:29 PM

Thanks, you were very helpful. I will do more experience and I will understand how to do progressively.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS