[FIXED][1567.6] Error in scenario

[thewood1]

This one of the AA-13 scenarios I posted. I don't have the save, but if you start the scenario in Flame, you'll get the error once the AA-13 is detected.

Screenshot 2025-03-19 111700.jpg (716.05 KiB) Viewed 382 times

[blu3s]

I can't replicate the fuse in steam version, did you set a custom altitude for any of the units?

[thewood1]

Sorry. Its in the Matrix version. And no on altitude. Just dropped the units in, turned sensors on, and gave a direction.

Just checked in Steam and same issue.

edit: Just ran it on my travel laptop and get the exact same error. So its not the install.

[thewood1]

The original file is an old one I have rebuilt and modded over the years. Was thinking maybe something got corrupted in all the rebuilds. So built this one from scratch. Same issue. Did notice the error seems to happen as the Mig-31's first missile starts to get close to the F-16. If you set up weapons tight on the Mig, no error.

[Raptorx7_slith]

I'm not able to reproduce it either. Post the text of the error here and Ill make sure someone looks at it.

[thewood1]

Its in the screenshot and the log text file.

"19/03/2025 11:16:20 -- Bv1.07 - Build 1567.6 -- Object reference not set to an instance of an object. -- Scen : Baseline AA Testing F16 Su24 -- DB : -- Exception: Object reference not set to an instance of an object.
Stack Trace: at Command_Core.Aircraft_AI.DetermineDesiredAttitudeAndThrottle(Single elapsedTime, Boolean RecalculatePlottedCourse)
Call Stack & Error details:
Error at 100392: "

[thewood1]

Just to clarify.

Tried it on a modded scenario and scratch built scenario

Tried it in Steam version and Matrix

Tried it on two different laptops.

All run on single flame speed and circuit breaker trips as AA-13 is spotted by F-16.

[thewood1]

OK. Tried to narrow it down for you.

In the zip is the error log, the message log, and a save right after the first fuse trips, but before the second one trips.

[Nikel]

This same exception happens running the benchmark (with the benchmark scenario) in B1852.

Just after it has started. Reproducible.

FE.png (23.08 KiB) Viewed 167 times

[Nikel]

If you prefer a save. It is reproducible in this one.

Just after starting it appears the x20. The x400 is later running at double flame.


A second one, smaller save.

[Nikel]

Fixed in B1859.