[Triglph]

Hi there, fraid I'm new to both freepace and freespace open but was very excited to try out a game and mod that's clearly got such a strong community around it.

Unfortunately I keep hitting a brick wall on the training mission   - whenever I click commit the game freezes, sound goes and the picture stays exactly how it is, most often I have to reboot my computer. Strange thing is that I can access the tech room and have a look at the lovely ship designs there without a problem. I've been looking through the forum and tried several different things:

I've tried running it in windowed and with the openal disabled. I used the installer and heard that it might be unreliable when it comes to the mediavp files so I downloaded those again with the patch and replaced them but with no such luck. I've got an intel graphics card which apparently has some issues with opengl so I tried running it in Direct3D but the freeze was the same. I've run the freespace 2 exe with no hitchs but when I run the freespace open even without the media vps i get the freeze.

My specs are: Windows XP, Intel Core Duo CPU 2.00 GHz with 2 GB of RAM and my graphics card is a Mobile Intel 965 Express Chipset Family, and I'm running this on a laptop.

I've attatched the datalog, hope it helps, thanks in advance guys.

[attachment deleted by admin]

[General Battuta]

Without even looking at the log I'm going to bet you have post-processing enabled.

EDIT: Or not! 3.6.10.

By the way, excellent help request. Very helpful, debug log and all.

Have you tried a 3.6.12 build?

[FUBAR-BDHR]

Nope he doesn't.

There are some flags on that probably shouldn't be but nothing that should cause that issue.  My suggestion would be to turn on run in window under dev tools and see if you are getting a popup in the background that is taking focus away from the game. 

[The E]

Triglph: Can you try the 3.6.12 RC1 build and see if the issue appears there as well? If it does, please post the log from that builds debug version.

Oh, and BTW: There is no Direct3D mode in the engine. Although the Launcher has a little setting for switching between D3D and OGL, the game will start in OGL mode regardless. This is not a bug, but indeed a feature.

[Triglph]

Without even looking at the log I'm going to bet you have post-processing enabled.

EDIT: Or not! 3.6.10.

By the way, excellent help request. Very helpful, debug log and all.

Have you tried a 3.6.12 build?

Thanks! Hadn't realised that a new build had come out - is the download link the same as the old one?

Will try the running it in a window to check for a pop-up as well and get back to you

[Jeff Vader]

ith the openal disabled.

Uh, could you clarify? OpenAL is a sound API which you must have installed on your computer, and OpenGL is used and required by FSO. You can't really disable it.

I used the installer and heard that it might be unreliable when it comes to the mediavp files so I downloaded those again with the patch and replaced them but with no such luck.

My understanding is that the Installer should get working MediaVPs now. But props for taking the initiative.

I've got an intel graphics card which apparently has some issues with opengl so I tried running it in Direct3D but the freeze was the same.

FSO builds after 3.6.9 do not use Direct3D at all. Even if you selected it from the Launcher, the game engine would still use OpenGL.

I've attatched the datalog, hope it helps, thanks in advance guys.

Thank you for that.

Hadn't realised that a new build had come out - is the download link the same as the old one?

Do what The E said. Get 3.6.12 RC1 behind the link he posted. New FSO builds keep popping up all the time.

[The E]

Thanks! Hadn't realised that a new build had come out - is the download link the same as the old one?

No. Get it here: http://www.hard-light.net/forums/index.php?topic=68190.0

[Triglph]

ith the openal disabled.

Uh, could you clarify? OpenAL is a sound API which you must have installed on your computer, and OpenGL is used and required by FSO. You can't really disable it.

Sorry I meant openGL, recommended from a rather old thread to be disabled in the tagline, only ran it windowed now I think about it since I couldn't find a disabling option in the devtools section.

[Triglph]

Right...fraid the error was the same - computer needed restarting. Got the devlog right here:

[attachment deleted by admin]

[General Battuta]

Man.  I'm worried your video card may just not be potent enough.

[The E]

Yeah, you should definitely get rid of mv_advanced. However, in theory, it does have all the features needed for FSO to work; I'm really scratching my head on this one.

Triglph: Please create an empty file in FS2\data, and call it debug_filter.cfg. Run the debug build, and then post that log. It's going to be huge, so you may have to zip it up before attaching.

[Triglph]

Yeah, you should definitely get rid of mv_advanced. However, in theory, it does have all the features needed for FSO to work; I'm really scratching my head on this one.

Triglph: Please create an empty file in FS2\data, and call it debug_filter.cfg. Run the debug build, and then post that log. It's going to be huge, so you may have to zip it up before attaching.

Yeah I know it's a rather weak graphics card so thanks for the heads up on the mv_advanced...but I've never encountered an error like this before when using it, mighty odd! I made the .cfg file and ran the debug but the file only seems to be 1 kb big but will upload anyway:

[attachment deleted by admin]

[The E]

Errm. I meant you should create that file, run the debug build, and then post the fs2_open.log....

[Triglph]

Errm. I meant you should create that file, run the debug build, and then post the fs2_open.log....

Ahhh...sorry about that - here's the log, thanks for this:

[attachment deleted by admin]

[Herra Tohtori]

Right...fraid the error was the same - computer needed restarting.

To avoid restart, run with -window or -fullscreen_window. These options are found in the "Dev Tool" list of features in the Launcher.

Looking at the long log, it doesn't immediately seem to tell what goes wrong. In fact it ends in a slightly perplexing way:

Code: [Select]

Entering game at time = 248.871
Player lethality: -0.2, num turrets targeting player: 0
Player lethality: -0.4, num turrets targeting player: 0
Player lethality: -0.6, num turrets targeting player: 0
Player lethality: -0.8, num turrets targeting player: 0
Player lethality: -1.0, num turrets targeting player: 0

...and it ends right there. The mission load seems to work normally, so I'm a bit stumped as to what could be causing a hang-up. It's even a dual core system so it shouldn't take all processing power either.

Give it a try with the windowed mode(s). Also, do other missions work normally? You could test from the Tech Room (press Ctrl+Shift+S and all campaign missions appear for testing). If you can run other missions, then it could be just something strange with this mission.

[Triglph]

Right...fraid the error was the same - computer needed restarting.

To avoid restart, run with -window or -fullscreen_window. These options are found in the "Dev Tool" list of features in the Launcher.

Looking at the long log, it doesn't immediately seem to tell what goes wrong. In fact it ends in a slightly perplexing way:

Code: [Select]

Entering game at time = 248.871
Player lethality: -0.2, num turrets targeting player: 0
Player lethality: -0.4, num turrets targeting player: 0
Player lethality: -0.6, num turrets targeting player: 0
Player lethality: -0.8, num turrets targeting player: 0
Player lethality: -1.0, num turrets targeting player: 0

...and it ends right there. The mission load seems to work normally, so I'm a bit stumped as to what could be causing a hang-up. It's even a dual core system so it shouldn't take all processing power either.

Give it a try with the windowed mode(s). Also, do other missions work normally? You could test from the Tech Room (press Ctrl+Shift+S and all campaign missions appear for testing). If you can run other missions, then it could be just something strange with this mission.

I've tried it with windowed mode and the freeze still happens, though thanks for this since now I'm not restarting my computer each time. The freeze is very sudden, no warning sounds or error messages and happens the instance I click the commit button. Fraid that it happens on other missions as well and the FSport mod even when windowed.   

[Herra Tohtori]

Does any other OpenGL application cause your computer to freeze like that?

[Triglph]

Does any other OpenGL application cause your computer to freeze like that?

I'm uncertain what other opengl applications I use - I'm pretty sure I've not encountered an error like this before on this computer though and while the graphics card can be troublesome to some games it seems fine with the basic freespace 2.

Just a thought - I had the Descent: Freespace demo on the computer before I downloaded freespace 2 off GOG and modded it. Is there anyway this could have interferred?

[The E]

Nope.

[General Battuta]

Just to be sure, it hangs even with the MediaVPs disabled and all graphical command line flags turned off?