[Spidey-]

Okay, So I've finally got a new laptop, my old one's 7900GS was idling at 95-105
Now I've got myself a spiffy new G73 (though I wanted to wait for a desktop).
Anyways to the point. I did a fresh install, patched to 1.2, installed OpenAL (in the x86 folder) and did a fresh install using FSOinstaller-->3.6.10, 5.5e
FS2 vanilla opens fine, but it crashes when I try to start fs2_open from launcher (no features on, no mods)-->i get a 'Freespace 2 has stopped working, windows is checking...blah blah'
I've run in compatability for 98 and xp, OpenGL and D3D8, and the debugger.
Am I missing something obvious? Because no one else seems to have problems like this with Win7

[General Battuta]

Try 3.6.12 RC3. Post a debug log.

[The E]

Also, have you installed OpenAL?

[haloboy100]

installed OpenAL

Did you restart after installing? I always have seemingly random crashes like that that are fixed after a quick reboot. They always happen after installing something. I am using Windows 7 also.

[Jeff Vader]

installed OpenAL (in the x86 folder)

Uh, this raises suspicions that you either got your OpenAL from a weird source or did something wrong with it. Installing OpenAL should consist of
- downloading the OpenAL installer from the OpenAL site
- running the OpenAL installer and clicking "Next" or "Yes" once or twice.

If it involved actually placing files to folders, you did something wrong.

[haloboy100]

I think he means he installed openAL to the program files (x86) folder in windows 7, which is applicable if you are using 64-bit windows 7 (like me). He was probably just making things overcomplicated by saying that.

[The E]

Which would still be wrong, because OpenAL installs itself to system32.

All it leaves in Program files is a copy of the installer.

[Spidey-]

sorry, yeah I installed OpenAL properly was all I was trying to say
here's the error log, oddly enough 3.6.12 doesn't generate an errorlog



[attachment deleted by admin]

[General Battuta]

sorry, yeah I installed OpenAL properly was all I was trying to say
here's the error log, oddly enough 3.6.12 doesn't generate an errorlog

Could we get a debug log? You'll need to run a 3.6.12 debug build to generate one.

[Iss Mneur]

sorry, yeah I installed OpenAL properly was all I was trying to say
here's the error log, oddly enough 3.6.12 doesn't generate an errorlog

What was in the error log should now appear in the Application Log of the Event Viewer.

Also, FSO 3.6.10 and 3.6.12 does not, and has never required any compatibility settings (other than the HKLM thing, but that is not controllable by the user anyway).  So, also make sure that you have not left any of the compatibility settings on.

[Spidey-]

weird, before I rand the debug, it didn't get to the point where it showed a log, then it id once, now I can't get it again


Warning: ships.tbl(line 146:
Warning: Unable to find [Terran] in species names list.

File: PARSELO.CPP
Line: 668


Call stack:
------------------------------------------------------------------
    fred2_open_3_6_10_debug.exe 005249f6()
    fred2_open_3_6_10_debug.exe 00524b6c()
    fred2_open_3_6_10_debug.exe 0053b0e7()
    fred2_open_3_6_10_debug.exe 0053ab0d()
    fred2_open_3_6_10_debug.exe 0054071c()
    fred2_open_3_6_10_debug.exe 00540c3e()
    fred2_open_3_6_10_debug.exe 0045962e()
    fred2_open_3_6_10_debug.exe 0045948d()
    fred2_open_3_6_10_debug.exe 00434f32()
    fred2_open_3_6_10_debug.exe 00435065()
    fred2_open_3_6_10_debug.exe 009e3e67()
    fred2_open_3_6_10_debug.exe 00433345()
    fred2_open_3_6_10_debug.exe 009e23aa()
    fred2_open_3_6_10_debug.exe 00a0091a()
    fred2_open_3_6_10_debug.exe 009f43aa()
------------------------------------------------------------------

[General Battuta]

Could you go into your data folder and post the fs2open log file from there, please? What you posted is not the debug log, just a warning.

[Jeff Vader]

weird, before I rand the debug, it didn't get to the point where it showed a log, then it id once, now I can't get it again

When you run a debug build, it writes the fs2_open.log INTO A FILE called "fs2_open.log". It really does that. The game engine doesn't even need to start that much before the writing begins. That file resides in \freespace2\data\ . We would like that file. And,

NOTE FOR PEOPLE USING WINDOWS VISTA OR 7:
If you installed FS2 to C:\Program Files\ (or C:\Program Files (x86)\ on 64-bit versions of Windows), the log file will not be in FS2\data\, but rather in a "virtualized" folder. This can be found by either going to the data folder, and clicking on the "Compatibility Files" button in the Explorer window, or by manually navigating to C:\Users\<Your Username>\AppData\Local\VirtualStore\Program Files (x86)\<Rest of the path to your FS2 directory>\data

[Spidey-]

oh okay, I didn't know that's what debug log refers to


[attachment deleted by admin]

[Jeff Vader]

I gotta admit. When some people talk about debug logs and the instructions talk about fs2_open.logs, it can get a bit confusing. Anyways,

Code: [Select]

... OpenAL successfully initialized!
Initializing OpenGL graphics device at 1920x1080 with 32-bit color...
  Initializing WGL...
something horrible happens at this point. And it is related to OpenGL. Which is related to your graphics card and its drivers in the end. So, if you don't have any proper GPU driver installed, install it. If you do have some GPU driver installed, find the newest one, uninstall the current one, and install the new one.

Incidentally, some nitpicking.

I've run in compatability for 98 and xp, OpenGL and D3D8, and the debugger.

As it was said, compatibility modes are not needed with FSO.
Any builds after 3.6.9 will use OpenGL, regardless of what you select in the Launcher.
The debugger is a tool for programmers. A tool which you most likely do not have installed. Nor do you need it. You were probably referring to a debug build. And debug builds are a very different thing.

Edit: I'm not sure if this happened but I'll say it just in case: When we talk about running a debug build, it doesn't mean that you should just double-click the debug .exe. You should select the debug build with the Launcher, as you did with the regular build. That way we'll also see what features and mods you have active.

[chief1983]

Actually Vader, won't running the exe directly use the last set launcher settings in cmdline_fso.cfg or whatever?  You only need to run the launcher if you want to change those I thought.

[The E]

You can, but personally I like to think of that as an option for advanced users.

[Spidey-]

Which is related to your graphics card and its drivers in the end. So, if you don't have any proper GPU driver installed, install it. If you do have some GPU driver installed, find the newest one, uninstall the current one, and install the new one.

So these are the G73 Specs,
i7 720QM
Windows Home Pre. 64bit
8Gb DDR3-1066
ATI Mobility HD5870 (equiv 5770)

Last driver released by Asus is CCC 9.12 (driver 8.683)

As it was said, compatibility modes are not needed with FSO.
Any builds after 3.6.9 will use OpenGL, regardless of what you select in the Launcher.
The debugger is a tool for programmers. A tool which you most likely do not have installed. Nor do you need it. You were probably referring to a debug build. And debug builds are a very different thing.

Thanks for clarifying

Edit: I'm not sure if this happened but I'll say it just in case: When we talk about running a debug build, it doesn't mean that you should just double-click the debug .exe. You should select the debug build with the Launcher, as you did with the regular build. That way we'll also see what features and mods you have active.

That's right, as I said before I'm running launcher with all features off and no mods.

So is there anything else I can do besides wait for asus to release a new driver? (I've tried a vBIOS sol'n for standard CCC10.6 off notebookreview but it didn't really work)

[Jeff Vader]

So is there anything else I can do besides wait for asus to release a new driver? (I've tried a vBIOS sol'n for standard CCC10.6 off notebookreview but it didn't really work)

Well, the only thing I can think of is to uninstall your GPU drivers and then reinstall them. And if that fails...