[Spartan-126]

I was playing the 2nd mission and when I got to the asteroid station and delta 1 first said something, my game just froze up. I played it again and when command says the admiral in the asteroid station is a decoy it happened again. Both times i was frustrated so I flipped the computer switch. Can someone help?

P.S: I didn't use any mods

[Jeff Vader]

Run a 3.6.10 debug build. When the game crashes, quit. Find fs2_open.log from \freespace2\data\. Post it here as an attachment or using the "code" tags.

[Spartan-126]

Run a 3.6.10 debug build

I have 3.6.9. Is that bad?

[FUBAR-BDHR]

No 3.6.9 isn't bad it's just 3.6.10 gives better info on crashes. 

[Jeff Vader]

On second thought, run the 3.6.9 debug. There is one thing that it can reveal, which 3.6.10's cannot.

[Spartan-126]

Yea well, I did it but I got past that part without problems, but when a delta fighter said the asteroid is breaking apart, suddenly my game froze up. 10 seconds later...my comp restarted. I'm very sad right now.

P.S: I think what is happening is caused by the game loading up certain things and somehow causing the game to freeze up.

[Jeff Vader]

Is there an fs2_open.log in \freespace2\data\? If yes, please reveal it to us. If not, download the Recommended build for Windows users from my signature, extract the contents (with 7-Zip) to \freespace2\, then run fs2_open_3_6_10.exe until it crashes, then post the log here.

[karajorma]

On second thought, run the 3.6.9 debug. There is one thing that it can reveal, which 3.6.10's cannot.

There is?

[Jeff Vader]

On second thought, run the 3.6.9 debug. There is one thing that it can reveal, which 3.6.10's cannot.

There is?

I currently have the impression that 3.6.10's forcefully select OpenGL. Which is why 3.6.10 debugs also state that the player is using OpenGL. If the player, however, uses Direct3D, 3.6.9 blurts it out.

If I'm completely off my ass here, do correct me.

[Spartan-126]

ok its an attachment





[attachment deleted by ninja]

[Jeff Vader]

Code: [Select]

Initializing Direct3D graphics device at 1024x768 with 32-bit color...
  Direct3D Adapter        : Intel(R) 82845G/GL Graphics Controller
  Direct3D Driver Version : 6.13.1.3119

Ha! I Knew it.

Update your graphics drivers from the Intel website. Then try switching to OpenGL from the Launcher's Video tab.

No wait. Damn. I thought that model sounded familiar. The latest, and last, drivers for that particular model date back to 2005 and they don't support OpenGL properly. If possible, buy a new graphics card.

[Spartan-126]

um...I can't. I don't have enough cash.

well now I'm 

wait I don't use OpenGL

[pecenipicek]

well, you have to. get a better card. save up a bit and get an inexpensive one. you can get a decent for under $70 if you're smart about it, even lower.

[Jeff Vader]

wait I don't use OpenGL

And that's (most likely) the problem. Direct3D is highly unsupported. In 3.6.9 it still "works", but 3.6.10 builds already forcefully select OpenGL, because it's easier for the coders to work with.

The only real option here is to do some hardware upgrading. If it is not possible... well, as they say: life sucks and then you ****in' die.