CTD After Turning on Battery in Carenado Skymaster

ISSUE DESCRIPTION

Description of the issue:

I load C&D into the Skymaster at KPRB. I turn on the battery and the sim CTD.

Fault bucket 1453051775756891120, type 5

Weather settings:

Live

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

Every Time

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Load C&D in Skymaster
  1. Click on Battery switch
  1. CTD

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

All mods disabled save for the Skymaster

What peripherals are you using:

[PC Only] Are you using Developer Mode or have you made any changes to it?

No

[PC Only] What GPU (Graphics Card) do you use?

GTX 1060 Max Q

[PC Only] What other relevant PC specs can you share?

Intel i7-8750H

MEDIA

Please add a screenshot or video of the issue occurring.

This is also occurring on my primary sim-rig PC.

Something has changed within the SDK, I presume?

Confirmed here.

CTD on switching on the battery when Cold & Dark has also been observed (by @Bondjpf and myself) in the Iris Simulations PC-21. So the bug is likely to affect more than just the Skymaster.

Bondjpf also reported a CTD in the PC-21 on a runway start, which I haven’t tested.

Edit: Have now tested the PC-21 on a runway start. It instantly CTD’d.

Also CTDs in the Skymaster when turning on the battery while C&D, and again instantly on a runway start.

Further edit: Checks repeated with the same outcome with an empty Community folder in the case of the Skymaster, and only the PC-21 present (bought directly from IRIS Simulations) when checking it.

1 Like

It seems very likely that this is the same bug as reported in

@Bondjpf reports:

As I replied, you shouldn’t have to do that to start an aircraft, but perhaps this will help to point to the source of the problem.

This appears to have been rectified with 1.6.11.0.

1 Like

Can confirm.

1 Like