Game not Starting

#1 Looks like part of your problem is this:

Loading compiled script Game/main.cs.
setModPaths: invalid mod path directory name: 'Game'

Seems to me that both your Main and Creator files are not being compiled. Or they might be but with errors.

Those tend to tie in with the gui stuff. I'd probably look at your directory structure and make sure everything is pointing to the proper place. Thats where I would start anyway. Another thing, it looks like you modded the 1.4 version to have an ammo counter and probably some other mods. Make sure that you made any engine changes to the 1.5 version. That could cause a hang-up too. Could probably tell you more if I could see the whole log....but that gets to be a bit large. Good luck!

#2 Looks like part of your problem is this:

setModPaths: invalid mod path directory name: 'Game'

Seems to me that both your Main and Creator files are not being compiled. Those tend to tie in with the gui stuff. I'd probably look at your directory structure and make sure everything is pointing to the proper place. Thats where I would start anyway.

#3 I've changed from Game, to stonehenge.fps, and it's not telling me setModPaths: invalid mod path directory name: 'stonehenge.fps', so I assume that's good. Besides the invalid mod path, the only thing that changed was in the bottom of the log: "Activating DirectInput..."

Also, I haven't modded the engine (yet), and teh ammo counter is purely scripting. Everytime the player shoots and/or picks up ammo, I have the scripts get total inventory for ammo, and update the gui to suit.

#4 Ok, I tried using the starter.fps and using some files from there. It worked for a little while, but it's not now... Here's the latest console.log with trace inabled.



Edit --> The Mission now loads, but in a couple of seconds the application will tell me that it has encoutered a problem and needs to shut down. I'm thinking that I might not has a good enough computer, but the only problem with that is the fact that all the demos for Torque 1.5.2 work. I've reuploaded the console.log.

#5 Well I took a look at the log. I do not see anything in there that would cause your game to error out like you are saying it does. I used to run into a similar problem awhile ago and it turned out that I had to update my video driver to overcome it. Granted I am using a HEAVILY modified torque engine but it might just be something like that. Especially if its a windows message and not a torque message. Judging by your basic machine specs (listed at the top of the log) you should be able to run this without any problems. Are you using a GeForce video card? If so....update the driver to the latest one. I know that helped me.

#6 Yeah, I've been messing around with it some, and I've come to a similar conclusion: that my graphics card isn't good enough. I didn't thing about the driver though, I'll try it.