Buggy stock scenario - Standing Naval Force Atlantic

[simovitch]

I searched the forum and didn't see anything on this - but when I start the scenario several error messages appear about placing subsurface contacts, and then one of the task forces relocates deep into the Norwegian fiords, and the other circles around waiting for a path when one is clearly present, and ignores my F3 commands to move it anywhere.

Any insights? playing with most current version to date.

standing naval force atlantic, 1979.jpg (180.32 KiB) Viewed 468 times

[simovitch]

Tried this scenario again with the new 18.1 and it's still broken. Except for the at-start errors above, the scenario seems to run fine until about 1minute into the scenario. Then the STANAVFOLANT TF instantly relocates hundreds of miles into the fjords and the Iwo Jima ARG gets confused about it's straight line plotted course and wanders aimlessly.

Both task forces have the "waiting for pathfinder generated course" status and are unresponsive to my F3 plot attempts.

I would just move on with my life if this was someone's abandoned 3rd party scenario but since it is a stock "stand alone" scenario I thought I would bring it up (again) with the hopes that it would at least be a verified bug.

[Nikel]

What did you have to do to reproduce the bug initially, just running the scenario?

And where did you get the v1.1, steam?

[simovitch]

Sorry, version 18.1 downloaded from Matrix (my "8" key sticks sometimes...)

Yes, just start the scenario and let it run at 1X for a minute or so.

[Nikel]

I see.

It was said 18.1 was only to fix duplicated scenarios, so besides some scenarios got a fix, probably the ones where Kushan posted, though he did not post in this thread.


Asked because just run it for 15' and did not happen here.

[simovitch]

I see.

It was said 18.1 was only to fix duplicated scenarios, so besides some scenarios got a fix, probably the ones where Kushan posted, though he did not post in this thread.


Asked because just run it for 15' and did not happen here.

OK thanks for checking - I'll look into it on my end.
UPDATE: This must be system related because this scenario works fine on my desktop. This issue can be closed. Thanks for the support!