-
(https://i.imgur.com/XdccDbH.png?3)
(v1.44)
Story Background
Capella happened. Though the Shivans are sealed off in Capella and the Neo-Terran Front is crushed, optimism soon fades when both Terrans and Vasudans start realizing what they actually lost during the war. It is not enough that they lost billions of innocent civilians, theColossus with many hi-ranking officers on board, and the bulk of their fleet, there is no guarantee that the Shivans won't find another route into GTVA space in the future.
High Command and numerous galaxywide civilian corporations are willing to put more effort and money into research and development, both civilian and military, to press the severely weakened Terran-Vasudan alliance into a new age. Countless reconstruction plans had been suggested in three months, the most promising and thorough devised an ambitious and potentionally gainful project: a giant scientific endeavor to learn more about the Ancients' civilization. They all know that, even though the Ancients were defeated by the Shivans millennia ago, it is them who supplied the Terrans and Vasudans with knowledge that allowed these two species to survive the attack of the SD Lucifer's task force. Discovering multiple Knossos subspace portals has convinced all leading figures that Ancient Empire indeed stretched much further than anyone could have imagined.
(https://i.imgur.com/YXqfxWD.jpg?2)
Civilian corporations saw the ambition and the possibility for profit in the project, and subjected themselves to study the unknown. Though the GTVA, a military alliance, was justifiably low on funds after a devastating conflict of such a scale, it was a matter of time until civilian corporations, who suffered lightly during the war, started supplying the initial preparations with seemingly unlimited funds. Within a year, the Altair system, which is believed to have played a major part in the Ancient Empire's history, was teeming with practitioners of all walks of science, including archeology, xenolinguistics, astronomy, and physics.
However, the rest of the GTVA was more bothersome. The Terrans and Vasudans diverged from each other, minding their own businesses. The Vasudans were concerned with their own traditions and respect to their deities. The Terrans were preoccupied by the welfare of their society and steadiness of their economy. Despite all this, the alliance remained officially intact. The General Assembly assembled, the Security Council communed, and the Vasudan Imperium did not hesitate to assist the other two branches when requested. The two governments withdrew to their respective homeworlds: the Terrans to Vega, where they intend to rebuild Earth in their own way, and the Vasudans to their desolate yet beloved Vasuda Prime.
(https://i.imgur.com/O4uuEEd.png)
Very soon, disturbances take place at Altair. Unknown Terran fighters and cruisers keep harassing supply depots and unguarded science vessels. As more military vessels are deployed, the pirate strikes intensify. Their intents are not as clear as those of most pirate organizations. Pirates typically don't destroy science vessels just for the sake of it, but take hostages and demand a ransom. These Terrans are different. Not only different, but more powerful. As the project's existence is gradually jeopardized by the escalating number of thefts, the Security Council hastily orders the deployment of the GTD Phobos and its fighter wings, along with a number of other corvette and cruiser-sized vessels. Because of the intermittent and unpredictable nature of pirate strikes, it is impossible to keep the entire task force in one place. The ships of the scattered task force gradually disappear. None of them ever sent a distress signal. On a dark day, the Phobos also vanishes.
Notable Changes
- All 31 missions have been revisited to various degrees. There were major alterations and additions to most of them. There were numerous bugfixes, thus you will be able to play through all the thirty missions without show-stopping bugs.
- Apart from the mandatory bughunt, this update's primary focus was to provide a fun playthrough not present in the earlier releases. Thus, gameplay has improved a great deal. There are a lot of quality-of-life improvements compared to the previous v1.1 release, including many more messages that give you useful advice on how to approach a given situation, more informative briefings, directives, mission goals, and a more intuitive use of the escort list.
- Pilot banter and, generally speaking, mission messages have become more military-like and mature. There's also far less yelling !!! during the missions.
- Use of Lightspeed's nebula backdrops and the old, low-quality planet images have all been replaced with high-quality ones.
- Non-retail music tracks provided by fellow HLPer ShadowOfLight, freeplaymusic, and other sources.
- Inclusion of the GTF Rapier, also known as the TF Kvasir as a Myrmidon Mark II.
For a full list of credits, see the accompanying credits.txt
(https://i.imgur.com/kFDXgz0.jpg?1)
Requirements
- MediaVPs 4.4
- FreeSpace Open 21.2.0 Release Candidate 2 (https://www.hard-light.net/forums/index.php?topic=97507.0)
Known Issues
- Debug builds produce a warning message at the start of every mission that features the GTF Rapier (TF Kvasir). This does not affect gameplay in any way.
- The mission "In Front of the Gate" produces a fatal crash when playing with a debug build. Release builds play the mission without problem.
- The mission "Warming Up" might crash during loading with lower-end machines with an error saying you're out of memory. If this happens, lower graphical settings, mainly by turning off more graphical features in the launcher. Computers with more than 4 GB RAM will likely not run into this issue.
See the campaign's FreeSpace Wiki article (https://wiki.hard-light.net/index.php/Renegade_Resurgence) for more information
DOWNLOADS
(https://fsnebula.org/static/kn_download.png) (https://www.fsnebula.org/mod/RR_v144)
wxLauncher version:
MediaFire mirror (https://www.mediafire.com/file/ov1yetc7t25t8b4/RR_v144.7z/file)
(unextract using 7-Zip (https://www.7-zip.org))
Put into your FreeSpace 2 folder, so the .vp should be in the FreeSpace 2/RR_v144 folder. Your MediaVPs must be in the MediaVPs_44x folder, otherwise you have to edit the included mod.ini (https://wiki.hard-light.net/index.php/Mod.ini). Open the file with a text editor, find the line starting with "secondarylist" and edit the folder's name accordingly.
.vp checksum
Found root pack 'C:\Games\FreeSpace 2\RR_v144release\RR_v144.vp' with a checksum of 0xc1776b8c
.vp file number
Searching root pack 'C:\Games\FreeSpace 2\RR_v144\RR_v144.vp' ... 190 files
-
Congrats on the release but I think you forgot to put in MVPs 4.4x with it. I looked in the "modify" tab and 4.4x was not in there. I also checked the tech room and the ship models were vanilla
-
This is the Knossos release, right? I did put the MediaVPs as a dependency, but I'll check it out.
-
This is the Knossos release, right? I did put the MediaVPs as a dependency, but I'll check it out.
It is knossos...forgot to say that
-
Check now. I refreshed the dependency settings and ran it myself, and the MediaVPs loaded.
-
Check now. I refreshed the dependency settings and ran it myself, and the MediaVPs loaded.
Currently doing a fresh reinstall of the mod and MVPs 4.4x just popped up for me so I think whatever bugged the release is gone
UPDATE: reinstall worked for me! :)
-
Mission 4 does not load. Another thing I think should be fixed is that medals still don't align in the medal box like they should
-
The medal thing is not my field of expertise. I simply renamed some medals in the medals.tbl to be more appropriate for the Post-Capella Era. If that causes a problem, it's a coder you need to find. I did have that thing, though I thought it was just a visual bug on my end.
I'll investigate Mission 4 a bit later. My guess is that somewhere it uses a post-21.0.0 coding somewhere. Knossos didn't let me mandate 21.2.0. RC2 as a required build. so I was forced to set it to 21.0.0 official.
[EDIT]Yes, it's a build issue. I ran it with the 21.0.0 build via wxLauncher and it didn't load. RC2 21.2.0 debug loads it without any compaints, so I'm assuming my initial guess was correct. I'll investigate it once I have the time.
I'm editing the release post until then.
-
SCREW KNOSSOS!!!
The wxLauncher file is "upgraded" (downgraded) to run on FSO 21.0.0 official. I've wasted hours "fixing" the issue that wouldn't have been there in the first place had this piece of garbage of a mod manager allowed me to require my mod be played with RC2, only to find Knossos is completely incapable of simply overriding one VP with another. Then I deleted the whole project, and that piece of **** complained someone is already using the mod ID I already deleted.
I'm done with Knossos.
-
I know what you mean :rolleyes:.
But well... somehow you have to arrange with it as many people are using that.
Sometimes it is tricky, as mods with Developer rights are handled different to mods were you only have playing rights.
It helps if you create a second account that you can use as an internal tester and then switch the users to download and start the mod in a regular manner.
It is still a nightmare from a developer perspective sometimes... but well, it is the best you can do.
That is actually the reason, why i was against the switch to Knossos as a sole release platform as long such severe problems still exists.
-
The wxLauncher file is "upgraded" (downgraded) to run on FSO 21.0.0 official. I've wasted hours "fixing" the issue that wouldn't have been there in the first place had this piece of garbage of a mod manager allowed me to require my mod be played with RC2, only to find Knossos is completely incapable of simply overriding one VP with another.
This is just a hunch but could it be that in the Knossos settings (under General), your preferred stability is set to "stable"? That settings will hide RC and nightly builds. You also can't select builds that you don't have installed (the main reason behind that is that you wouldn't be able to test them anyway).
What do you mean by "overriding one VP with another"? Knossos doesn't allow several VP files with the same name since it'd lead to conflicts and it'd be impossible to tell which VP file a user would actually get when they installed the mod and chose two packages that contain the same VP. It never seemed necessary to allow it, either.
Then I deleted the whole project, and that piece of **** complained someone is already using the mod ID I already deleted.
You can't delete a mod ID, you can only delete releases and even if a release was deleted, you can't reuse the same version number. This rule was created to ensure that if two players have version x.y.z of mod ABC, they always have the same files not an earlier or later upload. Tracking who downloaded what would get very complicated so it's far easier to just allow one upload per mod ID and version number.
The warning should probably also check if you own the mod ID before it warns that it's taken but I never expected someone to create their mod after they already uploaded it once so I didn't consider that case when writing that warning. That said, you should be able to ignore that warning. There's a separate check during upload which should allow you to still upload your mod since you're the one who first used that mod ID. If that doesn't work, PM me your mod ID and Nebula account name and I'll sort it out.
-
I now have my build settings set to "Nightlies" and when I try to direct my mod's FSO tab to that build, it first allows it, then when I try to upload, it says I can't use a local build. Of course I do have it installed, otherwise I wouldn't be able to point the "Browse" window to that .exe file. I still have the same three builds listed: 19.0.0, the december 11, 2020 nightly and the 21.0.0. I assume they're the requirements of the mods I have installed via Knossos.
By overriding it, I mean I had the original RR_v144.vp uploaded with the RC2 features at first (night of April 13), then changed some files to remove the post-21.0.0 features (changed four or five missions), recompiled the RR_v144.vp, then tried to get Knossos to change its version of RR_v144.vp to the new one (morning of April 14). When I tried to point my updated VP to it by clicking on the folder path below "Mod Path", it opened up a browser where if I double-click on a .vp, it opens up QuickVP as opposed to recognizing it as the new version I want to override the old version with.
Note: I'm developing from the traditional Games/FreeSpace 2 folder and using wxLauncher. Those few mods I have via Knossos are in Games/FreeSpace 2/Knossos. I haven't had a version of RR in my Knossos folder until I tried the version I uploaded following the "error" report about mission 4.
Also despite apparently deleting the mod, I was still able to re-download it from the Explore tab to check if your advice about Preference settings work.
From the previous post, I forgot to mention that my plan in deleting was to first delete the whole mod entirely, then upload the same thing again with the same settings and same steps (now with the RR_v144.vp I'm using as the base .vp being from the morning of April 14) to preserve the original link to Knossos in the OP by using the same ID, I wanted to avoid the confusion of having three version of RR available (the first one being Novachen's revision of an older version, the second one being the original release with 21.2.0 features, the third one with the 21.0.0 "updates").
[EDIT2]Hang on a second.
I just started the current version from Knossos and for some reason it ran the 21.2.0 RC2 build with it, and mission 4 loaded without a problem. I still don't have the 21.2.0 RC2 build in FreeSpace 2/Knossos/bin - it's in the root FreeSpace 2. Maybe it did recognize the RC2 build but the software believed it didn't and sent the error message instead? I have no idea what happened.
-
I now have my build settings set to "Nightlies" and when I try to direct my mod's FSO tab to that build, it first allows it, then when I try to upload, it says I can't use a local build.
You can't use a local build since Knossos won't be able to figure out which FSO version to use when someone wants to use your mod. Using your local .exe file works for local testing but you can't upload your mod unless you select a specific version from the drop down.
Of course I do have it installed, otherwise I wouldn't be able to point the "Browse" window to that .exe file. I still have the same three builds listed: 19.0.0, the december 11, 2020 nightly and the 21.0.0. I assume they're the requirements of the mods I have installed via Knossos.
You'll have to install RC2 through Knossos if you want to tell Knossos to use it for your mod.
By overriding it, I mean I had the original RR_v144.vp uploaded with the RC2 features at first (night of April 13), then changed some files to remove the post-21.0.0 features (changed four or five missions), recompiled the RR_v144.vp, then tried to get Knossos to change its version of RR_v144.vp to the new one (morning of April 14). When I tried to point my updated VP to it by clicking on the folder path below "Mod Path", it opened up a browser where if I double-click on a .vp, it opens up QuickVP as opposed to recognizing it as the new version I want to override the old version with.
If you click on the folder path, it opens your local mod path in Explorer. It's just Explorer, not a file select dialog. You have to replace the file there. Double-clicking the .VP there just opens it with the default program on your system (which seems to be QuickVP).
Also despite apparently deleting the mod, I was still able to re-download it from the Explore tab to check if your advice about Preference settings work.
Did you get this screen when you deleted the mod?
(https://d.gruenprint.de/ZaqCWmLfhl0lf4PFqYerSHaQGSSfuHyP.png)
"Local Delete" and "Uninstall" only delete the mod from your system not from Nebula.
EDIT: If you haven't already, you might want to read this guide (https://docs.google.com/document/d/1oHq1YRc1eXbCgW-NqqKo1-6N_myfZzoBdwZuP16XImA/edit?pli=1#) that explains the whole mod uploading process.
-
I tried to install the build, but now it complained that the package folder was empty even though I had the build as the main download and the debug as a package. What package folder? Isn't a build just one download?
-
FSO builds have several packages for different OSes and different architectures. Each package (even for mods) is a separate download. That said, it shouldn't complain about an empty package folder if you install it. I think that error should only show up during mod upload. Let me just check the source real quick...
-
Yeah, the message "The package ABC is empty!" should only show if you upload a mod and that only happens if one of your packages didn't contain any files since that's pretty pointless.
-
But what FOLDER? I have three files I'm using in FS root: the release 1) game engine and 2) FRED and the 3) debug game engine. Do I need to download every combination of platform + engine + FRED?
Okay, using the sample of /FSO-21.0.0/ in my Knossos/bin, I have a Knossos/bin/FSO-21.2.0 RC2/ with a /windows folder, within it an /x64 and /x86 folders with the four .exes, the .dlls and misc required techincalities. What's next?
-
What is the exact error message you got? If you got the error while uploading your own mod, only the folders in your own mod matter. The FSO folders don't since those are already managed by Knossos. When you click on your Mod folder link in the dev tab, Knossos should open your mod's folder in Explorer. There you should see a mod.json and maybe a few other files. Each package you create in Knossos will also show up as a subfolder there. If Knossos complains that one of your packages is empty, it is one of those folders. The error message should mention the folder name which should tell you which folder is empty.
-
I created a new mod using "Create" and selecting "FSO build", then setting the main download to the release engine build. At first, alone, then trying to add the debug as a package. Same complaint. I can't quote the exact message, because I didn't take a screen, and deleted the whole thing when it became clear it wasn't working, but it said "Can't upload because the package folder is empty." Now I just have the build and its accessories in FreeSpace 2/Knossos/bin/FSO-2.21.0 RC2/.
-
Wait. You tried to create a new build? Why don't you just install the RC2 already available? If you wanted to upload your own FS2 build, you'd have to include the Linux and macOS files as well or it won't run on those platforms.
To install a specific FSO version, go to the settings screen, open the General section, make sure your preferred engine stability is either RC or Nightlies, make sure "Show Engine Builds in Mod List" is enabled, save, go to the Explore tab, hover over the FSO tile, click the Details button, select the version you want from the Version dropdown and click Install. If that version already looks like it's installed, close Knossos, delete your FSO-21.2.0 RC2 folder, open Knossos again and install it.
Once FSO is installed, go back to the Dev tab, select your mod and the correct FSO version from the FSO build dropdown. Hit Save at the bottom of that page. Now try uploading your mod again.
-
Okay, after three attempts I managed to run the mod via Knossos, except this time it downloaded the April 12 build despite having clearly set it to RC2 at first, then I realized it also forgot I added the MediaVPs as a dependency (for the seventeenth time in the past 24 hours), so I readded that, but a clear whole delete -> redownload from Knossos -> "Play" successfully ran the mod, with the April 12 build, but it runs.
Thanks for the help. I appreciate it, even if I'm entirely worked up over this.
Can someone check if they can run the mod, with MediaVPs and a new FSO build?
I'll add the Knossos link to the OP once someone confirms it works as intended.
-
It works fine for me.
-
@ShivanSlayer: Make sure you've updated to 1.0.1 before testing. Mission 4 is "Strike In Vain" (M04_RR.fs2), right? That mission launches just fine for me (although I only tried to launch it from the tech room).
-
Mission 4 finally starts
-
Techroom or not, the problem was caused by the turret-set-inaccuracy SEXP, which was added some time in March.
-
Another issue present in this version present in the other one is that in the mission "Abduction," sometimes the allied transport that is supposed to board the transport you disable collides with the station and gets stuck. This can make for an endless mission
-
Beat the last mission, but I get failure music and it tells me I failed even though I completed every objective
-
Okay, that's a blast from the past. Yet another thing I fixed 70 times during development that kept coming back and somehow made it into the Knossos release. Now I spent my whole morning and early afternoon making every paranoid precaution to make sure no traces of the old campaign file remained. Fixes uploaded and I actually replayed the whole campaign to test just this,with fresh install, and a new pilot just to see if this finally works.
It does.
I don't know if it will work for you or those that download the fix AFTER beginning the campaign, since this related to the campaign file, which I believe is loaded either in the campaign room after "Select" or the launch of the first mission.
-
I replayed the final mission and it was recorded properly as successful
-
Strange problem here:
My ship is taking no damage, no matter if ships or beems are hitting me. The mod is good but I don´t like flying with godmode :-)
-
Which version did you download and which mission is this?
-
I dl with Knossos and played the first 3 missions. All did have the same issue.
-
Can't reproduce, sorry.
First I ran through the xwLauncher version, all 31 missions up until the first point I could realistically hurt myelf, and I was always vulnerable. Second, the first three missions with the same method on the Knossos version. Still vulnerable. Third, I figured I'd try it with the newest (unpromoted and minor (https://www.hard-light.net/forums/index.php?topic=97528.0)) MediaVPs updates because "Why not?" Still could hurt myself.
-
doublepost, sorry
-
Well I play on medium. Do I have very strong shields than? To test this I was flying nere a cruiser an it beems hit me 3 or 4 times with no damage on my ship. The shield indicator reacts but it don´t seem to harm me.
-
AAA turrets in Renegade Resurgence don't pierce shields. If there's a red flash, then you are taking damage, but you are careful enough not to move too slowly, too close near the AAAs. In the first couple missions, they are rather weak, but there will be missions later where you will feel the hurt, trust me.
-
Okay, will test again this evening. Thanks so far.
-
Can I make a suggestion for mission 6 "A Champion"?
I would suggest making the Phobos' beams invulnerable (like they were a few missions earlier when the Phobos came in to attack a station and you had to escort an Argo away) and removing the directive to destroy the Phobos beams from the directives list. If you destroy them too quickly it can break the mission (I don't think your allied destroyer is supposed to survive). At least, when I destroyed the Phobos' main beams quickly, the destroyer you're protecting never jumped out.
However, when I tried the mission later and let the Phobos destroy the capships I was supposed to protect, I was able to progress in the campaign.
-
Spoiler tags! Spoiler tags!
There's also an Aeolus that arrives as a reinforcement if the Phobos's main guns are destroyed quickly. Did it not show up or did you manage to disarm it, too?
Also what difficulty were you playing on?
Another thing: If I go about your solution, which I considered of course, but decided to go about the non-guardianed way, then someone else might come along and complain about that. I made my choice and it's final.
-
I reinstalled the mod yesterday and played the first 7 missions.
Everything works fine so far! Great mod.
-
Spoiler tags! Spoiler tags!
There's also an Aeolus that arrives as a reinforcement if the Phobos's main guns are destroyed quickly. Did it not show up or did you manage to disarm it, too?
Also what difficulty were you playing on?
Another thing: If I go about your solution, which I considered of course, but decided to go about the non-guardianed way, then someone else might come along and complain about that. I made my choice and it's final.
I believe I managed to disarm it too. I remember in my first playthrough the Aquitaine made it to the node and the Octopus survived too. Another solution might be to start the Aquitaine off at lower health.
I wanted to quickly see how the campaign compared to previous versions so I was playing it through on Very Easy. Would a higher difficulty be better?
I beat the campaign recently. Aside from this issue I just mentioned (which wasn't major and there was a workaround somewhat), I didn't encounter any gamebreaking errors and consider this a fun campaign and improved over previous versions. One thing I'd especially like to compliment this new version on was "Twilight." In previous missions that mission was easily broken but this time around played a lot better.
There was one minor technical error in the campaign though (I'll put it in spoilers just to be safe):
Nameplates didn't always appear on allied Terran warships. For instance, in its first appearance "GTC Fisthand" didn't appear on the side of that cruiser but in a later mission it did. Same with "GTD Obelisk" and "GTD Carthage" for example...sometimes nameplates would appear and sometimes not. Though some ships did always have their nameplates like "GTD Phoenicia" and "GTC Thief's Hand".
This wasn't a gamebreaking error, it was just something I noticed.
Overall, this was a great work.
-
Now that you mention it, one of the to-do things I completely forgot about was to test on any difficulty other than medium. I was carried away testing Anything Else(tm). :P
So glad you noticed the revamp to "Twilight." It's been rebuilt from GTF Ulysses 0 and I'm happy someone took note. Really gives me more energy to continue FREDding for Fate of the Galaxy (which is near the finish line). Thanks for the compliment.
-
So, I finished RR yesterday.
Really great campaign. Not just killing endless waves of bombers an such. Varied goals, tactical gameplay and quite a challenge on medium.
Congrats and many thanks to TopAce!
-
RIP TopAce.
This was a great campaign.