[karajorma]

As with previous patches, this patch does not require you to have earlier versions of the patch in order to work.

This patch is larger than the proceeding ones due to the new animation.


Downloads

Windows

Mac

Linux

Changelog

Fix an multiplayer issue with weapon convergence.
Fix an issue where the prometheus wouldn't depart
Add new animations for the volunteer for M3 screen
Fixed M6 breaking if Ion 1 is destroyed.
Added directive counts training missions

[Luis Dias]

The installer says the version is 1.0.2. It installs the correct 1.0.4 version, but I hesitated in clicking the button .

[karajorma]

Damnit. I knew I'd forget to update that somewhere!

EDIT : Fixed.

[karajorma]

I'm sure people are downloading, but we need some feedback that it works!

[Hardcover]

Created an account so I could tell you that the patch does indeed work insofar as I can tell. Also that you guys did a frakking awesome job. So much so that I'm thinking I need to find (and/or replace in all probability) my BSG double tanks so I can wear them while I play this.

[Caladus]

Still having issues in the refueling mission. It's a straight crash to desktop. I have to 'kill' the process using the launcher. The error message is a VB runtime error and seems to happen right when the Indark is done fueling the Thesus for one jump.

[karajorma]

Does the debug version give you any messages? Can you post the fs2_open.log you'd find in your data folder after running it?

[ThePsuedoMonkey]

Did a full run-through (in Ubuntu!) just now.  One attempt at M2 had no collisions between my viper and the basestar, rounds from Theseus seemed to be fine.  One crash during the bonus/rescue mission, and three during M6 (exit status of -1).  After making the debug build, M6 did not crash    (log here).
Are the flak clouds supposed to be so square-ish?  It seemed like the raiders collide with Theseus more frequently.  I must say that the debug build is much better now, but I wonder if that is just a difference between my two systems.

[raging_ninja]

I'm not sure if something strange is going on - I installed the patch to the Diaspora folder, and it now includes R1.04_Patch.vp. However, when I go to the launcher the only options I see in the Profile Management section are: Default, Diaspora, and Diaspora_1_0_3. How do I know for sure that I'm playing using 1.04, where is there a version number I can check?

[karajorma]

I probably should have named that profile 1_0_3+.

If you have the 1.0.4 VP and don't have 1.0.3 in there any more, you're definitely upgraded.

[raging_ninja]

I probably should have named that profile 1_0_3+.

If you have the 1.0.4 VP and don't have 1.0.3 in there any more, you're definitely upgraded.

Cool, thanks very much.

[Ringmasta]

I'm having issues downloading the update for the game. It starts, and just before it finishes it crashes saying network error I've reset all my networking and even dmzed and open all the ports on my computer yet the error still happens. I've been playing the first one where the game ends were you meet the galatica and haved played through it a few times. Any suggestions on getting this update to actually download??? 

[karajorma]

Well the patch doesn't add any more missions, it just fixes any bugs in the ones that exist. I can't do it but maybe someone can put the patch on another server for you.

[Nuke]

the fs2_open_Diaspora_R1.exe from the 104 patch is being called a trojan by avg, however the build that comes with the installer (or any other freespace build) does not. i have tried re-downloading the patch and i get the same results.

[General Battuta]

It's a false positive.

[karajorma]

Seems like a false positive to me too. MSE can't find anything wrong with the files I packaged up.

If anyone has AVG too (we talked on IRC, I'm not psychic), can they give it a try.

[Echelon9]

Or try uploading it to a suite of AV products to see if it's being picked up by more than one.

https://www.virustotal.com/

[Nuke]

yea was false positive. dont know why, no other freespace builds have done that, and the build from the main installer didnt do that either (not to mention a 203k difference in file size), and i didnt see any posts about it. so it really set off a red flag for me. kara gave me a hash with which to verify the exe, and that passed. and i ran played through with no ill consequences.

i was very impressed with the mod, really like the polish on the hud and rtt stuff. makes my old scripts look rather crude. i like the fact you went with a moving lead indicator, i was curious if that was scripted or part of the new hud system.

[VulcanRidr]

This is probably a dumb question, but I followed the instructions in the README. Is it indicated anywhere in any of the screens that I am running 1.0.4? My profile management in the launcher only has options for Diaspora and Default, and at the bottom of most of the screens, it only indicates the fs2_open version (3.6.13).

Edit: More grim news...I went into Mods in the launcher, and when I clicked Info for Shattered Armistice, It says "/data/Diaspora_R1_Linux/Diaspora/(No mod)" and at the bottom, "Also known as Diaspora : R1"

Did I miss a step somewhere? I untarred the Patch_Files.1.0.4.tar to /data/Diaspora_R1_Linux/Diaspora, rebuilt fs2_open and the launcher, doing make clean on both, and my patches directory has

Code: [Select]

[storm@defiant Diaspora]$ ls -l patches
total 320
-rw-r--r-- 1 storm storm    930 Nov 10 02:28 ai_bug_fixes.patch
-rw-r--r-- 1 storm storm   4908 Sep 10 21:46 bug_fixes.patch
-rw-r--r-- 1 storm storm   1440 Nov 10 02:28 changes_from_trunk.patch
-rw-r--r-- 1 storm storm 133673 Sep 10 21:46 colonial_hud.patch
-rw-r--r-- 1 storm storm    447 Nov 10 02:28 commit_9263.patch
-rw-r--r-- 1 storm storm 155914 Nov 10 02:28 commits_from_trunk_9124.patch
-rw-r--r-- 1 storm storm   1475 Sep 11 23:20 mantis_2711.patch
-rw-r--r-- 1 storm storm    552 Nov 10 02:28 more_ai_fixes.patch
-rw-r--r-- 1 storm storm    906 Nov 10 02:28 no_multi_autoaim.patch

and R1.0.4_Patch.vp exists in the Diaspora directory.

Thanks,
--vr

[karajorma]

Sounds like you're running it correctly.

In the future we'll try to see if we can get the game to identify itself better.