[WAD] Fighters dis-engaging after reloading from a save game (Full Version)

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support



Message

Airborne Rifles -> [WAD] Fighters dis-engaging after reloading from a save game (8/26/2016 12:48:18 AM)

I noticing an odd behavior and I'm not sure if it's because of the way I play or actually a bug. I've noticed before that if I save a game and quit in mid-engagement, sometimes when I load my save the AI aircraft that are engaged offensive against me break off and disengage immediately. I've attached an example of this behavior. In the attached save, when I load there are several Su-27s heading towards my fighters south of USS Enterprise (and a couple already heading north, away from the engagement). Upon loading the save they all immediately turn north and disengage.

Again, this could be a problem with how I play (have to catch snippets here and there when I can find the time). Thanks for any attention!



mikmykWS -> RE: Fighters dis-engaging after reloading from a save game (8/26/2016 4:33:31 PM)

Thanks for the report and file. You took the time so we will! Will let you know if we find something

Mike



Randomizer -> RE: Fighters dis-engaging after reloading from a save game (8/26/2016 7:49:44 PM)

For what it's worth, have noticed that saving during an engagement can sometimes yield odd results when the save is loaded. For example, on one occasion I had launched nine ICBM sorties but then had to exit the game so I saved while they were in flight. When I picked up the game all nine missed or failed, relaunching the strike and playing through without saving yielded expected results. I would not really categorize this as a bug because it does not appear to be consistently reproducible but things like this happen enough that I no longer try to save when guided weapons are active or units on missions are in proximity of hostiles.

To reproduce:

- Any suitable scenario - either DB;

- Launch a salvo of missiles/torpedoes;

- Save, exit CMANO;.

- Start CMANO, load save, observe the weapon behavior.

Edit: To clarify, noted this in v 1.10 and earlier but have not tried with v1.11 SR4.

-C



Schr75 -> RE: Fighters dis-engaging after reloading from a save game (8/26/2016 8:14:54 PM)

Hi Airborne.

Looked at your save, and from the sov side all your units are outside their prosecution zone.

I don´t know all the mechanics behind the prosecution zone, but perhaps if your units enter the zone and get engaged and you then save and your units leave the zone, the re-load will not evaluate your units as entered the prosecution zone.

Just my thoughts.

Hope this is usefull.

Søren



[image]local://upfiles/49421/4B08634E0D3C45C694AE846BDBA16783.jpg[/image]



ComDev -> RE: Fighters dis-engaging after reloading from a save game (8/26/2016 8:59:02 PM)

Thanks for the save, gave it a spin [8D]

I load the save, press play, and the aircraft disengage and head back to their patrol area. The contacts go 'Uncertain' and their uncertainty zones grow. The RWRs soon become the most accurate sensors, and based on the 'spike', the contacts are evaluated to be very near or inside the prosecution zone. The Flankers head off to intercept, their radars locate the contacts outside the prosecution zone, but they keep chasing the target for a bit in case it should turn towards the zone, and then they disengage.

When you load the scenario, they don't bother starting the chase and just disengage if the target seems to be too far away and there is no recent history on the contacts. Which probably makes sense?



ComDev -> RE: Fighters dis-engaging after reloading from a save game (8/26/2016 9:00:41 PM)


quote:

ORIGINAL: Randomizer

For what it's worth, have noticed that saving during an engagement can sometimes yield odd results when the save is loaded. For example, on one occasion I had launched nine ICBM sorties but then had to exit the game so I saved while they were in flight. When I picked up the game all nine missed or failed, relaunching the strike and playing through without saving yielded expected results. I would not really categorize this as a bug because it does not appear to be consistently reproducible but things like this happen enough that I no longer try to save when guided weapons are active or units on missions are in proximity of hostiles.

To reproduce:

- Any suitable scenario - either DB;

- Launch a salvo of missiles/torpedoes;

- Save, exit CMANO;.

- Start CMANO, load save, observe the weapon behavior.

Edit: To clarify, noted this in v 1.10 and earlier but have not tried with v1.11 SR4.

-C


Hmmm I'm not seeing this in the latest version... guys anyone else seen this in v1.11 or later?

Thanks!



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.78125