Jump to content

Donald Douglas

Member
  • Posts

    18
  • Joined

  • Last visited

Posts posted by Donald Douglas

  1. Departing FWKI, I had an NADP2 scenario where I hard keyed THR RED at 1500 agl (5500 MSL in this case) and ACC at 3000' AGL (7000 MSL)-- however, upon reaching Thrust Reduction, the aircraft began to accelerate immediately.

  2. I left it running almost 30 minutes while I composed these responses.  

    I've already reported this to BATC, they indicated it was an inibuilds issue.... and, why would this work for me for the iniA350 and not the A340?  If this was a BATC issue, or a communications issue, wouldn't it be evident globally??

    I have the A340 installed locally (ie: not streamed) if that matters...Neither MSFS or BATC run with Admin rights.  What is the difference or conflict here from my system to yours?

    @MMAACCXX Are you still having this issue?

     

     

     

  3. Nope. Still broken.

    CPDLC source set to BATC:
    Screenshot2025-11-06144911.png.af399db1b75723a9c516a34b810132d9.png

     

    BATC version 1.6.75 Experimental (which was just released today/last night, by the way)
    Screenshot2025-11-06145033.png.5e3dc6a79d565b37d2486dac122cc0ec.png

    INIT A completed:
    Screenshot2025-11-06145417.png.24d073d93fb510738fc9523945bc0f9a.png

    Clearance Request Composed and sent to DCDU:
    image.png.1eb6fb4f58fcca763c75f981f18daffe.png

    Sent to and received by BATC and BATC sends response:
    Screenshot2025-11-06145618.png.086411f814c3a68b9a6a82ce24dbcd2a.png

    No messages received on flight deck:
    image.png.bbcee65545bebaa62301e05071cf2cea.png

  4. When I hard tune a navaid on the RAD NAV page, I thought the font was supposed to be large to differentiate a hard, pilot tuned station from an auto tuned one.  I also really thought it acted this way prior to the 1.02 update, but I could be totally wrong there.

  5. I've done this a few times, but I entered the Navaid ID and not the frequency-- you may have to precede it with a "/"  like "/112.3" if you are entering a frequency only-- that is definitely true with the ILS hard tune entry.

  6. WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005

    image.thumb.png.edc424b158c0b73b8a2c07bffc1a4c18.png

     

    Stopped short of runway, set parking brake, turned off taxi and turnoff lights, then about 1 minute later released parking brake, turned on turnoff and taxi/TO, strobe, wing, and landing lights-- noticed no lights and realized was WASM crash.

     

    A340 EIS 1 Passenger

    FS2024

    Navigraph Navdata

     

    OFP attached except was modified to runway 33L TORK1C departure

     

    Specs: Ryzen 7 5800XCD, Nvidia RTX4070 Ti Super, 32GB Ram

    No autosave in the directory for this flight.

     

    OERKLKPR_PDF_1760296321.pdf

  7. I just left Riyadh (2000 msl) at 36C and only about 195T-- Flap 3 Flex 53-- no issue getting off the runway and initial climb was fine, but I definitely barely made the above FL230 SID restriction almost 60 track miles away, and this was with no intermediate level segments, and I was speed restricted to 250 until around 13k feet.  So I think, yes, it might be pushing harder on takeoff than some airlines did irl, but overall it's climb performance is still pretty realistic.

    • Like 1
  8. When I use CPDLC for clearance request in the ini A340, I can send the request,I see it in BATC, then see the response in BATC, but it never comes to the flight deck, so there's no way to respond or acknowledge it.  This seems to work fine in the A350.

    • Like 3
×
×
  • Create New...