Game crash on startup

[Ann!b@l]

Press Windows key+R and type eventvwr.msc.. And see if you can gather more infos linked at these ET crashes.

Edited October 9, 2016 by Ann!b@l

[Symfony]

Also, what the deuce is ET Legacy? o.o

It's a project that helps make ET run better on newer machines. http://etlegacy.com

Edited October 9, 2016 by Symfony

[Anton Chigurh]

What resolution you are trying to run?

[-=HipKat=-]

With console, I assume you mean the in-game console. I don't get that far into the game before the crash occurs, so I cannot provide you with that.

Not sure how the print-screen will help, it literally says "ET no longer works. We're looking for a solution."

 

Also, what the deuce is ET Legacy? o.o

I knew I had this before. Try this...

 

http://fearless-assassins.com/topic/75996-et-hangs-at-startup/

[Flible]

your dutch ? nevermind you are

 

probeer dit even zorg sowieso dat ET als administrator draait en kijk even in taakbeheer wat er gebeurd 

overbelasting of  iets dat niet hoort te draaien

ik moet even nadenken ik heb iets soort gelijks gehad maar kan even niet opkomen waarom ook al weer

 

 

translation try to make sure ET runs as admin look in taskmanager what happens if you open overload or something running that shouldnt I had a simular error im trying to remind myself why it was again I thought it had something to do with my video card I thought I  had to update drivers

Dat ik als admin run moge duidelijk zijn lol. Task Manager geeft een enorme piek op geheugen die direct na een succesvolle launch weer daalt. Als het ooit succesvol is >.<

[DFighter]

Dat ik als admin run moge duidelijk zijn lol. Task Manager geeft een enorme piek op geheugen die direct na een succesvolle launch weer daalt. Als het ooit succesvol is >.<

is je pc overbelast ? als dat zo is en je heb windows 10 stop defender process dat neemt enorm veel geheugen in beslag maar verklaard de crash niet ik had het omdat bij video kaart drivers niet goed waren

[RedBaird]

Every time that ET starts, it creates a file called "etconsole.log" in your etmain folder.  It might have clues to the problem at the end of the file.  It may show what ET was trying to do when it choked.

 

The next time you start ET and it crashes, rename that etconsole.log file to etCrash.log to preserve it.  Each time ET starts, it overwrites the old Log file.

 

 

BTW, you can't open that file while ET is running, but you can make a copy of it and open the copy.  

[Flible]

Every time that ET starts, it creates a file called "etconsole.log" in your etmain folder.  It might have clues to the problem at the end of the file.  It may show what ET was trying to do when it choked.

 

The next time you start ET and it crashes, rename that etconsole.log file to etCrash.log to preserve it.  Each time ET starts, it overwrites the old Log file.

 

 

BTW, you can't open that file while ET is running, but you can make a copy of it and open the copy.  

Seems to be no such file in my folder o.o

[RedBaird]

Seems to be no such file in my folder o.o

 

That is another clue.

[-=HipKat=-]

DId you read the thread I linked to above?

[Flible]

DId you read the thread I linked to above?

 

I did. It's suggesting to completely remove all ET files and pathways manually and to reinstall it. I've already tried this one-size-fits-all solution ^^. I don't feel my crash is because of a file corruption or missing file.

[RedBaird]

Press Windows key+R and type eventvwr.msc.. And see if you can gather more infos linked at these ET crashes.

 

 

I put the first few lines of my etconsole.log into the spoiler.  It starts working with openGL and the graphics rendering commands.

 

Your ET might not be getting that far along before it crashes, so you had best follow Annibal's advice.  

 

 

logfile opened on Mon Oct 10 18:56:56 2016

 

...detecting CPU, found Intel Pentium III

Bypassing CD checks

----- Client Initialization -----

----- Initializing Renderer ----

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

----- Client Initialization Complete -----

----- R_Init -----

Initializing OpenGL subsystem

...initializing QGL

...calling LoadLibrary( 'C:\WINDOWS\system32\opengl32.dll' ): succeeded

...setting mode 6: 1024 768 FS

...using desktop display depth of 32

...calling CDS: ok

...registered window class

...created [email protected],0 (1024x768)

Initializing OpenGL driver

...getting DC: succeeded

...GLW_ChoosePFD( 32, 24, 0 )

...215 PFDs found

...hardware acceleration found

 

 

 

I am not sure if the program caches these lines before writing them.

 

BTW, I once had trouble with Silent mod until I removed the hunkusage.dat file and let the mod create a new one.  I could not see any corruption in it, but Silent Did Not Like It At All!

 

Did you run FA's PK3-cleaner?  I don't see how it would help, but it certainly won't hurt.  

Edited October 11, 2016 by RedBaird
BTW