[Ghost]

My household recently acquired a much better computer than what was used previously. Allow me to list my specs, so you can share in my baffled-ness:

AMD Athlon 64 X2 Dual Core processor 4200+, at 2.22 ghz, 2 gig of RAM
Video card: nVidia Geforce 7900 GT

Now onto the problem. For installing FS2, what I did was I used the old 3.6.5 installer package to get everything needed for the actual program. Then, I upgraded the launcher, build, and VP files to 5.3 and 3.6.7, respectively. I have a couple other build exes, but... we'll get to that.

Okay, so I opened the launcher, selected the official 3.6.7 exe, fiddled with my options a bit, etc... and hit run. Game starts, start a new pilot, hit 'select,' main hall. Everything's dandy for about half a second. Then... either it locks up(not sure about it, since the music is still playing), or it's just taking a really long time to get to the next frame.

Sometimes it locks up, sometimes it'll get moving at the rate of about .1 frames per second.

Attempting with a more recent build won't start the game at all.

[CP5670]

hmm, I would have expected a newer build to do the trick. 3.6.7 is ancient these days and doesn't contain the dual core fix, but it's in everything after last November or so. This sounds like a dual core problem though, so you could try setting the affinity manually in the task manager and see if that helps.

[Ghost]

hmm, I would have expected a newer build to do the trick. 3.6.7 is ancient these days and doesn't contain the dual core fix, but it's in everything after last November or so. This sounds like a dual core problem though, so you could try setting the affinity manually in the task manager and see if that helps.

You mean the 3.6.7 build? I've tried a build by Karajorma, I believe, from mid-May. Which won't start the game at all.

If you meant the VPs, I have no idea which ones are latest. There's all this beta and zeta **** that should get cleaned up.

EDIT: Well, the affinity thing fixed it... sort of. It'll now run on the 3.6.7 official build. The other one won't start.

EDIT2: put in the 3.6.8 Zeta VPs from the thread in the upgrade forum. Now 3.6.7 build will start, but crashes with a few errors. Other builds still refuse to start.

[karajorma]

Firstly your installation method is a little baffling. There is no good reason for running the 3.6.5 installer. The fact that it's over a year old and has never been updated since should have been a clue to that


If you're trying to use 3.6.7 with 3.6.8 VPs you are similarly wasting your time. You should never run with newer VPs than the build you're using. That's simply asking for trouble as there is no way to ensure that a build can be forward compatible with the data that will be used by later builds.

Get yourself 3.6.9 RC 7.

[Ghost]

Firstly your installation method is a little baffling. There is no good reason for running the 3.6.5 installer. The fact that it's over a year old and has never been updated since should have been a clue to that


If you're trying to use 3.6.7 with 3.6.8 VPs you are similarly wasting your time. You should never run with newer VPs than the build you're using. That's simply asking for trouble as there is no way to ensure that a build can be forward compatible with the data that will be used by later builds.

Get yourself 3.6.9 RC 7.

I install that way because it's a good way to build upon for me. Otherwise I always think I forget something.

Also, like I said, new builds refuse to even start.

[karajorma]

Problem is that I have no idea what you have installed any more.

Follow the instructions here on how to clean out an old install of FS2_Open.

Then follow this guide on how to install 3.6.9 RC 7

[Nuke]

all builds should be capable of running with vanilla vp files. the ones that originally came with the game. id advise cleaning out the old media vps (not the originals), and try the builds in reverse-order untill one works, then install the appropriate media vps for it.

also you might want to consider running a debug build. then you can give the coders some debugging information and perhaps the problem will be fixed on future builds.

[Ghost]

Karajorma: What I did just now was uninstall FS2, and deleted the folder with everything in it. I then reinstalled FS2, patched it, and followed your instructions to the letter. I appreciate you being patient with someone as impatient as myself.

It still does not work. After putting OpenAL on my computer and running it, now the launcher, for some reason, won't start.

[karajorma]

Okay. At least we're getting somewhere now.

Delete your errorlog.txt file. Then attempt to run the debug build of RC 7 from the launcher. Give me the first 10 lines of your errorlog.txt file and the first 20 or so of your fs2.log file (along with the last 10 of the same file).

If you get any error pop up other than the standard windows needs to close this program paste the text in here too.

[Ghost]

When I run the debug exe, a small window with scrolling text pops up for about half a second, then disappears. No errorlog file is created.

Running the regular exe doesn't work, obviously, and creates an errorlog:

fs2_open_3_6_9 caused an Access Violation in module ntdll.dll at 001b:7c911f52.
Exception handler called in FreeSpace 2 Main Thread.
Error occurred at 9/17/2006 14:34:34.
J:\Freespace2\fs2_open_3_6_9.exe, run by Unknown.
2 processor(s), type 586.
2048 MBytes physical memory.
Read from location fffffffd caused an access violation.

Where's the fs2.log file located?

[karajorma]

It should be appearing in the same folder as the errorlog.txt (i.e  your main one).

Go into the launcher and post your command line for me (That will be the stuff in the greyed out box on the features tab. You can cut and paste it here).

[Ghost]

There's no fs2.log file there.

Also, if you didn't see what I said, the launcher isn't working either anymore.

[karajorma]

Delete the launcher6.ini and the flags.lch file and try it again.

[Ghost]

Will do when I get access to that computer again. I'll edit this post when I try that.

EDIT: Launcher opened, no command line set. First attempt will be the debug build... I hit run, 'debug spew' window popped up for maybe 2 seconds, then disappeared. Game fails to run.

New errorlog:

fs2_open_3_6_9 caused an Access Violation in module ntdll.dll at 001b:7c911f52.
Exception handler called in FreeSpace 2 Main Thread.
Error occurred at 9/17/2006 14:34:34.
J:\Freespace2\fs2_open_3_6_9.exe, run by Unknown.
2 processor(s), type 586.
2048 MBytes physical memory.
Read from location fffffffd caused an access violation.

Registers:
EAX=001401b0 CS=001b EIP=7c911f52 EFLGS=00010293
EBX=00140000 SS=0023 ESP=0012e2d8 EBP=0012e4f8
ECX=7ffde000 DS=0023 ESI=fffffff8 FS=003b
EDX=00140608 ES=0023 EDI=00000007 GS=0000

There's a boatload more stuff in there, too.

I'm still not seeing an fs2.log file.

EDIT2: Here's my command line: J:\Freespace2\fs2_open_3_6_9_debug.exe -spec -glow -env -jpgtga -mipmap -nomotiondebris -2d_poof -missile_lighting -dualscanlines -targetinfo -orbradar -rearm_timer -ballistic_gauge -ship_choice_3d -3dwarp -warp_flash -snd_preload -fps

[Bobboau]

OGL or D3D?

ten bucks on you useing D3D, wich is going to be broken till after the next release.

[Polpolion]

Firstly your installation method is a little baffling. There is no good reason for running the 3.6.5 installer. The fact that it's over a year old and has never been updated since should have been a clue to that

I remember 3.6.5

I used to try and run that with my old comp, no media VPs, I was like "wTf? These graphics are orgasmic!!!!" and then it froze, and I was like "NOOO!!!!!"

Now with my new comp I'm using 3.6.9 RC6 with all the Zeta VPs, and I'm like "Yeah, I guess these graphics are pretty good."

[Ghost]

OGL or D3D?

ten bucks on you useing D3D, wich is going to be broken till after the next release.

Looks like you owe me 10 bucks, then, haha.

[WMCoolmon]

Looks like you owe me 10 bucks, then, haha.

I have a new way of earning HLP money.

*Turns to the less-than-30 posts crowd*

Soo....who here wants to bet that there's gonna be a Freespace 3?

[Trivial Psychic]

I'm still not seeing an fs2.log file.

Actually, its called "fs.log", and a debug build should be generating one evey time its fired up.  The best way to find it is to first, run the debug build.  Then, open up your freespace2 folder in Explorer, make sure you have the option to view file extensions enabled, then tell the program to organize them by date modified.  FS.log should be one of the most, if not THE most recently edited file, and should be right at the top (or bottom, depending on whether you've got it set oldest-to-newest, or newest-to-oldest).

[Ghost]

I'm still not seeing an fs2.log file.

Actually, its called "fs.log", and a debug build should be generating one evey time its fired up.  The best way to find it is to first, run the debug build.  Then, open up your freespace2 folder in Explorer, make sure you have the option to view file extensions enabled, then tell the program to organize them by date modified.  FS.log should be one of the most, if not THE most recently edited file, and should be right at the top (or bottom, depending on whether you've got it set oldest-to-newest, or newest-to-oldest).

Okay, thanks. I've got to get to school at the moment; I'll look for it again when I get home.

EDIT: Found 'fs.log'

==========================================================================
DEBUG SPEW: No debug_filter.cfg found, so only general, error, and warning
categories can be shown and no debug_filter.cfg info will be saved.
==========================================================================
Passed cmdline options:
  -2d_poof
  -env
  -jpgtga
  -mipmap
  -missile_lighting
  -glow
  -nomotiondebris
  -spec
  -3dwarp
  -ship_choice_3d
  -warp_flash
  -snd_preload
  -mod mediavp
Building file index...
Searching root 'J:\freespace2\mediavp\'
Searching root pack 'J:\freespace2\mediavp\mp-710_adveffects.vp'
Searching root pack 'J:\freespace2\mediavp\mp-710_effects.vp'
Searching root pack 'J:\freespace2\mediavp\mp-710_models.vp'
Searching root pack 'J:\freespace2\mediavp\mv_core.vp'
Searching root pack 'J:\freespace2\mediavp\mv_effects.vp'
Searching root pack 'J:\freespace2\mediavp\mv_models.vp'
Searching root pack 'J:\freespace2\mediavp\mv_music.vp'
Searching root pack 'J:\freespace2\mediavp\mv_textures.vp'
Searching root 'J:\freespace2\'
Searching root pack 'J:\freespace2\mv_core.vp'
Searching root pack 'J:\freespace2\root_fs2.vp'
Searching root pack 'J:\freespace2\smarty_fs2.vp'
Searching root pack 'J:\freespace2\sparky_fs2.vp'
Searching root pack 'J:\freespace2\sparky_hi_fs2.vp'
Searching root pack 'J:\freespace2\stu_fs2.vp'
Searching root pack 'J:\freespace2\tango1_fs2.vp'
Searching root pack 'J:\freespace2\tango2_fs2.vp'
Searching root pack 'J:\freespace2\tango3_fs2.vp'
Searching root pack 'J:\freespace2\warble_fs2.vp'
Searching root 'f:\'
Found 21 roots and 11882 files.
AutoLang: Language auto-detection successful...
Setting language to English
Initializing OpenAL...
  Using 'Generic Software' as OpenAL sound device...

EDIT2: I should also tell you that I repeatedly have to delete my launcher's ini file as well as the flags file to get the launcher to work. Meaning every time I close the launcher, I have to do that whole thing each time to get it to work.