Page 1 of 1

GRAPHICS ENGINE ERROR

Posted: Tue Jun 26, 2007 1:02 pm
by josh1861
Hello,

i get an error:

failed to initialise graphics engine. Try and run UFO:ET with parameter "/safe"

what can i do to make it work??

RE: GRAPHICS ENGINE ERROR

Posted: Tue Jul 17, 2007 10:07 pm
by Hanal
Well you posted this some time ago so perhaps you got the game running, but this problem started happening to me when I was playing the end game.....No matter how many times I clicked play, the same error message you had popped up....my solution, I opened another game, in this case Commander Europe at War, and once the game loaded, I exited.  I then was able to open UFO without any problems.  It worked every time and it was as if some aspect of my graphics card needed to be jump started, by opening CEAW, before it could cope with UFO...go figure........

RE: GRAPHICS ENGINE ERROR

Posted: Fri Jul 20, 2007 6:54 am
by chappai
I don't know if you were receiving this error for the same reason I was. I had just purchased a new LCD Flat Panel display and the game absolutely hated the monitor. The resolution I had set for the previous monitor was apparently causing the error that prompted the "/safe" parameter message. Since support dragged their butts in offering a solution, I ended up seeking out help elsewhere online and found this website: http://www.widescreengamingforum.com/wi ... /Main_Page

They deal in solutions for playing a wide variety of games that may not have any support for widescreen.

They offered a most simple solution. The safe meesage appears to come up because the game does not like starting in the resolution you have the game set at.

Their fix is simple. Scrap the "/safe" command that the game is asking you to use.

Go into the game data folder and find the file DATA/ufo-et.ini and then edit the height and width parameters to a lower resolution OR if you are in fact using a widescreen monitor edit the resolution to the default resolution the screen runs best at and then resave the file. Restart the game and the "/safe" message should go away. Worked like a charm for me.

Let me know if this helps.