MediumRareBaku

OK thanks

Just what the title says -- I can't seem to get LNAV and VNAV to arm on takeoff. I feel like I used to be able to arm them with of course the takeoff modes (N1/TOGA/HDG SEL) being the active modes through takeoff and then LNAV and VNAV would kick on. Am I just confusing myself against the NGs or is this a limitation in the current state of the FMS that needs to be resolved with the pending rewrite?

I never followed the development of the Challenger with much interest as I am not and have never been all that interested in flying business jets. However, I have a couple friends who have it and really like it, and their enjoyment has given me a little bit of FOMO to where I've considered maybe buying it, but the price tag is steep enough that I'm really just unsure if I'd fly it enough to justify the money. Would you perhaps, given the steep price tag, consider some kind of a demo feature? I've seen a few other developers do it -- JF did it with the BAE 146 and it was super helpful for me to decide that I wanted to buy it. Not sure how big of a deal it is to implement such a thing, but I think if I could install and play with it for like an hour I'd know enough to see if I wanted to get it or not.

Is there a way or IRL correct method that's currently implemented to reset the FMS for a new leg? I can put in a new origin airport on the routes page and that clears out the flight plan, but should the perf pages etc. also zero out again?

https://www.thresholdx.net/news/fixegs The Gdrive link appears to now be dead, says the file is in the users trash. Anyone still have this tucked away somewhere?

Thanks very much for the continued work on the 733. I am excited to see the further developments going forward.

I haven't been able to reproduce it yet myself, but I'll keep trying. P/GVA is, I believe, the Delta Virtual Airlines ACARS program. It's the only thing I have running that would be pulling position reports as far as I know.

currently screen capping this issue in real time as I fly -- I was configuring some things in the menu and I can't remember what I clicked -- it may have been to hide the menu. When I did so, the yoke disappeared, the slider bar on the yoke height setting disappeared, and now the forward panel appears to be a click spot -- 2nd screenshot included showing the mouse cursor as an example -- that disconnects the autopilot so I can't click anything. autopilot panel + pedestal seem to be fine, click spot wise. Any ideas? Log.txt

That video is helpful, Jan. I'll practice with it some more today to see if it will make sense in real time now.

So, speed trim matches what I'm seeing based on when I'm seeing it, but either I wasn't paying attention pre 1.30 when I was flying the 733 or something is different. Is this a new addition? I haven't flown it since the first half of 2019 so perhaps its just bad memory. It makes that whole first phase of flight very awkward for me now in a way I don't remember. Based on your description then, as I take off and am in the process of cleaning up and accelerating, speed trim is going to be putting in nose up trim as I accelerate because it wants me to maintain the old speed. What is the purpose of this, since I'm in a flight phase based on first holding my post-takeoff pitch, and then lowering the nose to accelerate to flying speeds? Why would the plane want me to keep my same speed until I've cleaned up, which in theory I would never be able to do if it trimmed me at the same speed? I've got my dad's old FCOM from the 733/734, so I'm also going to read up on this on my end to try and better understand it.

Using 1.3 in 11.41 with experimental flight model on and beta Gizmo selected. Basically, when trying to hand fly, autopilot fully off, I have uncommanded pitch trim that does not stop. I've double checked my inputs and do not believe I have any axis assignments or conflicting controls that are causing this. It seems to stop if I put pitch up or pitch down commands with the yoke, but resumes when in neutral. I didn't know the -300s had MCAS

Same here, does make some for some awkward brain-reversing when trying to change settings

Hey Jan -- thanks for all that info. Can you expand a little more on waiting for XP12 to patch the FMS? That seems like something that could be a very long ways off, so I must admit to a pang of frustration reading that the FMS update won't be expected until then. Is this because there's an equivalent amount of time needed to actually fix it, or because you guys don't think the FMS is fixable in 11.XX?

+1 please

I definitely struggle with finding a happy place for the pitch axis. It's too sensitive with the default response curve and sensitivity/augmentation settings. I find the pitch generally too sharp/sensitive and also the aircraft seems to want snap back do it's previous pitch angle after making an adjustment. The pitch trim also seems to input too great a change for one click of the trim. Everything else feels pretty good, I think. I'd love to get the pitch handling confidence in the TBM that I have in something like the KA350.