[semmelbrot]

Hi there!

First of all, this is my virginity Post. And I want to say that this is a great project, please keep up with the great work. Freespace has become such an awesome game with the mediavps and all. But i have an annoying problem.

I installed FSO and FSPort Manually on Linux using fs2_open_3614. The Game itself works like a charm but I'm having trouble with the Red-Alert Missions.
I'm in the Tenderizer Mission of the FSPort. When the Galatea jumps out Command says something like "Standby for further orders". But after that nothing happens. When I jump out via Alt-J I get to the debriefing and the Messege that I was not allowed to jump out. When I hit continue im immediately in the "Incoming Transmission" screen, and I can play the next mission. It wouldn't bother me that much, because I can still play the campaign. The problem is when I'm in the second last mission when you have to follow the Lucyfer into subspace. When I reach the jumpnode and try to jump out via Alt-J it says "Jumpdrive not operable" or something like that. So I'm stuck there. I know that normaly the mission should end atomatically and jump to the "Incoming Transmission" screen.

It's so annoying, I want to play the game as it's meant to be

Does anyone know how to fix that? Here is my fs2_open.log. If there is some other info needed please tell me.

Greetz

Semmel

[MatthTheGeek]

Red alerts have been a broken mess since retail. However, that doesn't exactly seem to be the issue here.

IIRC this mission has some FRED logic holes that can possibly make the mission way too long or even impossible to complete (as sometimes the case with canon missions). There's something about Delta wing not launching if you don't destroy the first wave of basilisks, which blocks the progress of the rest of the mission.

As this is a FSPort and not FS1 issue you're having, this might be better moved to the FSPort board.

[semmelbrot]

Sorry my fault, I forgot to mention that the same happens in the FS2 campaign. In the mission where you have to escort the Bastion to destroy the jumpnode. So it is not FSPort specific. I also tried fs_open_3612 fs_open_3613 and new created pilots for both versions. But nothing changed. With all that in mind i don't think it is a FRED logic problem. Thanks for the answer though.

[MatthTheGeek]

In that case, can you get us a debug log ?

[Goober5000]

He already did, in his first post.

This smells like it's related to the issue Black Wolf reported:
http://scp.indiegames.us/mantis/view.php?id=2683

I intend to fix this as soon as possible, but this is another crazy week for me, limiting my time available.  Could anyone assist by narrowing down the revision at which this appears?

[MatthTheGeek]

He already did, in his first post.

My mistake, old habits die hard.

[semmelbrot]

Just realized that I mixed up my version numbers. I just played the Bastion Escort Mission from the simulator with 3.6.12 and when the Bastion jumps I instantly get to the main menu. So it should be fine with 3.6.12. I tried two other versions: 3.6.13 and 3.6.13.8748. I got these version numbers from the main menu. In both 3.6.13 versions the bug appears. I hope that helps.

[Goober5000]

It doesn't tell us anything we didn't already know.  We need someone to narrow down the range of revisions in source control.

[Goober5000]

Does it happen with this build?
http://staff.hard-light.net/goober5000/temp/r9051.zip

[xXGrifterXx]

Hello,

I'm playing STR and I am having problems with the red alert mission between the emp mission with the Krazy Ivan's and the Krios. When I warp out from the Krazy Ivan mission I get the "you should not have left the battle area" rant from command, but you can click Accept and continue on to the next mission. Unfortunately when you do that it puts you in a valkyrie, which is odd as in the previous mission you are in a Herc. 

[xXGrifterXx]

Forgot to say I'm playing on 3.6.14 RC6.

[Goober5000]

Can you retry the mission with the build I linked to immediately above your post?

[xXGrifterXx]

Can you retry the mission with the build I linked to immediately above your post?

Hi Goober,

Just tried it with that build, same result.

[Goober5000]

Well it sounds like two different players experienced the same bug, but I was not able to reproduce it in my testing this evening.  I tried both release and debug builds, so I'm a bit stumped.

[MatthTheGeek]

Unfortunately when you do that it puts you in a valkyrie, which is odd as in the previous mission you are in a Herc. 

Well that part is easy : red alert bug. STR dates back from when that bug wasn't all that known and there weren't really good alternatives to it anyway. Nothing to do about it than make a new pilot from scratch and replay the campaign.

Although the real issue Goober is probably interested here in is

When I warp out from the Krazy Ivan mission I get the "you should not have left the battle area" rant from command, but you can click Accept and continue on to the next mission.

which sounds more like a FREDing issue, and hence may be fixed.

Those are two separate and most likely unrelated issues.

[Goober5000]

No, they are the same single issue.  The issue is that red-alert is simply not triggering.  This causes a default to the AWOL debriefing as well as a default to the Valkyrie loadout in the next mission.

The problem is that I can't reproduce that issue.  Red-alert triggers successfully every time I've tried it.

[Goober5000]

I may have stumbled onto the cause of this issue.  Semmelbrot, do you play with the HUD enabled?