[BarFly]

Hi,

I have the problem that in the 1. practice mission, when I return to the Wellington(?) the game crashes, without any message, back to the desktop
My System: Intel E6300, 2 GB Ram, Nvidia 7600GT PCIe, Sound CMI 3768 PCICard
From the 'options' FSOpen Launcher 5.5a I copied this:
C:\Programme\Wing Commander Saga Prologue\wcsaga.exe -spec -glow -env -mipmap -2d_poof -no_vsync -cache_bitmaps -ship_choice_3d -wcsaga -snd_preload  -ambient_factor 100

I have also the Freespace2opensource installed.
Any help is appreciated of course.

Ciao Hans

[Tolwyn]

Hmm... this is a very rare issue. It was brought up several times before. As a matter of fact: are you using Open GL or D3D mode?

[BarFly]

High,

Hmm... this is a very rare issue. It was brought up several times before. As a matter of fact: are you using Open GL or D3D mode?

oops forgot about this - OpenGL with 1440x900 Resolution - 19" 16/10 LCD
Thx for the quick response

Ciao Hans

[Tolwyn]

Well, my theory is that change-ship-class is causing this issue. I *could* put online a special mission for you later today.

[BarFly]

hi,

Well, my theory is that change-ship-class is causing this issue. I *could* put online a special mission for you later today.

A  special mission just for me  If you need any more information...

Ciao hans

[Tolwyn]

try this one. Place it into data\missions (you might have to create the missions dir first)

[attachment deleted by ninja]

[BarFly]

Hi,

try this one. Place it into data\missions (you might have to create the missions dir first)

it works,  And yes I had to create the missions dir first.
thx a lot!
May I call you Merlin?

Ciao Hans

[Zacam]

This file SORTA works for me. I experience the same issue (along with a LOT of stuttering and jerk, common problem with 3.6.9 and not related to WCS). I find it funny that the only difference is the # in the Flags field....any idea why that is?

How I mean SORTA: Engaging Autopilot now plays the "cutscene" progression from nav to nav instead of ramping time compression. But it still crashes with "WCSaga has encountered an error and needs to close"

Also OpenGL, 1600x1200x32. Rig in Sig.

(FYI, using the 3.6.10 XT builds _really_ ramps some thing up speed wise. But it randomly decides to move the placement of the Fuel and Guns bars away from the Radar back to the bracketing the center of the HUD.)

[Zacam]

Sratch that. No Campaign missions work at all. CtD on training mission 1 weh going back to the Wellington, Mission 2 when going to Nav 1 with the Aurora, Mission 3 when targeting the Pirate cap.

Every one of them (Selested through CTRL+Shift+S) leads to a crash. Am attempting to re-download in the event that it got corrupted, but the MSI should have caught that.

If there is an MD5 for the Installer EXE, I'd like to know so that I have something to check against.

The MD5 for the EXE (Obtained via GamersHell) was: 3AE6C71DBC34097E9BA0D9FF5119FD9E
Now d/l'ing from WCNews.

[Tolwyn]

This is surely a problem on your end. I presume you are using the default video configuration...

[Zacam]

Default every thing. I also made a backup of the launcher INI and made adjustments to no effect.

I made a Profile in the NVControlPanel, no effect.

Tried various builds of 3.6.9 other than the wcsaga.exe, the only effect that had was that Autopilot used simulated cutscenes to move me through them instead of time compression (but only if/when +Flags: 2228226 was set).

Like I said, re-downloading from another source and hoping that will resolve the issue. If not.... *shrugs* I'll either find a way to make it work (pref with a 3.6.10 exe) or I wait for the next official release and settle for playing the Gauntlets repeatedly.

Despite the issues, I love what's been done. I never was really big into the Wing Commander series, for some reason I just was never exposed to it. (Too much DooM editing methinks) This Prologue has me wondering how much I missed out on and how I can get my hands on the originals and a machine to play them on. Thank you.

**Edit: wcnews download MD5 matches. So, I've either got two bad downloads (unlikely) or I need to break out a magnifying glass.

[Zacam]

Update: No longer having any crashes. However, the Autopilot is doing Time Compression.

Is it supposed to, or is it supposed to behave like the autopilot tech demo's? (Which work flawlessly)

[Tolwyn]

Now I am curious: how did you manage to get the game running?

At any rate: yes, in Prologue the autopilot system is fairly simple.

I must say, we were satisfied with it until we started working on a nebula mission. Watching nebula poofs in 64x time compression caused stomach pain, nausea and vomiting. Grr, it wasn't pretty.

[Zacam]

Is there any way to do misson edits to make the AP in Prologue watch the Tech Demo's?

(And in case I an mis-understanding the answer you gave, is there any reason they would not if they are?)

The fix is apparently something shared between the 3.6.10 WMCoolmon 03162008 and the Taylor XT 0314, because they both work without issue.

If you want to know why I'm running those vs the included 3.6.9 wcsaga.exe: It has a known and long discussed issues with the 169.xx  and 171.xx series drivers. In 171.17 there is atleast _no_ graphical corruption, but it has serious performance issues ONLY with 3.6.9 and _early_ 3.6.10 builds.

[BarFly]

hello,

Hi,
I have the problem that in the 1. practice mission, when I return to the Wellington(?) the game crashes, without any message, back to the desktop
My System: Intel E6300, 2 GB Ram, Nvidia 7600GT PCIe, Sound CMI 3768 PCICard
From the 'options' FSOpen Launcher 5.5a I copied this:
C:\Programme\Wing Commander Saga Prologue\wcsaga.exe -spec -glow -env -mipmap -2d_poof -no_vsync -cache_bitmaps -ship_choice_3d -wcsaga -snd_preload  -ambient_factor 100
I have also the Freespace2opensource installed.
Any help is appreciated of course.
Ciao Hans

Just for the record
2 years later are some things different: NVidia 9600GT, the  Motherboard and Sound .
But again the same problem - the Game crashes when I return to the Wellington.
The Good news:
The same solution works 

Ciao Hans

[KeldorKatarn]

Glad to know the workaround works for you, so you can play. We'll try to find the problem for the final release which will include an updated Prologue.