Matrix Games Forums

Greetings. This is not a "game issue" ie. big...it is in this scenario and I could not find a more fitting area to ask help.

This scenario has a CTD every time, within a couple of (game time) seconds of this save...usually at the xx:xx:28 or 29 point while I think this save is at the xx:xx:22 second mark.

Yes the AU count is very high, but minutes before this, it was much higher. A major land engagement just ended (game) minutes ago, and the very last phase of a NATO missile strike is near its end, as well as a major air battle...so about 15 (game) minutes ago it was running slowly but fine, with hundreds more AU count.
Something seems to trigger a period of "thinking" in the next moments after this save, in 9 consecutive run-throughs in the next few seconds here, then CTD Everytime.

Hi, thanks for the report. The exception log doesn't record any errors but I have been able to reproduce this. Have you tried playing the scenario again?

Is it the same bug, posted by scott1393?

https://www.matrixgames.com/forums/view ... 0&t=402072

Raptorx7_slith wrote: Mon Mar 04, 2024 6:09 pm Hi, thanks for the report. The exception log doesn't record any errors but I have been able to reproduce this. Have you tried playing the scenario again?

Yes the other iterations have played just fine ...when I create a scenario I run it through dozens of test runs, changing small things until it feels right...so this particular one was changed in the next trial run, mostly by the removal of one of the NATO bases in Florida and 1 fewer NATO ship, and a few less VZ aircraft. All of those and more, however, were in earlier tests that also ran fine

Please disable the scenario feature "Terrain Type Effects - Advanced" RIGHT NOW.

Dimitris wrote: Tue Mar 05, 2024 10:05 am Please disable the scenario feature "Terrain Type Effects - Advanced" RIGHT NOW.

Thank you D.
Is that feature broken? I usually run it since it became available in any scenario that will interact with things such as terrain cover.

I think the OP CTD has been fixed in B1328.17, can you confirm ?

Yes it seems fixed, thank you.