Game Development Community

Cheers

by Dave D · in Torque Game Engine · 12/21/2004 (12:21 pm) · 7 replies

I just convinced my wife to let me spend time working on a Torque game, and spend the money to buy it. Although I will have to eat mac and cheese and bologna for a month. So far this has been wonderful. I just have a few questions that I couldn't find in the docs. BTW I dumped MS for Debian Linux some time ago.

1.) Kdevelop documentation that I found for what ever reason is not corresponding with Kdevelop that I am using. I assume that is is for an older release or I just can't read.

2.) When I downloaded the demo to try it out, I had awsome framerates. Now that I purchased it and compiled, I get terrible framerates. I would assume that I just didn't compile it properly.

Any ideas would be helpful.
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine


Torque Owner FruitBatInShades
#1
12/21/2004 (12:23 pm)
The framerate drop is most likely if you've compiled a debug build. When any project is compiled as debug there is a lot more code and loops added to allow the debugger to trace all the variables and processes in the compiled exe.

Torque Owner Sikosis
#2
12/21/2004 (12:44 pm)
>have to eat mac and cheese and bologna for a month

a relatively small price to pay I'd say ;)

Torque Owner Dave D
#3
12/21/2004 (3:14 pm)
Bits of bologna IN the mac in cheese is well worth it.

Torque 3D Owner Stephen Zepp
#4
12/21/2004 (3:40 pm)
I would hesitate to say that a debug build should make you go from "awesome" to "terrible" in frame rate. Even as loose as those terms are, unless you really have a ton of things going on, that's probably not quite the issue.

Does the demo still perform excellently, and your own compiled build work poorly on the same machine, same configuration? Most of the time, I've found that poor frame rates imply OpenGL driver issues with your video card. Unfortunately, video card driver makers tend to not debug OpenGL stuff at all before they release a driver version, and in many cases if you fall back one driver version from the "latest and greatest", it works well.

Alternatively, if you haven't updated your drivers since World War II, then you probably want to upgrade to a more recent version (again, not neccessarily the latest one).

Torque Owner Dave D
#5
12/21/2004 (5:35 pm)
I actually updated the drivers yesterday for another issue that I was having. All the other games, Enemy Terrotory, Unreal, and Tux racer all work great. I aslo thought as you that it was a driver issue. I will reinstall the drivers in a little bit.
After moving over from VC6, I am in the process of trying different IDE's to get started in. KDevelop is what I would like to use, but I can't figure out how to set everything up yet.
I think once I get settled down into a comfortable enviroment that things will run smoother.
Btw thanks for the input.

Torque 3D Owner Stephen Zepp
#6
12/21/2004 (6:05 pm)
Yeah, if you just updated your drivers, I would imagine you grabbed the latest available. Historically for me at least, across 2 OS's and 3 boxes (WinXPx2, Win98), I have never gotten the "latest" drivers to work properly for any nvidia cards (Geforce 5600,6800, and a Radeon 5700 in there as well).

Try falling back one revision level in the drivers and see how things go.

Torque Owner Dave D
#7
12/25/2004 (4:13 pm)
I did reinstall the Nvidia drivers and it ran fine. I think it's linda wierd that nothing else seem affected, just the Torque related stuff. As I said, I played Enemy Territory and Unreal just fine. Thanks for you input.