• Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum

Occasionally, on startup, engine gauges only partially turn on or sometimes not at all

Scheduled Pinned Locked Moved RJ Professional
40 Posts 20 Posters 2.7k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • MartynM Offline
    MartynM Offline
    Martyn JF Staff
    wrote on last edited by
    #17

    Thanks all for the continued information on this. We are working hard to identify and fix the issue.

    Martyn - Development Manager

    1 Reply Last reply
    1
  • sg_aviationS Offline
    sg_aviationS Offline
    sg_aviation
    wrote on last edited by
    #18

    Same here in v1.2 and powering up loading TURNAROUND state. Resolved only after restarting flight, then loading TURNAROUND state twice.

    1 Reply Last reply
    0
  • T Offline
    T Offline
    TimVS
    wrote on last edited by
    #19

    I can confirm the same experience. The workaround for me is restarting and activating turnaround state on the efb 2 or 3 times until the engine displays show as normal

    1 Reply Last reply
    0
  • GADGETFPVG Offline
    GADGETFPVG Offline
    GADGETFPV
    wrote on last edited by
    #20

    Had exactly the same happen to me on my first flight (MSFS2020) (bought the aircraft today)... no engine guages... had to restart the flight... but when it works, what a beautiful aircraft...

    1 Reply Last reply
    0
  • BBoaBrimB Offline
    BBoaBrimB Offline
    BBoaBrim
    wrote on last edited by
    #21

    I had this happen to me today for the first time. I was still able to start the engines up and am currently mid-flight.

    1 Reply Last reply
    0
  • MarkM Offline
    MarkM Offline
    Mark JF Staff
    wrote on last edited by
    #22

    Hi all,

    Just to clarify a few points as I suspect there may be some confusion in this thread where the expected aircraft behaviour is being mistaken for a bug.

    When loading into the aircraft cold and dark, it is expected behaviour that only the N2 and EGT displays are illuminated on the PED (see attached screenshot). In that state, the aircraft is at the 'Essential Power Level' and electrical power is being supplied only by the aircraft's batteries. In order to preserve the battery's charge, only the most important systems are powered in this state. The rest of the PED displays will power on once the APU or GPU is connected and powering the aircraft.

    PED - Essential Power Level.jpg

    However, we have been made aware of an issue which is causing only the N1 displays on some engines to appear after switching on the batteries. This isn't intended behaviour and is something we are actively investigating. We suspect this may be battery voltage related, and waiting for an extended period on the ground without the APU or GPU connected is causing the battery to drain, causing this issue.

    If you switch on the batteries with only the N1 displays illuminated, we would recommend ensuring that "State Saving" is disabled on the EFB and then restarting the flight. That will ensure the battery voltage is at its maximum value when loading into the next flight and as long as the batteries are powered on within a reasonable time frame (approx 5 minutes) then the PED should display the correct format. A more permanent solution is being worked on for the next update.

    Mark - Just Flight

    Just Flight Development Assistant

    BBoaBrimB 1 Reply Last reply
    2
  • BBoaBrimB Offline
    BBoaBrimB Offline
    BBoaBrim
    replied to Mark on last edited by
    #23

    @Mark said in Occasionally, on startup, engine gauges only partially turn on or sometimes not at all:

    We suspect this may be battery voltage related, and waiting for an extended period on the ground without the APU

    I concur with the thought above.

    Usually when I get into the aircraft I start the electrical system up (batteries and APU) immediately. This time I got into the aircraft and was distracted for 10-15 minutes before I attempted start up. This was when I experienced only the N1 dials being lit.

    1 Reply Last reply
    0
  • MartynM Martyn referenced this topic on
  • GADGETFPVG Offline
    GADGETFPVG Offline
    GADGETFPV
    wrote on last edited by GADGETFPV
    #24

    So I noticed that I get no engine guages when I am preparing for my stream... the aircraft is sat on the apron, in a Cold and Dark state for about 30 minutes... When I start switching stuff on, the guages don't illuminate at all, then I have to restart... happened to me three times (streamed the aircraft 3 times)... off stream when I enter the aircraft immediatley and start switching stuff on, no issues...

    S 1 Reply Last reply
    0
  • S Offline
    S Offline
    SteveKane
    replied to GADGETFPV on last edited by SteveKane
    #25

    @GADGETFPV I think I've seen the same thing. Guessing "cold and dark" is still using up battery. So best to make sure we fire up APU or connect Ground power quickly after starting up a session.

    1 Reply Last reply
    0
  • J Offline
    J Offline
    Jasemelbo
    wrote on last edited by
    #26

    Getting the same issue here. I need to restart the aircraft to have those gauges appear. Starting up the APU quickly or ground power does not solve the issue.

    1 Reply Last reply
    0
  • K Offline
    K Offline
    kiwipilot77
    wrote on last edited by kiwipilot77
    #27

    mine is different - loading on ramp cold & dark or on runway - ALL instruments turn off within seconds, a partially visible PILOT's microphone sneaks up like a snake, the EFB is gone completely. Can post a video if you like. Creepy but makes this master piece unusable. Was working perfectly fine yesterday and earlier today - I have not changed any settings, updated Navigraph to the latest cycle etc. What is going on?

    Edit: here is a short video https://www.youtube.com/watch?v=H_1C2dXGSB0

    1 Reply Last reply
    0
  • G Offline
    G Offline
    Goochie
    wrote on last edited by
    #28

    Please don't blame the users for this problem. I have carefully followed the checklist from cold and dark through to engine startup and confirm what everyone is saying here. Hoped V1.2 would fix this but it hasn't. Restarting is not the solution. Please fix this bug. Thank you.

    MartynM 1 Reply Last reply
    -1
  • MartynM Offline
    MartynM Offline
    Martyn JF Staff
    replied to Goochie on last edited by Martyn
    #29

    @Goochie Users haven't been blamed and we've confirmed above that this is a bug that we are investigating. Until a fix is found, please make sure to establish electrical power ASAP after starting a flight, ideally the APU or EXT AC.

    Martyn - Development Manager

    BBoaBrimB 1 Reply Last reply
    1
  • BBoaBrimB Offline
    BBoaBrimB Offline
    BBoaBrim
    replied to Martyn on last edited by
    #30

    I was just about to post a reply to this “don’t blame the users”. What an utterly ridiculous notion to suggest that JF are blaming us. They’re absolutely not!

    G 1 Reply Last reply
    1
  • G Offline
    G Offline
    Goochie
    replied to BBoaBrim on last edited by
    #31

    @BPFonteyn Take it easy. If you read the posts you will see that early on the responses from JF were to look at different things we were doing. Fortunately there were plenty of others contributing their experiences, enough to show this was not a user problem. Quite often, the first thought can be the user is doing something wrong. We have got past that point.

    1 Reply Last reply
    0
  • BBoaBrimB Offline
    BBoaBrimB Offline
    BBoaBrim
    wrote on last edited by
    #32

    Nonsense! I stand by what I said.

    1 Reply Last reply
    2
  • J Offline
    J Offline
    Jasemelbo
    wrote on last edited by Jasemelbo
    #33

    This isn't JF's first rodeo. I have these issues as well however they will find a fix and let us know. I have also just posted about missing speeds on the HSI, could be related. It's gonna be okay.
    Jase

    1 Reply Last reply
    0
  • A Offline
    A Offline
    Adsm88
    wrote on last edited by
    #34

    Discovered it after all the preparations and checks were conducted and when reading the checklists. After calling maintenance, the problem could not be solved without aircraft change. Due to crew over duty the flight had to be canceled. Until a fix will be found by the maintenance the AC will be grounded. As I am be off I will be home playing MSFS A320 or 777.

    1 Reply Last reply
    0
  • MartynM Offline
    MartynM Offline
    Martyn JF Staff
    wrote on last edited by
    #35

    Hi all. We believe that we have now tracked down and fixed the issue, which will be included in the v1.3 update.

    Martyn - Development Manager

    BBoaBrimB 1 Reply Last reply
    4
  • BBoaBrimB Offline
    BBoaBrimB Offline
    BBoaBrim
    replied to Martyn on last edited by
    #36

    @Martyn Great news. Good work JF! 👍

    1 Reply Last reply
    1

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users