Donald Douglas

When setting a Preselect speed in the PERF CLB page, it seems to respect it (per the FMA) but as soon as you enter climb mode, it gets replaced/overridden by the Managed FMS speed.

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.

🤷‍♂️ Just tried again with 1.0.3a and most current BATC Experimental (with no changes to UAC/Admin, etc) and it worked this time. Ha, beats me, but glad! Thanks for your help in trying to resolve it.

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?

Nope. Still broken. CPDLC source set to BATC: BATC version 1.6.75 Experimental (which was just released today/last night, by the way) INIT A completed: Clearance Request Composed and sent to DCDU: Sent to and received by BATC and BATC sends response: No messages received on flight deck:

I had already done everything you are suggesting, down to the letter-- multiple times, but would never get the response onto the DCDU. I have not attempted since 1.02, but will try again now.

huh?

Hi- the entire sim froze— no movement, no keystrokes, no menus— had to kill it in task manager.

Scenario: Have Simbrief initialized flight in MCDU. During Climb, Press INIT, the WINDS softkey, then attempt to remove the first climb wind by pressing CLR and then LSK1L. Sim freezes, no error message but have to kill via task manager.

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.

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.

I figured, just thought I'd send as much data as I could. I've only had the one issue so far 🤞

Just repeated the exact same scenario and had no issue so 🤷‍♂️

WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005 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

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.