Graeme_77

Report 2429 | 2587 Fixed in v1.3.1, February 08, 2022

Report 2494 Fixed in v1.3.1, February 08, 2022

Report 2527 Fixed in v1.3.1, February 08, 2022

Report 2557 Fixed in v1.3.1, February 08, 2022

Report 2567 Fixed in v1.3.1, February 08, 2022

Report 2561 Fixed in v1.3.1, February 08, 2022

Report 2559 Fixed in v1.3.1, February 08, 2022

Report 2477 Fixed in v1.3.1, February 08, 2022

Thanks Bruce, I'm still spending a lot of time on support and testing with the aircraft, but I'll get the next tutorial video done as soon as possible. It's already a couple of weeks late, so is on my mind!

There should be no state save issue with this. As long as a stab trim channel is powered, the stab should move.

To add, following some extensive conversation, it's possible the flight condition behaviour can be improved. It seems for the single engine shutdown the on-side boost pump switch off should only generate the INOP message on that side, and will stop both pumps from running. We're not 100% as the documentation is pretty poor, and pilots can't simply shut down a real engine in flight!. However, the devs and testers will keep investigating and update where possible. Thanks for the post - a real head scratcher!

Interesting question, and sorry I missed it earlier. Yes, once is most likely expected behaviour and the other definitely is. 1) Fuel pumps. As you can see from the study menu, the boost pumps are not dedicated to a single engine. You have two boost pumps, and they both provide pressure for both engines. They should both run, or both not run. As such, the switches are not really turning the pumps on and off, but rather controlling the automatic logic. When the switches are pressed in, if pressure is lost on the engine driven pump on that side then both boost pumps will run. (So there is always a dual source providing fuel for the engine, one engine pump and electric boost pumps on standby, or both electric boost pumps). By switching off the right side, you are telling the system that despite the fact there is no fuel pressure from the right side engine pump, you don't want boost pumps. It's not happy about this and shows inop for the pumps. I will verify this behaviour with the type rated pilots as despite it being essentially the same check performed on the ground, it does "feel" wrong to me. However, at this point, go into failures, fail the other side primary ejector pump and you'll see the pumps come back to life as you would expect. 2) Ice detection. The ice detectors are not looking at ice on the wing, and are not affected by the wing ice protection. They operate on a cycle of 5 seconds of heat, 55 seconds with no heat and as long as ice continues to build, they will indicate ICE. They are telling you that you are flying in active icing conditions and ice protection is required. As long as you have the 14th stage isol open you'll be protecting both wings.

Thanks Adam, That does seem wrong. Thanks for the detailed report, and don't feel bad about bumping this thread, sorry I missed it first time. I'll add this to the list of issues to investigate.

Hello Paul, Do you have any plugins that could be affecting or hiding ground scenery? (The trucks are effectively scenery, where the cables are part of the aircraft.) Do you have the same issue with the fuelling truck?

Thanks Daniel, That's a known issue, and basically down to how X-Plane handles the popup windows (apparently it doesn't let the software know which is on top, so there needs to be some special code to work around that). The developers are looking for a solution to this issue.

That's a pretty weird issue. Does the "Ground Handling Request" clipboard and passenger ETA "watch" 2D popups work OK in the FBO?

The red blinking box is the position of your hardware levers - if that's not moving then there's either a hardware issue, or something incorrect on the throttle bindings. The fact you can't move the throttles during the preflight check also points to a hardware/binding issue.

The clock local time behaviour is under investigation. As you may have seem, the manuals are pretty weak on details for how local time interacts with GPS regulated UTC time. Will hopefully have more to report in a couple of days. In the mean time, the inside info is nobody ever uses local time, as it's totally pointless. It doesn't have a magic ability to sync to local time for the location, it's just a basic clock! Unless you only fly patterns in your local time zone, it's a bit of a waste of time :-)

Hmm. There shouldn't be any issues from the updates like that. Does it accel to 70 kts normally then just hold there, or does it creep up slowly? With only 1200kgs of fuel it should be going like a rocket!

Yes you should easily be able to put the checklist on the right MFD. Upper Menu button. Pressing the Menu Adv/Data knob in is a shortcut to advance to the next item, which is why it's moving to EICAS, just scroll the checklist and either let the menu time out, or press esc. There isn't a default state. It stores the page configuration in non-volatile memory, so will power up in the state it was powered down.

Reversers: did you have the 14th stage bleed on - that's the thing that usually gets forgotten so the reversers are not able to be powered. Nose Door: needs hydraulic power to close. Did you maybe have it open, then switch off the hydraulics?

Thanks, yes it will keep going until it's finished! Hopefully the handling can be cleaned up.

Logged and fixed as issue 2548, will be in next release.

Thanks. I've been able to replicate the issue. I don't think you're doing anything wrong, so will file as a bug report.

That is odd. Can you please verify you don't have any axis accidentally set to toe brakes? There's not much else we can think of that would cause that. Worth setting 200 kts as the speed target - not related to this issue, but will save you trouble when you get airborne.