Campaign objectves

[vonfriedman]

It seems to me that there are now a lot of threads but that the interesting discussions have been reduced this new forum was introduced.
Just to do something, I put a couple of questions.
1) The campaign objectives depend on the level of accumulated OPs or are randomly chosen?
2) Is there somewhere a scenario about the clash on May 15 1917 in the Adriatic that is sometimes called "Battle of the Otranto straits"?

[randomizer]

1. Some objectives may be date sensitive but in general the selection is random. FW would need to weigh in on the specifics.

2. The Stock Otranto scenario (dated 26 May 1917) covers a similar situation to the 15 May action in and around the Straits but some components are absent and the overall situation differs somewhat. There are no submarines for example and the date is off by 11-days. However the surface OOB's are very similar although the action tends to play out differently than the historical battle. The Austrians usually need to fight their way to the Barrage with their cruisers but in the event Horthy attacked the drifter line virtually unopposed in darkness and was intercepted in daylight while escaping.

[Fredrik W]

Moved the post as it hardly had anything to do with problems.

1. It is correct as Randomizer says. Many objectives are active between certain dates, and some have varying probabilities, but within those parameters, they are randomly assigned.

2. The stock Otranto scenario is intended to recreate the battle of the Otranto straits in may 1917. I have never realized that the date was off, my bad in that case. In my experience you usually can reach the drifters unchallenged, but sometimes you have bad luck and run into one of the patrols.

[vonfriedman]

I expressed myself badly. I would like to find another scenario about Otranto 1917 (and Otranto 2) mainly because I can not run these stock scenarios. In fact, the following error message appears immediately: "Access violation at address 004C4AA0 in module SAI.exe. Read of address 0000000C." All the other scenarios run smoothly.

[randomizer]

That is very odd, I have the same downloaded game version with no edits or additions (used for testing submitted saved games) and both Otranto scenarios work as designed. Could you please zip up and submit your copies of the following scenario files as found in the Steam and Iron\Scenarios folder:

2d Otranto.NSC
2d Otranto.txt
Otranto.ENV
Otranto.NSC
Otranto.txt
OtrantoBrief.ENV

I'll run them through my commercial copy of the game to see if the issue can be located.

Thanks in advance.

[randomizer]

Vonfriedman wrote:

I expressed myself badly. I would like to find another scenario about Otranto 1917 (and Otranto 2) mainly because I can not run these stock scenarios. In fact, the following error message appears immediately: "Access violation at address 004C4AA0 in module SAI.exe. Read of address 0000000C." All the other scenarios run smoothly.

Thank you for sending in your game files, unfortunately I was unable to recreate the AV errors that are plaguing you with the two stock Otranto scenarios.

Spent much of yesterday and today's AM (GMT -7) testing your files in my machine and comparing your submitted files with the stock versions that shipped with the game and found zero differences. Having eliminated the scenario files themselves, it is possible that there is a common design that is causing the error messages that you are seeing.  However, the files themselves are identical to those that shipped with the game and both scenarios ran error-free to conclusion in a stock SAI v1.6 game installation.

The cause of your AV errors must be elsewhere.

Both Otranto and 2d Otranto share a number of ship and shore installation designs and if you are only seeing the AV errors in these two scenarios, one or more corrupted design file shared between the two scenarios may account for what you're seeing. If you have made any edits using DesignShip2 or edited the scenario and saved the changes in your Custom Files folder I suggest that you delete (or move) the edited files and try again.  This will allow SAI to use the stock designs, provided none of these have been edited at all.

If you have made no edits try reinstalling the stock designs.  While I do not like to recommend uninstalling and reinstalling SAI v1.00 and then patching to v1.6 using the latest update, it appears that some altered design file or files that are shared between the two Otranto scenarios is likely the root cause of your AV errors.

Sorry that I could not be of more assistance.  Good luck, please keep us posted on how this develops.  Thanks.

[vonfriedman]

Your assumptions are correct. Following your advice I deleted all the custom files generated, since moving them was of no avail, but I get the same error message. I will consider reinstalling. I thank you warmly for your efforts and continued support.