Sharing my experience with campaign progression issues

xXNightEagleXx · 11-20-15, 05:08 PM

I just want to share my experience hoping that it might help others.

At first, I've installed this game using the download/installing procedure from uplay. As soon as i started to play, i've realized that i had problem with mission progression showing always as pending even when i had completed it (i would like to point that i never had tonnage bar issues in the tutorial).

Lately, i made a windows 10 clear install and reinstalled the everything back (again using uplay as source), but the problem persisted. This time i pissed off our big friend THEBERBSTER with many question about mission progression, until he suggest me MAMA fix.

The whole MAMA procedure, has shown me that on my computer OSI.EXE (which i was not even aware of its existence) never wanted to start. I fixed that by setting the osi, uplay and sh5 executable files as "run as administrator".
With these actions, osi.exe started with no problem, so i could do the change priority trick that actually worked and i saw mission being set as completed. However, unfortunately for some reason i started to have random CTD without messages.

Before trying to find the source of the CTD and try to fix it, i've just uninstalled the game (preserving uplay and osi as before) and deleted any folder/file related to the previous SH5 installation (just to avoid any mistake that i've might have done in the previous installation/mod/fix).

This time i've installed the game using the CD, which from the beginning has shown a different behavior in the vanilla itself (not even starting without running the executable as administrator). Then i installed TWOS with patch 12 (previously i was using the patch 10/11), leaving anything else as before (as i said above). Before even apply the mama fix, my instinct told me to try the game as it is due to its different behavior. I was so happy to discover that this time everything was working as it should, at the end of each mission date the status changed from pending to finished, and this i archived without mama fix (TDW modification and priority trick).

I hope that it might result on more information to help to find a final solution that works for everyone.
Note that there is a different mission status set when completed between with and without mama fix.

NE

Sorry for any mistake

vdr1981 · 11-20-15, 05:36 PM

You should be aware that with TWoS on board, objectives status (pending, finished, completed) and OSI.exe priority are completely irrelevant until campaign ending date.

Anyway, your experience with strange OSI.exe behavior could be useful for some users...

MaMa · 11-21-15, 04:50 AM

I bring everyone attention to the main issue strictly connected to the OSI application functionality :

In the past, different OS systems, different applications installed and different network settings affected OSI in many different ways so that's why sometimes players didn't experience no problem at all playing SH5. the PC probably automatically gave OSI enough resources to run properly and, on the other hand, many other peoples had it compromised all times depending from it.

My biggest concern when tracking down this SH5 bug was in fact related to why some players were experiencing problems and Others not

... that brought me thinking of resources allocation thus giving Birth to my fix...

Remember that more processes running means more probability to experience issues with OSI, setting it to "real time" is the best way to reduce to minimum the probabilities of failure for this application (so far, on Win7 i have a 100% success with it). Despite this it is not possible to be sure that different OS handles processes in the same way, that's why i asked to test this fix with every possible OS as i can't do it by myself. An other trick is to lower other processes priority but it would be painful to try with every process running

...

One last thing jumped on my mind during these days : OSI is an application downloaded from the UPlay browser. Each time a game is first started after installation it needs to download OSI from the UPlay server (it do not tell us anything of this, good way to interact with players UBI

). Let's hope that Ubisoft is not going to change anything in the future since we may find ourselves in troubles again if OSI is going to be updated without telling anyone as Ubisoft standard code of conduct

... fingers crossed.

Just wanted to share my thoughts with everyone

...

11-20-15, 05:08 PM	#1
xXNightEagleXx Planesman Join Date: Aug 2015 Posts: 182 Downloads: 148 Uploads: 0	Sharing my experience with campaign progression issues I just want to share my experience hoping that it might help others. At first, I've installed this game using the download/installing procedure from uplay. As soon as i started to play, i've realized that i had problem with mission progression showing always as pending even when i had completed it (i would like to point that i never had tonnage bar issues in the tutorial). Lately, i made a windows 10 clear install and reinstalled the everything back (again using uplay as source), but the problem persisted. This time i pissed off our big friend THEBERBSTER with many question about mission progression, until he suggest me MAMA fix. The whole MAMA procedure, has shown me that on my computer OSI.EXE (which i was not even aware of its existence) never wanted to start. I fixed that by setting the osi, uplay and sh5 executable files as "run as administrator". With these actions, osi.exe started with no problem, so i could do the change priority trick that actually worked and i saw mission being set as completed. However, unfortunately for some reason i started to have random CTD without messages. Before trying to find the source of the CTD and try to fix it, i've just uninstalled the game (preserving uplay and osi as before) and deleted any folder/file related to the previous SH5 installation (just to avoid any mistake that i've might have done in the previous installation/mod/fix). This time i've installed the game using the CD, which from the beginning has shown a different behavior in the vanilla itself (not even starting without running the executable as administrator). Then i installed TWOS with patch 12 (previously i was using the patch 10/11), leaving anything else as before (as i said above). Before even apply the mama fix, my instinct told me to try the game as it is due to its different behavior. I was so happy to discover that this time everything was working as it should, at the end of each mission date the status changed from pending to finished, and this i archived without mama fix (TDW modification and priority trick). I hope that it might result on more information to help to find a final solution that works for everyone. Note that there is a different mission status set when completed between with and without mama fix. NE Sorry for any mistake Last edited by xXNightEagleXx; 11-20-15 at 05:29 PM.

11-20-15, 05:36 PM	#2
vdr1981 Navy Seal Join Date: May 2010 Location: Србија Posts: 6,078 Downloads: 581 Uploads: 13	You should be aware that with TWoS on board, objectives status (pending, finished, completed) and OSI.exe priority are completely irrelevant until campaign ending date. Anyway, your experience with strange OSI.exe behavior could be useful for some users... __________________ Best regards... Vecko The Wolves of Steel v2.2.25_SH5 Expansion Pack_Full The Wolves of Steel v2.2.xx to v2.2.25 - Update PDF Install Instructions How to report an issue If You wish to support my work...

11-21-15, 04:50 AM	#3
MaMa Bosun Join Date: Jun 2010 Location: Italy Posts: 69 Downloads: 108 Uploads: 0	I bring everyone attention to the main issue strictly connected to the OSI application functionality : In the past, different OS systems, different applications installed and different network settings affected OSI in many different ways so that's why sometimes players didn't experience no problem at all playing SH5. the PC probably automatically gave OSI enough resources to run properly and, on the other hand, many other peoples had it compromised all times depending from it. My biggest concern when tracking down this SH5 bug was in fact related to why some players were experiencing problems and Others not ... that brought me thinking of resources allocation thus giving Birth to my fix... Remember that more processes running means more probability to experience issues with OSI, setting it to "real time" is the best way to reduce to minimum the probabilities of failure for this application (so far, on Win7 i have a 100% success with it). Despite this it is not possible to be sure that different OS handles processes in the same way, that's why i asked to test this fix with every possible OS as i can't do it by myself. An other trick is to lower other processes priority but it would be painful to try with every process running ... One last thing jumped on my mind during these days : OSI is an application downloaded from the UPlay browser. Each time a game is first started after installation it needs to download OSI from the UPlay server (it do not tell us anything of this, good way to interact with players UBI ). Let's hope that Ubisoft is not going to change anything in the future since we may find ourselves in troubles again if OSI is going to be updated without telling anyone as Ubisoft standard code of conduct ... fingers crossed. Just wanted to share my thoughts with everyone ...