Game Development Community

Chapter 4 Video issue

by Micheal Hollemon · in Torque Game Engine · 01/25/2005 (3:55 pm) · 2 replies

OK I installed emaga4 via the install file, created all the modules saveed them where they belong, but when I launch the tge.exe I get the dos like window and then a window which the graphics are all messed up. I uninstalled and reinstalled the demo. I updated my video card drivers still no luck. I checked the log file and their are no errors.....


Has anyone else had this problem? can any one help?

Thanks in advance
micheal

About the author

Recent Threads


#1
02/05/2005 (1:41 pm)
Happens all the time. Well, in Emaga there is no place to input options, but in other TGE games like real wars you can press Ctrl O and then decrease the bit depth or change the graphics driver.
#2
02/05/2005 (1:54 pm)
Assuming that there are no errors in your typewritten modules, then run the emaga4 installer again (do not uninstall). You want to re-install it directly over top of the installation you were working with. It won't affect your typewritten modules. Then run tge.exe. If it messes up again, let it sit there for at least a minute. Then hit escape to exit (or kill the task) and relaunch. It should go after the re-install. At worst, after the second launch.

The problem seems to surface with some video card/mobo cominations, and seems to be related to the Torque video autodetection capabilities.

------------------------------------------

If the above still doesn't work for you, do this (read it all before doing it):

Procedure:
1) copy the RESOURCES\CH4 folder from the cd to the hard drive.
2) rename the HD version of the CH4 folder to "C:\Emaga4TEST"
3) run the Emaga4 installer (doesn't matter if you run it from the HD or from the CD), ensuring that it installs to "C:\Emaga4TEST" .
4) run the game by double clicking on tge.exe.

*** NOTE: In this procedure, make sure you ARE NOT installing over top of your already existing working folder. If you already have a folder named "C:\Emaga4TEST" that you had created yourself earlier, then use a different name for the procedure, like "C:\Chapter4TEST" or something, and then follow steps 1 to 4.

This will work, and if your version still doesn't, it points to an error somewhere in your typed scripts.