[0rph3u5]

Version 1.0.3:
- Mission 4: Removed a superflous event
- Added Mission 4 Ex (HGI_04-Ex.fs2) to the Mission Simulator. In this mission the Orcus will now be a fully fledged missile destroyer.

EDIT:
Version 1.0.4:
- Added the correct capital04.pof.

[0rph3u5]

Support for this release has been discontinued.

I will continue to fix any bug you find, however any fix will go only towards a future release as part of the Memories of the Great War - Omnibus. This is due to a substantial divergence between the Memories of the Great War - Omnibus version of the "core"-package and the same package found in this release, I will not be able keep up with supporting two different builds.

[amiralace]

I keep trying to beat mission 4 on medium.

Spoiler:

The Galatea blows up every single time. There are just too many Nephilims, and the supply is endless.

Difficulty aside, this is a top quality set of missions in every aspect. Very fine use of FRed. Might be worth looking into adding voice acting.

EDIT:

Spoiler:

I did it. But I had to ignore disarming the Shivan destroyer. Focusing on preserving the first two allied cruisers kept the Nephilims busy long enough to spare the Galatea and to be able to finish them off. I did send Alpha wingmen to disarm the Shivan destroyer (I am not sure to what effect in the end), but I had to give Beta Apollos and assign them to intercepting the bombers. Given the debriefing and the end cinematic, I have a sense that destroying the Shivan warship was not meant to be...

[0rph3u5]

Difficulty aside, this is a top quality set of missions in every aspect. Very fine use of FRed. Might be worth looking into adding voice acting.

Thank you.

I keep trying to beat mission 4 on medium.

Spoiler:

The Galatea blows up every single time. There are just too many Nephilims, and the supply is endless.

Noted for the Omnibus-version.

Spoiler:

I did it. But I had to ignore disarming the Shivan destroyer. Focusing on preserving the first two allied cruisers kept the Nephilims busy long enough to spare the Galatea and to be able to finish them off. I did send Alpha wingmen to disarm the Shivan destroyer (I am not sure to what effect in the end), but I had to give Beta Apollos and assign them to intercepting the bombers. Given the debriefing and the end cinematic, I have a sense that destroying the Shivan warship was not meant to be...

Among the fixes changes for the Omnibus-version are balance changes which make the Disarm-order a bit more sensible for that mission - check out the EX-version in the Mission Simulator if you want to see a "how it should have been"-version of the mission, which goes part of the way to where the Omnibus-version is now.

As for the fate of Orcus:

Spoiler:

Back then it was meant to be a plant for another story, so it is meant to escape. But I never quite managed to pay off that plant. I have no more plans for the Orcus.

[amiralace]

Noted! I'll check that out.

I don't know if you've looked at Discord, but we mentioned your Rain on Ribos IV yesterday. I had planned to play it via Knossos, but it doesn't seem to be on the Nebula yet. Any plans for that? Or would that be released along with the other Memories of the GW into a single mod?

[0rph3u5]

So the original plan was to re-release Rain on Ribos IV seperate, then because it became dependant on balance changes for Vega Must Burn - which when I discontinued support for the Hellgate: Ikeya and Light of Antares as they are on Knossos right now.

With the release of Mjn.mixael's newest Mainhall I also got a little too excited for the possibilites of its added features... so that was another delay.

I am currently averaging one mission a week, but demands on my time have been increasing as social distancing continues - we will just have to see how that goes. Once I have the first branch of Vega Must Burn finished, I will see if I can't push a version of Rain on Ribos IV to completion as well.

[amiralace]

Thanks for the clarification. Looking forward to your new campaign as well then.

Not that it makes the completion of projects any easier, but voice acting could at the very least be a nice finishing touch to these works - and in case you're interested, there's this thread, for instance. Wither better voice actors than me would also be great, obviously.

[caine440]

I went to install this campaign and it says it cannot install because the MVP is missing.
How can I check to see which MVP release is needed so I can install it.
Or am I missing something simple?

Thanks!
 

[Firesteel]

I remember trying to troubleshoot this a while ago but with one of the more recent MVP updates, the way to reference them in the dependencies changed slightly and the couple of cursory attempts to fix it made it seem like it wasn't just the dependency list at the top of the mod.json that was referencing the wrong thing.

[0rph3u5]

Obsolete now, replacement deployed:

[Mobius]

Congratulations! Time for another playthrough of these campaigns. 


EDIT (because I don't feel like double posting). Very enjoyable campaign, and quite challenging too! I stumbled into a number of minor issues, however:

Spoiler:

- This is probably a known issue, but just in case: the Aten model seen in the campaign is outdated. FSPort dependencies are known to cause this sort of things, and you probably know it already.
- For some reason, even though it's pretty much a standard feature even in the Port, the Galatea lacks her nameplate.
- In the Typhon inspection mission, I get storms of messages about Orcus fire barrage right at the beginning of the mission itself. Later on in the mission, if I get too far from the destroyer during the data download procedure, I receive an even more intense message storm. If these warnings are meant to warn the player and get him to pull back to the Typhon in order to speed up the data transfer, they could be sent every 5-6 seconds maybe. Unfortunately, I forgot to take screenshots showing the flow of these messages but the issue is fairly easy to reproduce - I played the mission 4 times, and got the exact same message patterns during all playthroughs.

[0rph3u5]

- For some reason, even though it's pretty much a standard feature even in the Port, the Galatea lacks her nameplate.

Fixed in 1.0.1. Must have slipped my mind because I didn't have to make a nameplate for the Galatea.

- This is probably a known issue, but just in case: the Aten model seen in the campaign is outdated. FSPort dependencies are known to cause this sort of things, and you probably know it already.

Just as with the lasers, put on wait for 1.1 - unlike the Demon, Cain & Lilith the Aten is not affected in function by the dependency conflict.

- In the Typhon inspection mission, I get storms of messages about Orcus fire barrage right at the beginning of the mission itself. Later on in the mission, if I get too far from the destroyer during the data download procedure, I receive an even more intense message storm. If these warnings are meant to warn the player and get him to pull back to the Typhon in order to speed up the data transfer, they could be sent every 5-6 seconds maybe. Unfortunately, I forgot to take screenshots showing the flow of these messages but the issue is fairly easy to reproduce - I played the mission 4 times, and got the exact same message patterns during all playthroughs.[/spoiler]

Seperate issues:
- the missile warning had the wrong kind of arguments list, oversight on my part. Fixed in 1.0.1.
- the distance warning for some reason has been saved as "intervall in miliseconds" when it is intended to be 20 seconds. Fixed in 1.0.1.

[caine440]

Thank you for releasing these campaigns. Already downloaded and ready to play tonight.