Game Development Community

Frame Rates Stock RTS vs 1.52

by Swaroop Reddy · in RTS Starter Kit · 01/07/2008 (8:50 pm) · 11 replies

Has any one noticed that there is a considerable drop in frame rate with the 1.52 RTS conversion. I have tested using OpenGl and D3D. There is a 30% drop in frame rate with OpenGl and over 40% drop in frrame rate with D3D. Is it worth the conversion?

#1
01/07/2008 (11:46 pm)
Well I think TGE 1.5.2 has a lot of fixes for memory leaks, compared to the stock RTS-SK. I know this because I'm currently going through finding and fixing them with the stock RTS-SK.

That's a big drop in frame rate though, wonder why?
#2
01/08/2008 (3:30 am)
Is that with just a stock update Swaroop?

Geom, perhaps you can share with us what you're doing and we'll include it in the next update to the patch.
#3
01/08/2008 (6:31 am)
I think Geom is working with the stock kit, am I right Geom?

Sounds like a big drop indeed. I'll check the general forums and see if this is common from TGE 1.3 to 1.5
#4
01/08/2008 (6:56 am)
Sorry about the confusion guys. The drop in frame rate is about 10 frames per sec. I tested on 3 different pcs. If the frame rate is 30 it drops to 20 with 1.52. If it is 90 it drops to 80 with 1.52. I was using the stock RTS kit debug. The rate limiting step for my project is the frame rate.

James by stock RTS I mean the only "downloadlable / Purchaseable" RTS kit from GG.

Geom I am really interested in your fixes for memory leaks. If the issue is only for memory leaks would a dif bet the the stock RTS and 1.52 conversion not show where we need to make changes to fix the memory leaks. I am in a bit of a dilemna now as to which way to proceed.

I will do one more comparison test on my fastest PC and start with 100 units in both. I will post the resuts in a few minutes.
#5
01/08/2008 (7:12 am)
Swaroop, its important wich executables are you comparing. You will have torqueDemo.exe and torqueDemo_DEBUG.exe, wich is slower (and much larger).

When comparing realeses, in fact, Im getting a much better frame rate with the 1.5.2: about the same percentage, but in favour of the last port.
#6
01/08/2008 (10:37 am)
Yep, I'm still on the TGE 1.3 / stock RTS-SK code base.

Ok, I'll post the mem leak fixes I've applied...looking back at my list there's actually only 3 or 4 of them. Funny how it seems like there's a million, when you're actually fixing them :)

But memory leaks are just a small part of the picture, I imagine Torque 1.5.2. has a *lot* of bug fixes besides memory leaks, compared to 1.3. If I was starting a new project today, I'd try to use the latest version of Torque if at all possible, personally.

I'm just kind of wedded to the 1.3 code base at this point because of all the changes I've made to it, that's the only reason I'm still on the old version.

Edit: cleaned up my tortured English..
#7
01/08/2008 (11:14 am)
Indeed. If you Swaroop have not done much engine code changes, the wiser patch would be to upgrade the codebase. There is not only the HUGE changes between TGE 1.3 and 1.5 (like the incorporation of the Lighting Pack), but also the TDN port includes bugfixes for the RTS Kit.

Anyway, if the doubt is about a frame rate drop, forget it, the 1.5 runs better. Im almost sure you are comparing the wrong files.
#8
01/08/2008 (11:21 am)
Quote:
like the incorporation of the Lighting Pack

That almost certainly is why there is a frame rate difference between 1.3.x and 1.5.2x right there. More powerful/flexible lights are going to give at least a small rendering performance hit.
#9
01/08/2008 (6:45 pm)
Hey James,
I posted my list of memory leak fixes over here, hope they're useful!
#10
01/08/2008 (8:00 pm)
Geom
Thanks. You are most kind.

Novak
I retested using both release versions and debug versions. No change in my results. 1.52 is slightly slower. After looking at all the feed back, I will proceed with using 1.5.2. Thanks for your advice and help.
#11
01/08/2008 (9:14 pm)
That's excellent Geom. If you don't mind, I'll post it over on the RTS TDN page when I get chance this week. I'll let you know when it's done so you can check it for accuracy.

Again, excellent and thanks :)