Med Conflict changes and lock up

[djoos5]

Hey Devs,

I hope you can give me some insight as to how I broke my scenario I wrote. Let me explain first by saying the changes made:

• Corrected Strike Mission settings for Soviets
• Changed briefing and scenario description
• Changed position of targets and reference points to Libya instead of Algeria
• Changed the name of all Tripoli airport units to include the name 'Tripoli"
• Changed active status on a few of the WP missions and gave some a timed start
• Changed positions and stations of ships in US fleets
• Added more helicopters to US ships
• Changed the number of days the scenario will span
• Added PFCG's to Libyan coastal defense and added them into the ASuW patrol mission

I think that was everything.

The scenario used to run fantastic on Build 507 and then 517 before my changes. I don't think I ran the original scenario before my update to Build 519. Anyway, now when I hit start on the scenario it moves slow (especially when set to 5x speed) and finally locks up. I just tried it again and I received the following notice in the attached image. I have included the Scenario zip.

Thanks for any help on what I need to do to fix it. Once done, I can resubmit to Miguel so that he can swap it out of the Custom Scenario folder.

[djoos5]

Here is the crash pic.

[mikmykWS]

Just looking real quick it seems like there are many ships that are engaged offensive at game start but no visible targets. Can you think of any reason for this state?

Mik

[djoos5]

None that I know of, Mike.

Are the ships on the US or Soviet side?

[djoos5]

I guess I am going to have to re-build this scenario from scratch. As I made my updates and changes, I overwrote my work to save it and so no longer have the original file.

Oh well, it will give me chance to re-look at all of the components I put in it.

[mikmykWS]

You can use the import functionality to copy stuff and then re-import it back in to a new scenario.

Mike

[djoos5]

Cool, thanks for the help on the re-import. I won't be copying anything broken, right? I mean from the error report above, it is not a specific ship that is broken, is it?

[mikmykWS]

No it grabs the id's not the actual unit.

Mike

[djoos5]

Just running tests on my game and I got this one.

[djoos5]

Running my test, Mike, I see where there are a lot of the surface ships running Engaged Offensive, on both the NATO (allied) side and the Soviet (WP). The US ships are not.

I am assuming from your statement above that this can be a memory hog, but what would cause the ships to all go Engaged Offensive? I have the PCFG doing an ASuW patrol Mission, the subs doing a Sea Control Mission - should they AI side vessels not be put in these kind of missions?

Let me know when you get the chance. I am attaching another copy of my edited scenario.

[Dimitris]

Can you check again for crashes with B546? Thanks!

[djoos5]

Hey Suburn,

I will but it'll be a few days until I can test - I am currently in Florida. I will have a response up next week.

[djoos5]

I'll be honest though, I haven't seen this crash again since. I am up to revision D of the scenario and I need to do some changes recommended by Mike (I.e. database update, setting up prosecution areas for SAMs) but otherwise it has been working well. Still, I will give you an update when home.

[mikmykWS]

Just check and it does reoccur. Logged and we'll check it out.

Mike

[Dimitris]

Unable to reproduce crash in Build 547.