[IPAndrews]

Think you've found a bug in the Raider Wars campaign? Report it here please. Thanks in advance.

[Stunaep]

I guess one could call this a small bug, that being that the TBP 3.1 patch installer deleted my TBP Base.vp, instead of updating it. Any ideas?

[karajorma]

Worked fine for me.

[Admiral Nelson]

The "Smash and Grab" mission doesn't seem to work correctly. The Scylla does not fire at any asteroids. Your wingmates do not fire on asteroids bound for the Wellington, either, even when ordered to protect it.  No idea how it is possible to successfuly complete this one.

[Stunaep]

Pretty please give me a way to extract the files from the installer manually, as right now, the installer keeps deleting my Base vp, (and not installing the campaign, the same as the update), so I can't play it.

Otherwise I'll go to my mommy and cry

[Alphakiller]

Originally posted by Admiral Nelson
The "Smash and Grab" mission doesn't seem to work correctly. The Scylla does not fire at any asteroids. Your wingmates do not fire on asteroids bound for the Wellington, either, even when ordered to protect it.  No idea how it is possible to successfuly complete this one.

Don't order your wingmen to do anything. I saw them shooting at some random rocks then. Also get close to the wellington, stay at low/zero throttle, direct a lot of energy into guns, and start blasting. And praying.
I had the Wellington at 1% hull for the _entire_ time the shuttle was loading guys. Longest 30 seconds ever...

That and just pray you get them all. Not that the "you failed" reccomendation text is worth a damn, I might add. In FS2 it's like "hey here's a helpful hint." in this it's like "Man you're not very good, are you?"

Is it a bug report to say "far too many of these missions rely on bull****tery rather than difficulty?" Or perhaps I'm bitter.

[Admiral Nelson]

...aaand now having completed the "Hell and Back" mission, the game consistently CTDs when clicking commit on the "Incoming Transmission" screen. FWIW:
fs2_open_r caused an Access Violation in module fs2_open_r.exe at 001b:004664a3.
Exception handler called in Freespace 2 Main Thread.
Error occurred at 1/16/2005 19:03:18.
F:\Games\The Babylon Project\fs2_open_r.exe, run by Administrator.
2 processor(s), type 586.
1023 MBytes physical memory.
Read from location 0000014c caused an access violation.

Alphakiller, I figured it would work as it did in the escort Iceni mission. But the mission as a whole is pointless when none of the other ships in it do anything.... Generally I have found the other missions entertaining, but leave the rock busting for the guys sentenced to hard labor in prison...

[NGTM-1R]

This is endemic to TBP missions; I've seen it in pretty much every mission I've played.

Click on the briefing icons and you get God-Knows-What as the ship, not what it actually is. "As the Wheel Turns", for example, had Alpha as flying MF Nials, according to the briefing. Actually, according to the briefing the Scyla was a MF Nail too, and Altair Station was a Kestrel. And this kind of thing happens in EVERY briefing. Granted it's not a serious, crash-your-game bug, but it's annoying.

I think I'll be echoing Alphakiller here too. Failing a mission five times on Very Easy is a sure sign that SOMETHING is wrong with it. I think by creating Gold wing in that mission you might have broken the AI code that gets the Scyla and your wingmen to shoot at regular asteroids.

[Burns]

Wow, these missions are generally hard. Im trying to get though the second one, but damn - too much **** going on. My idiot wingmen shoot down the transports instead of disabling them, even when i tell them to A. Disable ship.. or select engine subsystem and tell them to blow it up. This is rather frustrating.

[PSI-KILLER]

I can't seem to protect the wellington.  It keeps blowing up.

[Alphakiller]

Originally posted by Admiral Nelson


Alphakiller, I figured it would work as it did in the escort Iceni mission.  

Sure, and the Galatea mission before that. Once I finish Raider Wars I'll have my actual opinion written and ready to go, and in a thread slightly more appropriate - I think we're heading a bit off target here.

Specifically to this: Don't target anything, either. I just started the mission, raced for Wellington, and started blasting white box asteroids. Don't ever try and target one (i.e. get red brackets) ... that just messes it up or something. I say this because the one time I got red brackets (without hitting the targeting key) my wingmen did nothing. When I just stayed away from any command or targeting key, I remember seeing at least one wingman shooting at rocks.

My guess, therefore, is there's a bug in the initial Gold Wing rocks -> wingmen protecting Wellington via regular shooting of rocks code or triggers or something.

[Fury]

This thread is not for the patch discussion, this is only to report bugs in the Raider Wars campaign.

[Fury]

Originally posted by ngtm1r
This is endemic to TBP missions; I've seen it in pretty much every mission I've played.

Click on the briefing icons and you get God-Knows-What as the ship, not what it actually is. "As the Wheel Turns", for example, had Alpha as flying MF Nials, according to the briefing. Actually, according to the briefing the Scyla was a MF Nail too, and Altair Station was a Kestrel. And this kind of thing happens in EVERY briefing. Granted it's not a serious, crash-your-game bug, but it's annoying.
 

This is a FEATURE. Three races is not enough for TBP.

Check the brefing icon chart in documentation.

[Fury]

Originally posted by Stunaep
I guess one could call this a small bug, that being that the TBP 3.1 patch installer deleted my TBP Base.vp, instead of updating it. Any ideas?

Raider Wars campaign installer does not touch your B5-Core-3_0.vp.

The patch installer patches B5-Core-3_0.vp but only when it matches the checksum of the original B5-Core-3_0.vp. If the vp's checksum is different, no patching is done.

[Alphakiller]

I'm getting CTDs on the second half of the hyperspace mission; same as Admiral Nelson.

[Fury]

I really hate fred2_open. Once it is used to fix one bug, it presents another.

[PSI-KILLER]

I just had to add that the Wellingotn in asteroid feild is possable to save the crew.  Very good game.  I am very impressed with the animation in breifings and such.  Fine job.  It is balanced where it is very dificult which is good.

[Alphakiller]

Originally posted by Mr. Fury
I really hate fred2_open. Once it is used to fix one bug, it presents another.

So is there a workaround we can use here to just keep playing or what?

[Fury]

Originally posted by Alphakiller


So is there a workaround we can use here to just keep playing or what?

I suggest you play the mission with a debug build in a case it gives us a better explanation of what the problem really is.

http://fs2source.warpcore.org/exes/fs2_open_3_6_5_debug.exe

[Alphakiller]

Hahaha, oh man. You're not going to believe this one...

Debug build? Worked _perfectly_ ... played it just fine.
On the upside, it DID serve as a workaround that I asked for. Thanks!

Want me to get you any information from the debug build, still?