Mismatched mission results

AndyLorentz · 06-23-17, 11:10 PM

I downloaded 1.04b this evening, and I'm getting "failed mission" debriefs in the campaign on every mission, regardless whether I succeed or fail, but the news reports are correctly reporting based on success or failure.

Anyone else seeing this?

PL_Harpoon · 06-24-17, 05:31 AM

Yes. Happens to me too.

USSCheyenne · 06-24-17, 11:35 AM

I don't know if it's been clarified before but i hope that mission succes doesn't mean i have to fulfill 100% of the orders. I mean if i sink 2 out of 3 primary targets, it should count as some succes and not a failure. Now it's everything or nothing. That shouldn't be the case.

AndyLorentz · 06-24-17, 12:35 PM

I don't think that's the issue, since it would happen even if I sunk everything in the mission.

That said, the problem seems to have gone away after starting a new campaign. The bug occurred for me in a savegame from 1.03.

Full disclosure: I started a new campaign because the commies won.

Killerfish Games · 06-25-17, 01:14 AM

There is/was definitely a bug with failed radio messages, but the correct win event follows.

We've not been able to reproduce it, but it might be related to some bad tags in some mission files. Not sure if fixing these tags have resolved it, or if there is another cause.

To win a mission you must sink 50% or more of the "mission critical" vessels for that mission.

PL_Harpoon · 06-25-17, 04:34 AM

In my case, just like with AndyLorentz it seemed to be the case of 1.03 savefile running on 1.04.
Saving the campaign in 1.04 and reloading it fixed the issue.

max-peck · 06-26-17, 03:15 PM

Yeah - I have just had this
Started a new campaign - running 1.04b

Was tasked to intercept a landing force

Sunk the following
2 x Kanin
1 x Kara
1 x Aligator
2 x Ropucha

Damaged a freighter (Amguema I think?)

Command told me that they were disappointed I failed to intercept the landing force

But the very next news item told me that the seaborne invasion of Norway had been stopped.

SO - it seems as if the campaign recognises that I succeeded, but the message from high command does not

FPSchazly · 06-26-17, 03:27 PM

Quote:

Originally Posted by max-peck

Yeah - I have just had this
Started a new campaign - running 1.04b

Was tasked to intercept a landing force

Sunk the following
2 x Kanin
1 x Kara
1 x Aligator
2 x Ropucha

Damaged a freighter (Amguema I think?)

Command told me that they were disappointed I failed to intercept the landing force

But the very next news item told me that the seaborne invasion of Norway had been stopped.

SO - it seems as if the campaign recognises that I succeeded, but the message from high command does not

To be fair, those aren't mutually exclusive events. I'm not sure if the game models it this way, but it could be true that one fails to sink all ships of a landing force at moment X (mission completion), but other "forces" still repel the landing at moment Y (some time after mission completion).

max-peck · 06-26-17, 04:01 PM

Quote:

Originally Posted by FPSchazly

To be fair, those aren't mutually exclusive events. I'm not sure if the game models it this way, but it could be true that one fails to sink all ships of a landing force at moment X (mission completion), but other "forces" still repel the landing at moment Y (some time after mission completion).

I hadn't thought of that

Good point mate

wathomas777 · 06-30-17, 05:25 PM

Quote:

Originally Posted by max-peck

Yeah - I have just had this
Started a new campaign - running 1.04b

Was tasked to intercept a landing force

Sunk the following
2 x Kanin
1 x Kara
1 x Aligator
2 x Ropucha

Damaged a freighter (Amguema I think?)

Command told me that they were disappointed I failed to intercept the landing force

But the very next news item told me that the seaborne invasion of Norway had been stopped.

SO - it seems as if the campaign recognises that I succeeded, but the message from high command does not

I don't care where you come from, if you can single handedly deliver that much tonnage to the bottom of the ocean in a single engagement, that's a win in my book.

Aktungbby · 06-30-17, 06:10 PM

wathomas777!

after along 13 year silent run!

max-peck · 06-30-17, 06:24 PM

Quote:

Originally Posted by wathomas777

I don't care where you come from, if you can single handedly deliver that much tonnage to the bottom of the ocean in a single engagement, that's a win in my book.

Well that's what I figured

The game did not agree though

wathomas777 · 06-30-17, 06:31 PM

Quote:

Originally Posted by Aktungbby

wathomas777!

after along 13 year silent run!

It's been 13 years since there was a modern subsim worth playing

06-23-17, 11:10 PM	#1
AndyLorentz Swabbie Join Date: Jun 2017 Posts: 10 Downloads: 3 Uploads: 0	Mismatched mission results I downloaded 1.04b this evening, and I'm getting "failed mission" debriefs in the campaign on every mission, regardless whether I succeed or fail, but the news reports are correctly reporting based on success or failure. Anyone else seeing this?

06-25-17, 01:14 AM	#5
Killerfish Games Cold Waters Developer Join Date: Aug 2012 Posts: 274 Downloads: 0 Uploads: 0	There is/was definitely a bug with failed radio messages, but the correct win event follows. We've not been able to reproduce it, but it might be related to some bad tags in some mission files. Not sure if fixing these tags have resolved it, or if there is another cause. To win a mission you must sink 50% or more of the "mission critical" vessels for that mission. __________________ Visit Killerfish Games for more info and ongoing discussion.

06-26-17, 03:15 PM	#7
max-peck Grey Wolf Join Date: Jun 2011 Location: UK Posts: 752 Downloads: 393 Uploads: 0	Yeah - I have just had this Started a new campaign - running 1.04b Was tasked to intercept a landing force Sunk the following 2 x Kanin 1 x Kara 1 x Aligator 2 x Ropucha Damaged a freighter (Amguema I think?) Command told me that they were disappointed I failed to intercept the landing force But the very next news item told me that the seaborne invasion of Norway had been stopped. SO - it seems as if the campaign recognises that I succeeded, but the message from high command does not __________________ -------------------------------------------------- Authority should derive from the consent of the governed, not from the threat of force If the only tool you have is a hammer, pretty soon everything starts to look like a nail FOTRS Ultimate http://www.subsim.com/radioroom/showthread.php?t=226270 The future of SH4 - coming to a PC near you soon

06-30-17, 06:10 PM	#11
Aktungbby Gefallen Engel U-666 Join Date: Jul 2013 Location: On a tilted, overheated, overpopulated spinning mudball on Collision course with Andromeda Galaxy Posts: 27,823 Downloads: 22 Uploads: 0	welcome aboard firsttime poster! wathomas777! after along 13 year silent run! __________________ "Only two things are infinite; The Universe and human squirrelyness; and I'm not too sure about the Universe"

06-24-17, 05:31 AM	#2
PL_Harpoon Engineer Join Date: Sep 2016 Posts: 210 Downloads: 21 Uploads: 4	Yes. Happens to me too.

06-24-17, 11:35 AM	#3
USSCheyenne Swabbie Join Date: May 2016 Location: Warsaw, Poland Posts: 9 Downloads: 7 Uploads: 0	I don't know if it's been clarified before but i hope that mission succes doesn't mean i have to fulfill 100% of the orders. I mean if i sink 2 out of 3 primary targets, it should count as some succes and not a failure. Now it's everything or nothing. That shouldn't be the case.

06-24-17, 12:35 PM	#4
AndyLorentz Swabbie Join Date: Jun 2017 Posts: 10 Downloads: 3 Uploads: 0	I don't think that's the issue, since it would happen even if I sunk everything in the mission. That said, the problem seems to have gone away after starting a new campaign. The bug occurred for me in a savegame from 1.03. Full disclosure: I started a new campaign because the commies won.

06-25-17, 04:34 AM	#6
PL_Harpoon Engineer Join Date: Sep 2016 Posts: 210 Downloads: 21 Uploads: 4	In my case, just like with AndyLorentz it seemed to be the case of 1.03 savefile running on 1.04. Saving the campaign in 1.04 and reloading it fixed the issue.