RELEASE: Legion's Demise- a playable FS2 Intro!

The Lucifer has just entered Deneb. Now the GTI has been mobilized to defend Deneb from the Shivans and to look for a weakness in the Lucifer, and you (Iota 1) find yourself at the forefront of disaster. Can you command your squadron, save the Intel, and minimize the damage? Or will you fall onto Deneb III with the rest of the space junk?(for plot purposes we will assume it's one of your wingmen who gets shot down in the cutscene, and not you.)This is a two mission FSPort mini campaign set around the Battle of Deneb. In it, you will take part in GTI's last-ditch plan to destroy the Lucifer's escort fleet, assist the Vasuden evacuation of Deneb III, REDACTED, and brake the Superdestroyer's shields. What could possibly go wrong?

Features:Two action-packed, well Fredded missions with clear win/fail states. Balanced for play on (More or less) all difficulties.

Modded HUD elements.

Railgun and Prometheus-A.

The 1st mission is a Playable recreation of Freespace 2's opening video, and the 2nd mission involves escorting the GTC Juggernath!

Re: RELEASE: Legion's Demise- a playable FS2 Intro!

What are the dependency problems you have with 3.8.0? Did you try the AppImage build? You should be able to download that from the release thread and run it without having to compile or install anything else.

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. <MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".(the very next day)<MageKing17> this ****ing code did it to me again<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."<MageKing17> **** ME<MageKing17> THE REASON IS PEOPLE ARE STUPID<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"(...)<MageKing17> so<MageKing17> more than two hours<MageKing17> but once again we have reached the inevitable conclusion<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

Re: RELEASE: Legion's Demise- a playable FS2 Intro!

Special Containment Procedures: SD-001 is currently uncontained. Research is currently focused on developing a way to bypass the object's overdriven shield matrix. MTF-70 ("Blue Lions") is on 24-hour standby should an effective means of damaging the object be discovered. Until such a mechanism is found, any engagement with SD-001 is strongly discouraged.

Any personnel encountering SD-001 are to report to GTA Command immediately. Accurate monitoring of the object's location and heading are essential to preventing a second [REDACTED] scenario.

Description: SD-001 is a ████-meter-long Shivan destroyer of [DATA EXPUNGED] origin. The vessel is employed as a raider, using its air wing and high-alpha [REDACTED] cannons to devastating effect against targets of opportunity. SD-001 houses the equivalent of at least ██ GTA fighter squadrons. At this time, it is unknown how the vessel can host such an overwhelming number of spacecraft. When not active in this role, SD-001 appears to act as a central [DATA EXPUNGED] for Shivan operations. MTF-99 ("Skulls") is investigating means to disrupt this capability. Per Order-001-NOOS, research into Shivan communication procedures has been suspended.

SD-001 integrates two unique technologies not seen in other Shivan specimens. The first is a pair of [REDACTED] cannons located in the ship's bow. These cannons have been employed to overwhelming effect against targets ranging from cruiser-size to [REDACTED]. It is suspected that SD-001 may use [DATA EXPUNGED] to mitigate the heat dissipation issues associated with such weapons. The second is a destroyer-scale shield system, similar to that seen on Shivan strikecraft but massively scaled up. This shield is impervious to all known GTA and PVN weaponry.

Following operation [REDACTED] in the █████ system, Dr. ████ of Galactic Terran Intelligence has proposed that a reverse-engineered version of SD-001's own cannons may be sufficient to penetrate its shields. Research is ongoing.

In light of the ██████ incident's effect on morale, disinformation campaign STONE RAIN is in effect to downplay 001's significance. The redaction has been deemed necessary. ~GTI-██

Addendum:Regardless of what the ████████ say, this ship is an opportunity! Imagine the potential - a beam-equipped destroyer in every GTA fleet! Permission to detach the Repulse for independent reconnaissance is hereby requested. ~Admiral Glaive

Request denied following considerable discussion. Giving up even more to your pet warship isn't an effective use of our resources at this time. ~GTI-██

Special Containment Procedures: SD-001 is currently uncontained. Research is currently focused on developing a way to bypass the object's overdriven shield matrix. MTF-70 ("Blue Lions") is on 24-hour standby should an effective means of damaging the object be discovered. Until such a mechanism is found, any engagement with SD-001 is strongly discouraged.

Any personnel encountering SD-001 are to report to GTA Command immediately. Accurate monitoring of the object's location and heading are essential to preventing a second [REDACTED] scenario.

Description: SD-001 is a ████-meter-long Shivan destroyer of [DATA EXPUNGED] origin. The vessel is employed as a raider, using its air wing and high-alpha [REDACTED] cannons to devastating effect against targets of opportunity. SD-001 houses the equivalent of at least ██ GTA fighter squadrons. At this time, it is unknown how the vessel can host such an overwhelming number of spacecraft. When not active in this role, SD-001 appears to act as a central [DATA EXPUNGED] for Shivan operations. MTF-99 ("Skulls") is investigating means to disrupt this capability. Per Order-001-NOOS, research into Shivan communication procedures has been suspended.

SD-001 integrates two unique technologies not seen in other Shivan specimens. The first is a pair of [REDACTED] cannons located in the ship's bow. These cannons have been employed to overwhelming effect against targets ranging from cruiser-size to [REDACTED]. It is suspected that SD-001 may use [DATA EXPUNGED] to mitigate the heat dissipation issues associated with such weapons. The second is a destroyer-scale shield system, similar to that seen on Shivan strikecraft but massively scaled up. This shield is impervious to all known GTA and PVN weaponry.

Following operation [REDACTED] in the █████ system, Dr. ████ of Galactic Terran Intelligence has proposed that a reverse-engineered version of SD-001's own cannons may be sufficient to penetrate its shields. Research is ongoing.

In light of the ██████ incident's effect on morale, disinformation campaign STONE RAIN is in effect to downplay 001's significance. The redaction has been deemed necessary. ~GTI-██

Addendum:Regardless of what the ████████ say, this ship is an opportunity! Imagine the potential - a beam-equipped destroyer in every GTA fleet! Permission to detach the Repulse for independent reconnaissance is hereby requested. ~Admiral Glaive

Request denied following considerable discussion. Giving up even more to your pet warship isn't an effective use of our resources at this time. ~GTI-██

Re: RELEASE: Legion's Demise- a playable FS2 Intro!

Any possibility of getting this on Knossos? It's on my radar (duh), but an easy way to play it without futzing about with too many settings manually would probably bump it up a few notches in priority, if you know what I'm saying.