Game Development Community

CH4, Emaga4 problems

by Robby · in Torque Game Engine · 01/03/2007 (10:03 pm) · 5 replies

Ok, I didn't see anything on the first page about this so I decided to post it. I can't figure out what is wrong, I made all the modules, and for some reason it won't run. I re-did the modules 3 times now, and it has mothing to do with the code from what I know of. anyway when I double click on tge.exe it won't run, I really need help, does anyone know what is wrong with the thing? The code is the exact same as in the book, but it won't run. I guess I am going to sleep now and I will be back on 2morrow, hopefully someone will help me. Thank you guys for reading this, please I beg you to respond to this message. :)
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine


Torque Owner Robby
#1
01/12/2007 (3:12 pm)
It, happened to me too. I heard the code in the book from ch4 is messed up, and isn't correct. So I suggest to you you just give up. I can't figure out what is wrong but I have the same problem. sorry I couldn't help. The code in the book is messed up sorry. :(

Torque Owner Surge
MDNAMEDIA
#2
01/12/2007 (5:18 pm)
Suggestion : Move onto something else, and eventually your mind will piece together what was wrong!

Michael Lunday
#3
01/28/2007 (1:18 pm)
Glad to know I am not the only one with this problem.... ;)

One question, are talking the 2nd Edition of the book?

Regards,

Torque Owner Robby
#4
01/28/2007 (7:44 pm)
Reply to Michael Lunday, yes it is the second edition, However I have decided to move away from this book, and today I bought The Game Programmer's Guide To Torque, and let me say things are slowly starting to come together. Thank you for your reply though. :)

jnbutler1815
#5
03/08/2007 (8:43 am)
I had the same problem after typing in all the code from the book (2nd edition). What I had to do to fix the issue was go into task manager and kill the process tge.exe. Then open the console.log file under the emaga4 directory to see what was going on. It wasn't loading the parseargs function and I found I had some typo's from camparing my version of the root main.cs to the one from the cd in RESOURCES/CH4 BOOK CODE. After making the corrections, it progressed further in the startup and I had other issues. These other issues were found by doing a search in the console.log on the word "error", which revealed other typo's that I had made while creating the other modules.
So I would suggest instead of just looking at the console.log output to search on different words like "error", "missing", "missing file", "syntax error", and any other word you can think may denote a problem.
This worked for me and I was able to get Emaga4 running after solving all the errors. It's called debugging, and you will do a lot of it during your programming career, whatever the industry! You think ch4 was a bugger, wait till ch5! muhahaha! Even more debugging!
Enjoy!