PC-24 Battery Fault SU2

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.


ISSUE DESCRIPTION

Description of the issue:
The battery discharges over time, restricting the length of the flight before the avionics shut down. The generators dont seem to be charging the batter. In addition flickering between yellow and green state exists. Eventually the battery fault appears as the power continues to drop. This is the 3rd flight in succession since the SU2 dropped its happened in.

If applicable, which aircraft is experiencing this issue:
Pilatus PC-24

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
No adds on installed, community folder empty.

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 into Pilatus PC-24.
  2. Do a mission or a free flight.
  3. After about an hour the batteries have discharged enough to get the error on the MCDU.

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.

What peripherals are you using, if relevant:

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

[PC, MSFS 2020 Only] Are you using DX11 or DX12?
DX 12 , MS 2024

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

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

MEDIA


[END OF FIRST USER REPORT]

1 Like

I wanted to update this bug, the battery drain happens when I turn all the lights on from a mapped button either on the keyboard or joystick (flight controller). If I turn the lights on inside the cockpit from the panel above all works fine.

Wierd. Been flying the PC-24 in SU2 and never got this particular problem, I even finished a 2-3h flight just now :person_shrugging:

Nope, this hasn’t happened to me either, and I’ve been doing 3h Missions in Career.

I wonder if that all lights mapping is turning off the Gens. That’s the only way the batteries drain of the engines are still running.

I agree its a really weird one, and I cant fathom the cause, the only mapping I have on the controller when I search is toggle all lights. As long as I dont do that all is well, and just do the lights from inside the cockpit all is well.

Do you use the “skip” feature or start with the aircraft already powered?

I ask because IIRC there was a PC-24 bug related to nose wheel steering when skipping ahead in career mode, maybe this is related because I never skip and start “cold&dark” with fully manual startup.

I dont skip no, and I’ve not tested this yet outside of career mode, but will record a video soon and post.

Here is a video of the issue:

1 Like

Ok, that explains why I don’t have the same problem, I switch the lights on/off individually, either with peripheral switches or mouse clicking.

If I had to guess… there’s probably some hidden electrical switch that gets activated and exceeds the generators capacity.

Next time I fly I’ll try it with that lights command and I’ll give some feedback.

1 Like

Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes.

Provide extra information to complete the original description of the issue:
Switching the lights on with the “TOGGLE LIGHTS” input and flicking landing and logo lights to pulse causes both batteries to flicker “-108A”.

Turning all the lights on manually, even cockpit and cabin lights, doesn’t cause any issues.

If relevant, provide additional screenshots/video:
N/A

1 Like

Many thanks for confirming :+1:

Hi @CasualClick hope all is well. Are you able to confirm you see the same issue and we can probably get this logged as a bug then.

I queued it up with the Community Managers, they’ll take a look. Thanks.

1 Like

Thank you for the bug report.

We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.

2 Likes

Can someone explain how this got logged in only 12 days where we have had issues from the start only just being logged? All the beta testing and bugs reported only a minority of them being logged, some proper game braking bugs just ignored

It’s just “feedback-logged”, not “bug-logged”.

The fuel flow bug, on this same aircraft, was created about six months ago and is still only “feedback-logged”. And that one seems like a pretty easy fix (divide by two).

So, and unfortunately, this is not some major step to solving an issue :slightly_frowning_face:

Once it’s Feedback Logged, it means a ticket was opened to try and recreate it on the responding/fixing team’s side. If it’s a Dev Partner - which in this case is Carenado - it’s on them to address. I don’t really have any more answers than that.

1 Like

See you in 2026 then when it’s fixed :rofl:

1 Like

I think this is Carenado being lazy and copied the PC-12 fuel data being single engine, as they did with the V-speeds, do you know if there’s anyone from the Carenado team on the forum? Maybe we could get an answer off them?

I’m not aware of anyone from Carenado with an active forum account. If they’re here, they’ve not identified themselves as a Third Party Dev for which we have a badging process so their identity can be validated and noted.

Traditionally, Carenado is pretty silent - notably they don’t maintain presences other than Social Media (I’ve only seen their Facebook channel), and they have a Zendesk of their own.

1 Like