Hard Light Productions Forums

Hosted Projects - Standalone => Wing Commander Saga => Topic started by: Tolwyn on January 07, 2007, 01:57:47 pm

Title: Troubleshooting Guide
Post by: Tolwyn on January 07, 2007, 01:57:47 pm
Trying to track down and resolve technical problems on your computer is, undeniably, one of life's most frustrating experiences. To help you through the process, I've compiled a list of common problems users experienced with Wing Commander Saga Prologue so far.

No Sound

There is something wrong with your OpenAL install.  Check X:\Windows\system32 for ct_oal.dll and nvopenal.dll. (X stand for your system partition). If you find them, delete them. Then install OpenAL 1.1

If that doesn't work, copy the openal32.dll and wrap_oal.dll files from their system32 directory directly into the game directory. 

Launcher/Game fails to start

This is most likely related to the No Sound issue.

Low framerate in missions Demo01-Demo03

Try installing Asteroid Field Performance Fix.

Error: Could not load WarpMap01 anim file!

Try updating your GPU drivers. Make sure you run the game in OpenGL mode.

Error: Could not load in ChoosePilot-m!

640x480 and 800x600 resolutions are not supported. Most systems should be able to have decent performance on the default resolution setting.
Title: Re: Troubleshooting Guide
Post by: Alffallen on January 08, 2007, 03:46:20 pm
Hello,

I've been trying to install the prologue. Though I allways get the following error after downloading and trying to run the setup. "Error reading setup instalization file". I've tried downloading from diffrent mirrors thinking It was a corrupted download.

Any ideas?
Title: Re: Troubleshooting Guide
Post by: Tolwyn on January 08, 2007, 03:54:23 pm
Try updating Windows Installer.
Title: Re: Troubleshooting Guide (Joystick Problem)
Post by: Sennanio on January 22, 2007, 02:27:15 am
Hello there,

well, this is my first post and I hope I wont get slaped right away. I searched the forum but I didn't quite find a solution fitting to my problem.
So, I hope you may be able to help me out. (Excuse me for my pitiful english ... )

The systems I use are a MacBook Pro and a Mac Pro and I use the Saitek Cyborg EVO (USB) joystick. Binding the keys and axises of the joystick works just fine and the keys work within the game, too. But the default steering direction is always to the left (even if I don't touch the joystick).
Same problem on both machines (MacOSX 10.4.5 and 10.4.8 )

I learned from this forum the windows version has some kind of launcher with an option to calibrate the joystick and so I tend to ask if there is an "hidden" option to calibrate the joystick within the mac os x version, too ?

Did I just miss it ?

I also tried to use third-party tools like the game companion or the usb overdrive x which both resulted in an unoperational joystick (neither steering nor buttons)...

Maybe someone finds some time to see to it ...

thx in advance

S.

PS: Oh, I forgot to mention : The joystick is alright - it works just fine with other progs and the old originals in parallels desktop ;-) !

Title: Re: Troubleshooting Guide
Post by: Mongoose on January 22, 2007, 03:47:21 am
I have that same stick myself, and I've experienced the same thing before.  Have you tried moving the stick fully left/right/up/down?  That should activate the auto-calibration and get it to stop drifting.
Title: Re: Troubleshooting Guide
Post by: karajorma on January 22, 2007, 07:28:20 am
The calibrate option in the launcher simply takes you to the Windows control panel. It's not doing thing particularly FS2_Open related.
Title: Re: Troubleshooting Guide
Post by: Sennanio on January 22, 2007, 12:37:55 pm

Well, how embarrassing - I didn't know about an auto-calibration feature but it worked out the way you predicted.

Thanx a lot ... I really appreciate your help !
Title: Re: Troubleshooting Guide
Post by: Mongoose on January 22, 2007, 03:55:55 pm
No problem. :) I wouldn't have known about it myself if I hadn't come across it in the manual while installing the stick.
Title: Re: Troubleshooting Guide
Post by: marcus28 on February 01, 2007, 04:53:15 pm
Just installed this and I'm dead excited as I love the Wing Commander games. I'm running tis on a Mac Pro with a 512MB Graphics Card with 3Gb RAM (yeah I know, show off). Anyway the in game graphics are pants. The Nebulas all look like mismatched squares and don't seem to join. the passing stars look like sugar cubes. The large ships all look jagged.....whats going on?!?! What have I done??

 :eek2:
Title: Re: Troubleshooting Guide
Post by: Tolwyn on February 01, 2007, 05:05:33 pm
I can't tell you, as I have very little mac experience :(

You could ask here (http://www.hard-light.net/forums/index.php/board,113.0.html) though.
Title: Re: Troubleshooting Guide
Post by: venom30 on February 07, 2007, 10:08:26 am

Quote
No Sound



If that doesn't work, copy the openal32.dll and wrap_oal.dll files from their system32 directory directly into the game directory.

already tried that but it didnt help. and when i start the game (after it finishes with loading. the screen flackers and i can t see anything accept collers and stripes
Title: Re: Troubleshooting Guide
Post by: karajorma on February 07, 2007, 04:15:24 pm
What are your system specs Venom30?
Title: Re: Troubleshooting Guide
Post by: venom30 on February 07, 2007, 11:45:35 pm
athlon 2200+
512mb ram
ati radeon 9200 128mb
Title: Re: Troubleshooting Guide
Post by: Tolwyn on February 08, 2007, 01:35:25 am
and the sound card? Mainboard?
Title: Re: Troubleshooting Guide
Post by: venom30 on February 08, 2007, 01:39:06 am
sound ist onboard ,yes
Title: Re: Troubleshooting Guide
Post by: karajorma on February 08, 2007, 04:28:51 am
Are you running in D3D mode or OpenGL? Run the launcher.exe program and go to the video tab if you don't know.
Title: Re: Troubleshooting Guide
Post by: Akalabeth Angel on April 06, 2007, 08:55:55 pm
    Hey, another problem. My computer has a tendency to freeze up and crash at certain points. Notably, in the fourth campaign mission (kilrathi), it freezes when as Alpha flight approaches the Wellington Nav point. And sometimes during the simulator missions, it will crash as well. Playing the torpedo run mission, it crashed when I was bearing towards a freighter 2000m away that exploded. Since it has a tendency to crash when ships explode and I'm looking at them, I'm guessing it means my computer can't hack it. I have a new computer but the video card is just the one which came with the computer, I can play a game like Doom3 but other games complain my video card sucks and won't run (ie Dawn of War). Except for the crashing I don't have any other performance issues (no lag or anything).

   
Title: Re: Troubleshooting Guide
Post by: tk-cologne on April 08, 2007, 08:14:59 am
Hi, i can't install the prologue. The setup doesn't react anymore after trying to extract a file (.msi?), so i have to stop the setup in the taskmanager. I tried this with firewall antivir off, had the same result.
PC is Athlon2000+, AtiX700 256MB, 768MB Ram, WinXP, Soundonboard

Any ideas?
 
Regards from Tom Cologne/Germany
Title: Re: Troubleshooting Guide
Post by: Tolwyn on April 08, 2007, 08:24:55 am
Give the setup routine some time. It takes several minutes to extract the msi package from the exe file.
Title: Re: Troubleshooting Guide
Post by: Aginor on April 08, 2007, 08:35:02 am
Jep, give it a LONG time. I started it three times before I realized that it takes that long.... :rolleyes:

-Aginor
Title: Re: Troubleshooting Guide
Post by: tk-cologne on April 08, 2007, 06:53:38 pm
Thanks for the help, i had to wait for about 20 minutes. Installation and starting the game worked without problems.

Unfortunatly now the game crashes very often. It appeared in the transport escort mission for the first time. The error log shows an access violation. Don't know what this means.

wcsaga caused an Access Violation in module atioglxx.dll at 001b:6914f966.
Exception handler called in FreeSpace 2 Main Thread.
Error occurred at 4/9/2007 01:04:16.
C:\Programme\Wing Commander Saga Prologue\wcsaga.exe, run by xxx.
1 processor(s), type 586.
768 MBytes physical memory.
Read from location 00000000 caused an access violation.

Registers:
EAX=00000000 CS=001b EIP=6914f966 EFLGS=00010282
EBX=03d0d000 SS=0023 ESP=0012f870 EBP=03d0d000
ECX=00000003 DS=0023 ESI=03d580b8 FS=003b
EDX=00000000 ES=0023 EDI=03d57f78 GS=0000
Bytes at CS:EIP:
8b 10 b4 00 00 74 1b 8d 96 f8 26 00 00 52 8d 86
Stack dump: ..........................

Is this about my graphic card, at first i thought it was a sound problem, cause the sound was kind of hanging/repeating? RAM Testing showed no errors.

Tom
Title: Re: Troubleshooting Guide
Post by: gevatter Lars on April 08, 2007, 07:08:39 pm
atioglxx.dll
I would say you got an ATI card? I heard that some ATI drivers have problem with opengl. Maybe that causes a problem.
Title: Re: Troubleshooting Guide
Post by: Wanderer on April 09, 2007, 03:54:17 am
First are you running DirectX, if you are then use the launcher to switch over to OpenGL and try again.. Otherwise...

When does the error appear? On the mission load? During the mission?

Do you have debug build? If you do run it and then search for fs.log or fs2_open.log named files from the FreeSpace direcory and from the data directory. Copy paste the contents as described here (http://www.game-warden.com/forum/showpost.php?p=62785&postcount=11)
Title: Re: Troubleshooting Guide
Post by: tk-cologne on April 09, 2007, 09:51:27 am
There is OpenGl in the video settings and the game crashes/freezes during the missions often with the latest sound effect repeating.
Quote
Do you have debug build? If you do run it and then search for fs.log or fs2_open.log named files from the FreeSpace direcory and from the data directory. Copy paste the contents as described here
I don't know if i have one, the launcher shows no debug build button or something like that?

Quote
I would say you got an ATI card? I heard that some ATI drivers have problem with opengl. Maybe that causes a problem.
Are there other drivers i can use?

PC is Athlon2000+, AtiX700 256MB, 768MB Ram, WinXP, Soundonboard

Thx and regards from Tom
Title: Re: Troubleshooting Guide
Post by: gevatter Lars on April 09, 2007, 10:13:47 am
Since I have an Nvidia I can't tell. I think ATI is also more or less regular releasing updates for their products. Maybe you should visit the ATI homepage and search their for updated drivers.
Title: Re: Troubleshooting Guide
Post by: durandal2006 on April 10, 2007, 07:43:44 pm
it's been a long day/week/month/any and all of the above, so i may just be missing something here, but i get to the first training mission and the framerate slows down instantly and i get weird pops and jumps in the sound.  i disabled the sound to see if that was the problem, but it wasnt.  and i've installed the asteroid performance fix.

any ideas?
Title: Re: Troubleshooting Guide
Post by: Tolwyn on April 11, 2007, 01:47:05 am
I've never heard of such a problem. The best bet would be to post here (http://www.hard-light.net/forums/index.php/board,50.0.html).
Title: Re: Troubleshooting Guide
Post by: tk-cologne on April 11, 2007, 07:11:19 am
Since I have an Nvidia I can't tell. I think ATI is also more or less regular releasing updates for their products. Maybe you should visit the ATI homepage and search their for updated drivers.

Problem found, drivers are ok but when i opened my pc, there was a lot of dust everywhere, too much for my gpu.  :eek2: The gpu was just overheating, now after some cleaning temp. decreased about 10°C.  :rolleyes:

Played the missions, liked them all and i'm looking forward to the full game.  :)

Regards Tom
Title: Re: Troubleshooting Guide
Post by: Tolwyn on April 11, 2007, 07:19:27 am
you should also try the autopilot demo. Althrough the scripts we used there have been updated since, it gives a pretty good idea how the final product will look like :)
Title: Re: Troubleshooting Guide
Post by: durandal2006 on April 11, 2007, 11:04:50 am
I've never heard of such a problem. The best bet would be to post here (http://www.hard-light.net/forums/index.php/board,50.0.html).

ran into the same problem with the beyond the red line demo.  figured it might be the graphics (i'm on a laptop after all) and turned it down to 16-bit.  fixed btrl, tried the same with wcs.  still had the same problem, but i just tested the opening part of the first mission, so it might be due to the fact that it starts you off inside the hanger.  when i get back from class/work i will see if it works once i launch.
Title: Re: Troubleshooting Guide
Post by: benben84 on August 01, 2007, 05:16:32 am
Hey guys, just downloaded WCS but when i get to the pilot create screen and i enter a name it comes up with an error stating that i don't have enough diskspace to create a profile, Retry, Ignore and Quit. I've had quick look around the forum but couldn't find anything to help, you guys know what i should do? Thanks! REALLY looking forward to getting into this ^_^
Title: Re: Troubleshooting Guide
Post by: Tolwyn on August 01, 2007, 05:18:17 am
you will need to create single folder inside the players folder manually. Also check whenever or not thoese two folders are write protected.
Title: Re: Troubleshooting Guide
Post by: Leuthesius on September 06, 2007, 12:33:10 pm
Followed your procedure for sound. Still no sound.
Title: Re: Troubleshooting Guide
Post by: Leuthesius on September 06, 2007, 05:38:49 pm
Ok, it miraculously started working.  :confused:

The game is running great, however the missiles are ridiculously powerful. I went from 100% health, full shields, full armor to dead in one hit after I took out a pirate capship with one. ONE torpedo. What the deuce?
Title: Re: Troubleshooting Guide
Post by: Tolwyn on September 07, 2007, 01:03:25 am
You are either playing at the hard mode or your shields were severely weakened. Even then it is very unlikely that a single missile could score a kill. :)
Title: Re: Troubleshooting Guide
Post by: Boozer on September 10, 2007, 03:41:11 pm
Hi folks,

first of all, thank you very much for keeping Wing Commander alive.

But I got problems with the OpenAL stuff.Though I followed your advices in first post ( copying *.dll files directly in the game directory) I always get the message " OpenAL 1.1 or newer is required for proper ... Please install ... available at ... and try to start the programm again later "
Then the game starts without sound.

I got Onboard sound AC97 (the one from the NForce 2 chipset), does this may cause the problem?

Best regards
Boozer
Title: Re: Troubleshooting Guide
Post by: Tolwyn on September 10, 2007, 03:51:11 pm
shouldn't cause any problems. Have you tried the troubheshooting advice from the first post?
Title: Re: Troubleshooting Guide
Post by: Boozer on September 10, 2007, 03:54:10 pm
Yes, i copied both files
Title: Re: Troubleshooting Guide
Post by: Jeff Vader on September 10, 2007, 04:06:03 pm
You sure that you have OpenAL version 1.1 or newer? If you don't, you can get it from a couple of locations, like openal.org or the Useful stuff for FSO link in my sig.
Title: Re: Troubleshooting Guide
Post by: Boozer on September 10, 2007, 04:59:48 pm
Definitly got OpenAL 1.1 from openal.org
Installer doesn´t need much time, but says installation complete.

And the files are inthe system32 directory ( and in the game directory too )
It´s a bit strange
Title: Re: Troubleshooting Guide
Post by: karajorma on September 11, 2007, 07:34:08 am
Have you set the audio to generic software? The other options are a bit dodgy
Title: Re: Troubleshooting Guide
Post by: Kail on February 03, 2008, 05:48:55 pm
You guys do know that the installer won't continue unless there's enough space on drive C even if you choose to install to another drive that has more than enough...right?
Title: Re: Troubleshooting Guide
Post by: Tolwyn on February 04, 2008, 03:46:08 am
How to resolve Common "Windows Installer" Problems (http://support.microsoft.com/?scid=kb%3Ben-us%3B555175&x=5&y=14)
Title: Re: Troubleshooting Guide
Post by: FekLeyrTarg on April 18, 2009, 04:02:06 pm
I have a weird problem:
When I launch the game, no matter which settings I have in the launcher, the PC reboots. (Luckily, it didn't substain damage)

My PC specifications:
Intel Celeron 2.0 ghz
ATI Radeon 9800 PRO (AGP, 128 mb and Pixel Shader 2.0)
about 700 mb RAM
Creative Labs Audigy
DirectX 9.0c
OpenAL

I don't have Freespace 2.
I've installed WCS on H:\programme\Wing Commander Saga Prologue (it's an external hard drive with a capacity of 1 Terrabyte (1000 Gigabyte btw)
I have the same problem with Beyond the red line. But Imperial Alliance (a Star Wars game based on Freespace 2 developed by the science office of the Emperor's Hammer) works without problems.

Any help would be appreciated. Thanks in advance. :)
Title: Re: Troubleshooting Guide
Post by: The E on April 18, 2009, 04:06:55 pm
Go here (http://www.hard-light.net/forums/index.php/topic,62210.0.html). Download the 3.6.10 RC2 executable, extract and copy it to your WCS directory. Open the Launcher, click the Browse button, and select the regular build. if that doesn't solve it, select the debug version and run that as far as it goes, and then post the FS_open.log file in the \data\ directory here.
Title: Re: Troubleshooting Guide
Post by: FekLeyrTarg on April 18, 2009, 04:25:28 pm
Go here (http://www.hard-light.net/forums/index.php/topic,62210.0.html). Download the 3.6.10 RC2 executable, extract and copy it to your WCS directory. Open the Launcher, click the Browse button, and select the regular build. if that doesn't solve it, select the debug version and run that as far as it goes, and then post the FS_open.log file in the \data\ directory here.

Here you go.
btw I've looked for others with this problem via google ealier this day. No results.

[attachment deleted by evil Tolwyn]
Title: Re: Troubleshooting Guide
Post by: The E on April 18, 2009, 04:29:38 pm
Ummm.....First, you should mark the "Enable features for WCS" checkbox in the Launcher, under Gameplay.
Second, I have absolutely no clue whats going on there, but I believe it's something with your Hardware, rather than FreeSpace. Do you have problems when running other Games, especially ones that are build on OpenGL?
Title: Re: Troubleshooting Guide
Post by: FekLeyrTarg on April 18, 2009, 04:45:41 pm
Ummm.....First, you should mark the "Enable features for WCS" checkbox in the Launcher, under Gameplay.
Second, I have absolutely no clue whats going on there, but I believe it's something with your Hardware, rather than FreeSpace. Do you have problems when running other Games, especially ones that are build on OpenGL?
No, I don't. Exept of Beyond the red line of course.
And I tried it with "toogle features for wcs". It's still the same. As I said above, it doesn't matter how WCS  is configured: My PC reboots when staring either wcs or btrl.
btw here's another log just in case it helps us all.

[attachment deleted by evil Tolwyn]
Title: Re: Troubleshooting Guide
Post by: The E on April 18, 2009, 06:04:00 pm
I still believe that there's a problem with your system, rather than with FS2. When you say "reboot", do you mean a complete BSOD, or a regular reboot?
Title: Re: Troubleshooting Guide
Post by: Jeff Vader on April 19, 2009, 02:02:05 am
I've seen a similar issue with FSO. Your log ends at reading prologue_hud.vp. Chances are that the file is corrupt and is causing this issue. I'd suggest redownloading and reinstalling WCS.
Title: Re: Troubleshooting Guide
Post by: FekLeyrTarg on April 19, 2009, 04:02:16 am
I still believe that there's a problem with your system, rather than with FS2. When you say "reboot", do you mean a complete BSOD, or a regular reboot?
A regular reboot.

I've seen a similar issue with FSO. Your log ends at reading prologue_hud.vp. Chances are that the file is corrupt and is causing this issue. I'd suggest redownloading and reinstalling WCS.
I'll give it a try right away.
If this doesn't work, could someone of you send me your "prologue_hud.vp", please? If redownloading doesn't work, then perhabs replacing that file with the one from someone else. Thanks in advance.

edit: No, it didn't. But I'm trying another approach: Replacing the normal ATI drivers with Omega ones.
edit2: No, it didn't work either. I've also tried both DX8 and OpenGL modes: No success.
Title: Re: Troubleshooting Guide
Post by: Jeff Vader on April 19, 2009, 09:01:48 am
Are your other drivers up to date? At one time I had strange rebooting/crashing issues with games because of old audio drivers.
Title: Re: Troubleshooting Guide
Post by: Tolwyn on April 19, 2009, 11:26:01 am
It has nothing to do with Prologue's data files if you experience issues with Beyond the Red Line as well. This is an engine related issue, probably related to your specific hardware/OS configuration.
Title: Re: Troubleshooting Guide
Post by: FekLeyrTarg on April 19, 2009, 11:49:27 am
Are your other drivers up to date? At one time I had strange rebooting/crashing issues with games because of old audio drivers.
I've tried it with updating my Sound card drivers: No success.

Well, looks like there's nothing I can do anymore but to wait for the next engine build.  That's not fair. :(
But thanks anyways for your support. I still appreciate your efforts to help me solving this problem. :)
I wonder if someone else has this problem.

edit: I think I'll report this to the team behind the fsopen engine.

edit2: I have an idea what caused this: I recently brought my PC to a technician and he told me that the internal HDD and my graphics card are damaged. I got a new HDD but the wrong gpu, an ATI 7000 (I can't play most games with it because of no hardware acceleration). He'll install a Nvidia card on monday (I hope that it'll be a geforce 7900 gs). If this fixes my "wcsaga start => PC reboot" problem, I'll let you know.

edit3: Nope. I've got a nvidia fx5600 now and wcsaga and btrl still don't work.
Title: Re: Troubleshooting Guide
Post by: crimson_05 on July 19, 2009, 07:40:36 am
Firstly, Im a big WC fan and this mod looks fantastic, well done to all involved.

However I do not seem to be able to get through the first mission without a CTD. It always happens at the same spot, when proceeding to the 3rd (or 4th) nav point, the one right after the training fight against the corvette. The game will freeze for a moment, then a windows dialogue box pops up (i.e. Freespace has encountered a problem and need to close) and close it does.

Has anyone else encountered this problem?
Title: Re: Troubleshooting Guide
Post by: The E on July 19, 2009, 07:49:56 am
Hi there. The first thing you should try is downloading this (http://www.hard-light.net/forums/index.php/topic,63492.0.html). It's the latest recommended version of the engine. Get both the 3.6.10RC3 exe and the Launcher. Put both into your WCS directory, start the Launcher, select the 3.6.10RC3 executable, and see if the problem still exists.
If it does, select the debug exe, run it until it crashes, then post the fs2_open.log file in the data\ directory here.
Title: Re: Troubleshooting Guide
Post by: Tolwyn on July 19, 2009, 08:27:38 am
The crash is caused by change-ship-model sexp. If the new exe doesn't solve it for you, I'll upload a modified mission for you.
Title: Re: Troubleshooting Guide
Post by: crimson_05 on July 20, 2009, 01:43:41 am
The new engine version did the trick. Thanks guys  :yes:
Title: Re: Troubleshooting Guide
Post by: FekLeyrTarg on August 07, 2009, 12:25:49 pm
I've played WCS on other PCs and so far I'm impressed. Nice.
But I've noticed something while I was playing the last mission of the 2nd Autopilot demo (the one where you have to destroy the Lexington). I know this isn't exactly the right place to write this but I don't want to open a new topic just for a minor glitch. (if you want me to report such things in separate topics, just tell me)
I don't know if someone noticed it before but the Lexington's  lasers fired right through her bulkheads and hit me while I was fighting her from the inside.

When I'm home again, I'll try to get WCS and BtrL to run on my own PC on which the reboot problem occurs.
Title: Re: Troubleshooting Guide
Post by: Dragon on August 07, 2009, 01:13:11 pm
It is, unfortunately, an issue with FS in general, though not a bug.
A turret can shot throught the ship it's mounted on and it's a standard retail FS behaviour.
In 3.6.10 builds there's a subsystem flag "Check Hull", which prevents such behaviour, but at the time WCS Prologue was made, it wasn't existing.
Final WCS should have this flag on all turrets of all ships and most likely will have.
Title: Re: Troubleshooting Guide
Post by: FekLeyrTarg on August 07, 2009, 01:31:50 pm
It is, unfortunately, an issue with FS in general, though not a bug.
A turret can shot throught the ship it's mounted on and it's a standard retail FS behaviour.
In 3.6.10 builds there's a subsystem flag "Check Hull", which prevents such behaviour, but at the time WCS Prologue was made, it wasn't existing.
Final WCS should have this flag on all turrets of all ships and most likely will have.
Thanks.
I've already downloaded the 3.6.10 rc2 exes and I'll check it out again.
btw sorry for being stupid. I haven't noticed the sentence "Report Wing Commander Saga bugs with Mantis". My apologies.
Title: Re: Troubleshooting Guide
Post by: Dragon on August 07, 2009, 04:00:36 pm
Download 3.6.10 final, not RC2.
And don't forget that build itself won't solve the "issue", you need to make a mod for Prologue that will add "Check Hull" flag to ship turrets to do that.
Also, as I said it's not a bug, engine version provided with Prologue doesn't have "Check Hull" flag.
Title: Re: Troubleshooting Guide
Post by: FekLeyrTarg on September 01, 2009, 08:16:05 am
Good news. The PC restart bug has been fixed by upgrading one of my drivers. It's running fine now.
Title: Re: Troubleshooting Guide
Post by: Krt_Bong on November 24, 2009, 02:51:38 pm
I have an X-52 Saitek Hotas which the game doesn't recognise, any thoughts as to how I can remedy this?
Title: Re: Troubleshooting Guide
Post by: Tolwyn on November 24, 2009, 03:10:08 pm
Try using Force 0/1 settings in the launcher.
Title: Re: Troubleshooting Guide
Post by: Krt_Bong on November 24, 2009, 04:47:36 pm
Try using Force 0/1 settings in the launcher.
Well, I'm not sure what that means exactly but, I did fix it.
I dropped the whole kit and kaboodle into the FreeSpace2 folder and ran it from that launcher where it was no tribble, er, trouble at t'all.
Title: Re: Troubleshooting Guide
Post by: KeldorKatarn on November 25, 2009, 03:13:05 pm
We'll make sure the main game will have an easier to use launcher.
Title: Re: Troubleshooting Guide
Post by: rapierdragon on December 27, 2009, 12:59:14 am
My only problem is with the movies.   Movie audio is fine, but the video (in Direct3d8) is only showing up in the bottom-right 2/3rds of the screen (regardless of the settings I try, be they in the config program or my usual desktop graphics settings).  Once the movie is done the game returns to normal.

In Direct3D8 all other game aspects work 100% fine... menu, flying/combat, etc.  I haven't tried completing the first mission yet to see if the between-mission type bits where you can click on save/load or talk-to-person type screens look okay, so I'm thinking it has something to do maybe with a bad codec, or perhaps a codec splitter is interfering (I have Combined Community Codec Pack on my system for multiple video format playback... I'll have to see if the Haali a/v splitter or something is messing up the video part of the movies).

I'd play in OpenGL but on startup it gives a "cannot create proper pixel opengl w32" or something... and oddly, no matter what video resolution I set for, the screen momentarily goes to 800x600 and back.

So aside from the movies, the game and gameplay are fantastic.
Title: Re: Troubleshooting Guide
Post by: The E on December 27, 2009, 01:04:08 am
 :wtf: What build are you using? Direct3D hasn't worked right in ages......

Please try and download a 3.6.10 build from here (http://www.hard-light.net/forums/index.php?topic=64520.0), select it in the Launcher, and run it. If it still gives you that error, select the debug version (filename ends with a d), run it, then go to the data folder in your WCS directory, and post the fs2_open.log found there here.
Title: Re: Troubleshooting Guide
Post by: rapierdragon on December 27, 2009, 02:40:22 am
kk, here's the log.... btw, same error message as before, but now I also get it if I try to run in direct3d8 too (whereas before d3d8 only had the movies not showing up right... the flying/combat part was 100% fine)


==========================================================================
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.
==========================================================================
FreeSpace version: 3.6.10
Passed cmdline options:
  -ambient_factor 100
  -glow
  -spec
  -cache_bitmaps
  -ship_choice_3d
  -snd_preload
  -wcsaga
Building file index...
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_anims.vp' with a checksum of 0x20ede0b2
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_asteroids.vp' with a checksum of 0xed4efb11
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_core.vp' with a checksum of 0x2c725bc9
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_effects.vp' with a checksum of 0xb0272d7b
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_hud.vp' with a checksum of 0x0a624b02
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_interface.vp' with a checksum of 0x17c4567c
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_music.vp' with a checksum of 0x244979b7
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_ships.vp' with a checksum of 0x4248ea63
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_sounds.vp' with a checksum of 0xda87e6ba
Found root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_voice.vp' with a checksum of 0x3066cebf
Searching root 'E:\Program Files\Wing Commander Saga Prologue\' ... 40 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_anims.vp' ... 3 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_asteroids.vp' ... 21 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_core.vp' ... 60 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_effects.vp' ... 245 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_hud.vp' ... 205 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_interface.vp' ... 1313 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_music.vp' ... 37 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_ships.vp' ... 1167 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_sounds.vp' ... 157 files
Searching root pack 'E:\Program Files\Wing Commander Saga Prologue\prologue_voice.vp' ... 685 files
Found 11 roots and 3933 files.
AutoLang: Language auto-detection successful...
Setting language to English
Initializing OpenAL...
  Using 'Generic Software' as OpenAL sound device...
  OpenAL Vendor     : Creative Labs Inc.
  OpenAL Renderer   : Software
  OpenAL Version    : 1.1

... OpenAL successfully initialized!
Initializing OpenGL graphics device at 1280x960 with 32-bit color...
  Initializing WGL...
ERROR: Unable to initialize display device!

File: gropengl.cpp
Line: 2972
    gr_init_sub()    gr_init()    game_init()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c817077()
Title: Re: Troubleshooting Guide
Post by: The E on December 27, 2009, 02:47:48 am
That's because Direct3D support has been cut from FS2_Open completely. Even if you select it in the Launcher, it will ALWAYS use OpenGL.

Now, this error usually means that your GPU drivers are broken. What card are you using?
Title: Re: Troubleshooting Guide
Post by: rapierdragon on December 27, 2009, 03:02:38 am
asus p4p800-mx motherboard with a 2.6 ghz cpu, 1 gb ram stick (and a 256 ram stick... so guess that writes as 1.256 gb ram?)
for video:
intel video chipset 82865g with latest drivers installed

trying to find what version opengl I have (thinking its 1.1 think I read the game needs 1.2 or higher)
Title: Re: Troubleshooting Guide
Post by: The E on December 27, 2009, 03:13:33 am
The game actually needs 1.4 (Actually, it should work with 1.2, but 1.4 is recommended). And Intel GMAs are basically crap. Any chance you can get a real GPU in there?
Title: Re: Troubleshooting Guide
Post by: rapierdragon on December 27, 2009, 03:19:09 am
WTF?  re-ran their latest-chipset-driver checker program and suddenly its saying my drivers are OLD.  Ran the prog like 10 times in the past 5 hours and it always said that I had version 6.x (2005 date) and was up to date.... but suddenly it said I had 6.x.x but 14.x.x was the latest (and the date was like 2007 for 14.x)

so installed and retested... video working 99.99% fine now (some odd garbage at top and bottom of screen... movie occupies full screen from left to right, but only about the middle 5/7th's top to bottom... bout 1" empty room at top and bottom of monitor... and that 1" has odd-colored garbage)
Title: Re: Troubleshooting Guide
Post by: rapierdragon on December 27, 2009, 04:58:44 am
Is there a save for immediately after the 2nd mission?  Seems the auto-pilot is really jerky and even fairly buggy.

SUGGESTION:  an "AUTO" text should display while in auto-pilot.

Visuals are beautiful.  What little gameplay I've seen has been great.  Audio seems spot-on to the feeling of the background music I remember from actual WC games.  Just the damn buggy auto-pilot.

7 attempts so far and:

3 attempts had the auto-pilot engaged and was in route to nav 1 when transport "suddenly" blows up and I find myself back approaching the carrier (alive) only then it cuts to "you left formation and went against the pirates on your own against the order to stay in formation.  You were one, they were many, your now dead."   :mad:

1 attempt had auto-pilot on route to nav 3 (with like 8k left to the nav-point) when suddenly my ship drops out of auto-pilot (or something) and then suddenly my fighter flips 180 degrees and I can see the transport (moving at like it was still at 64X high-speed autopilot) and then blam, it rams me over and over again (till I'm dead).  I can only guess I was still in auto since I couldn't stear or use afterburner to get out of its way.

2 attempts got as far as nav 3 then, just short of where auto-pilot should turn off, without warning I'm dead (and it gives the "you left formation" blaw blaw message.

1 attempt got 3 pirates killed within the first few moments, few minutes later there only was ONE pirate left with the transport at like 12% health and clearly the pirate isn't in missile range of it when, just like 1/2 second after the pirate explodes, suddenly blam, the transport vanishes (no explosion) and I get the "you failed to protect the transport" ...  :confused:
Title: Re: Troubleshooting Guide
Post by: KeldorKatarn on December 27, 2009, 09:12:03 am
What build are you using for this? This sounds very strange, I've never heard anything like this happen before.
Title: Re: Troubleshooting Guide
Post by: Tolwyn on January 04, 2010, 06:06:57 am
Please use, if possible, the EXE supplied with the game.
Title: Re: Troubleshooting Guide
Post by: bombush on September 01, 2010, 07:13:04 am
Definitly got OpenAL 1.1 from openal.org
Installer doesn´t need much time, but says installation complete.

And the files are inthe system32 directory ( and in the game directory too )
It´s a bit strange

If everything else fails (and it did on my XP SP3 machine), try copying wrap_oal.dll to your wcsaga folder and renaming it as openal32.dll
(you can delete the original openal32.dll file from the wcsaga directory).
It works just fine for me.

Big thanks for this great game to the modder/developer team...