Serious Help Needed Cannot run TorgueDemo.exe

#1 If you have access to any other computers in your vicinity, go try on them. To me this sounds like some hardware or O/S and/or driver issues rather than anything with Torque.

Worst case, send me the binary file over at staff@innercircledev.net and I'll take a look at it. Make sure it's the DEBUG build, and compress it..

Or maybe this is an common issue that I've missed. Someone else might be able to help you.

#2 Hey Steven,

What does your console.log say? That's the first place you should turn to if Torque does something unexpected. What are your computer specs?

Marrion

#3 I've had the same thing in the past and I have no clue why. I have a GeForce 3 Ti 200, Win XP Pro, and my guess is there's something wrong with the newest NVidia drivers.

I get the same problem when using GLUT programs, although both with GLUT programs and with Torque, if I wait long enough (sometimes upwards of 10 minutes) then the program starts as usual. Sometimes restarting my computer fixes this problem, other times it doesn't.

There's nothing in console.log that stands out as being especially "wrong."

#4 Got the newest drivers here and on one of our test systems and they work. Could you elaborate on that a bit, please?

#5 I was only *guessing* that there's something wrong with the newest NVidia drivers. Perhaps the problem is only specific to my video card & OS or something else strange.

My problem is identical to Steven's--I run the program and the console window pops up with only a blinking carat. After a while (last time I tried it was only about 20 seconds, but this "while" varies quite a bit), the main application window pops up and from then on everything runs exactly as normal.

#6 Sounds like a problem within the Profile code.. at least to me.
Could you send me the binary (DEBUG preferebly) to my address above? I'd like to take a look if it fails on my system too or if it's system specific.

#7 I sent the file to Stefan.

I recall whenever I had a driver problem with a game before I always atleast got a flash of some kind.

If I let the console run it just sits there no change.

I would also like to add that I am new to programming. Been dabbling for about 2 years. One year seriously.

Stefan was the first person I ever sent a zip file to.

#8 It runs fine on three of our computers here, with the standard demo from 1.3.

Looks like there is something wrong with your system or the configuration :/
OR there is something wrong within Torque and it's profiler.

Does all other games run fine?
What about the standard downloadable demo from GG?

Edit: Steven.. does the console log say anything at all? I mean, just anything? Does it show your CPU and what GFX you're running?

#9 I am updating my drivers now.

Got a phone modem so it will take awhile before I can see if anything happens.

#10 While I am downloading Stefan you are saying the the exe I sent you is running fine. Is this correct.

#11 I downloaded the drivers and still have the same problem.

I deleted the torgue demo exe and built it again and it is still the same.

I did a search for console.log file and found a file. Please remember that I am not an expert in this area. I have never had to get a console.log file
I did a search with the C:\Torque\SDK\example\torqueDemo_DEBUG.exe running and got a message saying I had no access because it was being used. I closed it and searched again and got this file. It might be the wrong one.

//-------------------------- 11/17/2004 -- 15:44:54 -----
Processor Init:
Intel Pentium III, ~1.00 Ghz
(timed at roughly 996 Mhz)
FPU detected
MMX detected
SSE detected

Math Init:
Installing Standard C extensions
Installing Assembly extensions
Installing FPU extensions
Installing MMX extensions
Installing SSE extensions

Input Init:
keyboard0 input device created.
mouse0 input device created.
DirectInput enabled.

--------- Loading MODS ---------
Loading compiled script starter.fps/main.cs.
Loading compiled script common/main.cs.
Missing file: common/defaults.cs!
Loading compiled script starter.fps/client/defaults.cs.
Loading compiled script starter.fps/server/defaults.cs.
Missing file: starter.fps/client/prefs.cs!
Missing file: starter.fps/server/prefs.cs!

--------- Parsing Arguments ---------

--------- Initializing MOD: Common ---------
Loading compiled script common/client/canvas.cs.
Loading compiled script common/client/audio.cs.

--------- Initializing MOD: FPS Starter Kit ---------
Loading compiled script starter.fps/client/init.cs.
Loading compiled script starter.fps/server/init.cs.
Loading compiled script starter.fps/data/init.cs.
Loading compiled script starter.fps/data/terrains/grassland/propertyMap.cs.
Missing file: starter.fps/data/terrains/scorched/propertyMap.cs!

--------- Initializing MOD: FPS Starter Kit: Server ---------
Loading compiled script common/server/audio.cs.
Loading compiled script common/server/server.cs.
Loading compiled script common/server/message.cs.
Loading compiled script common/server/commands.cs.
Loading compiled script common/server/missionInfo.cs.
Loading compiled script common/server/missionLoad.cs.
Loading compiled script common/server/missionDownload.cs.
Loading compiled script common/server/clientConnection.cs.
Loading compiled script common/server/kickban.cs.
Loading compiled script common/server/game.cs.
Loading compiled script starter.fps/server/scripts/commands.cs.
Loading compiled script starter.fps/server/scripts/centerPrint.cs.
Loading compiled script starter.fps/server/scripts/game.cs.

#12 Stefan I am so sorry for getting you so involved with this problem. Thank somebody that Mike has the same problem too. That meaning that I am not the only one with this problem, meaning it is a problem.
I don't wish Mike any trouble either.
I am so tired at this point I put some of the console.log that was there. Tell me if it is the wrong one. I don't no if it was part of the demo, torgue engine demo, or the demo.exe I sent you.

Thanks for taking the time out of your day
to be kind.

#13 Haha, it's alright. Don't worry. I'm interested in this as well, you know.
Hopefully someone else will come in and help soon though because I'm not sure I understand why the error occurs.

It's the correct file, for sure. Hmm, are you sure this is the clean demo?
Have you tried to download the one from GG as I suggested before?

You can get it from here. (Assuming that you're running Windows)

If you can do this, then we can rule out that changes have been made to your demo that could make it behave in this way. I don't know if it's something GG haven't bothered to "fix" yet but it seems the prefs.cs files are not generated at the first startup.

It could be that these were deleted somehow and the game can't get the proper settings for rendering, which makes it not open the window.

That could be the reason why it's not continuing from the console window.
But please try the normal demo and get back here with your result and we can go from there.

#14 @Stefan: Looks like he either didn't give the entire console file (he says "put some of the console file"), or it crashed there (which is very wierd).

FYI, I've found that the "latest" nvidia drivers are actually very unstable with Torque on my Win98SE SP2 box--specifically the virtual display that is used with a (windows) console driven app. I downgraded one level to 56.64 for my GeForce 5600 Ultra, and haven't gotten a blue screen of death (or registry corruption either, come to think of it) since.

It may make sense to try downgrading your drivers if worst comes to worst.

#15 One of the bigest problems running torque for the first time is that the in game resilution is higher (more then likely, equal to)then your desk top, all you get is the console thing,

default torque is 800x600 , set your desk top higher then that and you should be fine

#16 Didn't think of that Ace, good point.

Stephen, Windows98SE - bleh.. that's ages back :) Do people really play games on that O/S anymore?

I don't think it's odd, what you're describing. Most drivers are not meant for Windows 98 anymore, at least not Nvidias. ;)

#17 My desktop is at 1024x768 and my Torque is at 600x800 and I'm still having problems.

I downloaded the clean demo and it still took 5 or 10 seconds longer than it should have. As I said, sometimes things run at a normal speed, and sometimes the application idles in the console window for a while. What is especially strange is that when the program is running strangely, my CPU usage is very low (5% or less) and I cannot hear the CPU working. Whereas when things are running normally, I can hear the CPU chugging away, and the main application window pops up almost immediately after the console window pops up.

BTW, the GG community rocks :) I've had this problem for 2 or 3 months (roughly since I last upgraded my video drivers) and I'm glad to see it getting discussed.

#18 I hope you're saying 800x600, and not 600x800 :)

Ah, that's because you can't hear the CPU work. You can hear the HDD work though, and that's probably the swapfile.

Anyway, if the game DOES start after 5 to 10 seconds, then I don't think what anyone says here can fix it. It could be your computer that's messy, or terribly slow.. Especially if it's random, as you describe it. I'm almost certain that's the case.

Have you checked for Malware, general crap and viruses? This is exactly how my system behaves when something is wrong.

Steven Bodo: Is this how your problem is, as well?

#19 Oh my...I *did* say 600x800.

I'm not too concerned about the time it takes the main app window to open, but I figure it couldn't hurt to ask. I agree that 5 to 10 seconds isn't long to wait, but sometimes the wait is 5 to 10 minutes, which is no good.

I've tried to clean my computer of Malware, crap, viruses, etc. but I'm sure I didn't get all of them.

#20 The thread was too long for the console.log to fit in one post but he is seeing a problem with just that part of it.

I downloaded 1.3 from the link I was sent after I paid for it. It's not the same as the link you put up Stefan. I guess I will try that one. I'll do that now.