Yep, you are correct. It was an unused device. Removing its bindings fixed it. Thanks a lot. I would not have guessed in a million years

@alanfernandes said in Bug? Fuel Burn.: Although fuel flows by gravity from the forward to the aft compartment within the main system during refueling, there is no gravity transfer between the auxiliary and main tanks. In flight, this transfer relies exclusively on jet pumps operated by engine motive flow, which renders the fuel in the auxiliary tanks unusable should the pump system fail. I recall discussing this in one of my videos. Here is what I said in the manual: "Most of the fuel in the aft tanks will transfer to the main tanks by gravity, and the rest can be transferred by the aft tank transfer jet pumps. Should the aft tank transfer jet pumps fail, the total usable fuel may be reduced." Here is what the Flight Safety manual says: "Although a small amount of fuel may gravity-feed from the aft tank without the motive-flow system, the pilot should consider all fuel in the aft tank as unusable and plan the flight accordingly." Without looking right now (sorry, I'm leaving to record sound from the Twin Commanders in a few hours), I recall that I assumed this statement was made out of abundance of caution, and implemented the system such that it would slowly equalize to a certain point, so long as the jet pumps had not failed (emulating a blockage). Given the arrangement of the jet pumps and their no-moving-part nature, I assumed that there would be flow through them, so long as the pressure on the auxiliary tank side is high enough.

@taylerf01 Thanks. I assume that means they had to wire the entire annunciator panel power (likely the ground, I would think) through the standby power switch, just to get those two annunciator lights called out in the manual to illuminate for some reason. Thanks for the demo! I'll see if this can be replicated without too much trouble.

Much thanks to you turnandbank! It worked for me. I join in with Black Square Developer with much appreciation for both your discovery of the problem and then letting everyone else in the form here know the cure. Again thanks....

@Black-Square said in STBY ELEC PWR INOP light during preflight: "...before I travel to record sounds for the Twin Commanders."

that looks like a perfect inclusion, thanks for the link!

I totally support this idea. I've been wishing for a realistic Twin Otter for ages. The Aerosoft version for MSFS2020 was aesthetically awesome. But the systems, flight dynamics, and turboprop simulation left a good bunch to be desired. The default one isn't even worth our time mentioning. I am very impresed with the Blacksquare Caravan and I know they would make an amazing Twin Otter.

@C-FJDH said in 13,450lbs - Significance on CG display?: Interesting! But it leads to a question on the implementation of the marker in the tablet. As I read it, the full aft limit is available at all weights. The forward limit is what changes at higher weights. 307 inches aft of datum (farther forward) at lighter weights, but the forward limits is pushed rearward 3 inches for weights above 13,450. I think the marker in the tablet should be near the forward CG limit, not the rear. Old thread, but since Nick may have missed this, I wanted to comment that it appears you're correct. This image is from section 6-27 of the flight manual. The forward CG limit evenly moves rearward after 13,450 lbs. Tablet mistake, indeed. [image: 29297225-5e96-40bc-94e0-76f772417adf.png]

@Black-Square thanks for replying. I am in 2020 and only when I am in auto pilot the trim wheel looks to be moving forward and back, quickly and heavily causing the plane to jerk along. I am not aware of anything that might be conflicting. I have checked and there are no other bindings that might be conflicting. I am not aware of any trim assist with in the sim but will double check this tomorrow.

Your welcome. I did let him know you were interested in talking to him - that he could contact you through here or the support staff. I did try to pass a message on to you through a support ticket (95631) about a month ago - so there's a chance not all of those messages are getting through (although I know it's been a BUSY month for you).

@hazzer111 a Comet is already being developed https://msfsaddons.com/2024/11/25/classic-aircraft-simulations-announces-the-de-havilland-comet-4-for-msfs-2024/

I've done that before! I found that ensuring the AT is off and the cycling the AP switches on the OVHD works.

@Derek - curious stuff! I found that with resource heavy aircraft there was a marked difference in performance between MSFS2020 and MSFS2024 with regards to the Series S, less noticeably so with the Series X. I am very aware though that that’s very much anecdotal, while you guys will have access to telemetry with hard numbers. Hopefully something works out some time, and thanks for being so engaging, it’s really appreciated

Thanks, this answer a lot of questions for me.

I have same post on reddit about lack of glass cockpit options in MSFS in general. Seems like it requires a lot of work from developers so I doubt that we see anything in near future. However one dude said that he is working on Aspen avionics as an addon and provided couple of screenshots.

Thank you for your feedback. There are no plans to add support for sound packages from other aircraft into the product at this time; however, FS Traffic does already include a large selection of custom sound packages for the included models, including the A320NEO. The included custom sound packages are specifically designed for us with AI aircraft. Mark - Just Flight

That sounds like a failure may have occurred (as part of the Maintenance simulation in the PA-38 Tomahawk), and the state saving is causing it to be recalled on future flights. In MSFS 2024 specifically, there is some instability with state-saving logic in the core simulator that could be causing this, but it may also be caused by how a flight is ended in the simulator. We would always recommend exiting a flight via '[ESC] > Main Menu', rather than forcing the simulator to close with a shortcut such as '[ALT]+[F4]'. If the same failures continue to be present at the start of every flight after ending a flight via the above method, I would recommend deleting the WearStates.ini file from the relevant file directory below, and it'll then regenerate the next time a flight is loaded with the Tomahawk's default wear state, with no active failures: MSFS 2020 - MS Store: C:\UsersUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe LocalState\packages\justflight-aircraft-pa38\work\Wear MSFS 2020 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator\Packages\justflight-aircraft-pa38\work\Wear MSFS 2024 - MS Store: C:\Users\USERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\justflight-aircraft-pa38\work\Wear MSFS 2024 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\justflightaircraft-pa38\work\Wear Hope that helps. Mark - Just Flight

All of my keyboard flap keys are disabled and only respond to trim button on yoke and flap axis handle on TM quadrant. Never seen flap responses from B key. Thanks though for the info.

It is possible for the state saving to get confused between updates, especially after large product updates which have a lot of changes, as the aircraft may be attempting to load a state that was only possible in a previous version of the product. One thing I'd recommend trying is deleting the StateSave.ini file from the relevant file directory, and it'll then regenerate the next time a flight is loaded with the RJ with the correct state saving options available. MSFS 2020 - MS Store: C:\UsersUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe LocalState\packages\justflight-aircraft-rj\work\PanelSave MSFS 2020 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator\Packages\justflight-aircraft-rj work\PanelSave MSFS 2024 - MS Store: C:\Users\USERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\justflight-aircraft-rj\work\PanelSave MSFS 2024 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\justflightaircraft-rj\work\PanelSave Hopefully, that should resolve any issues you may be having with state saving. If you continue to experience any of the behaviour you have listed, could I kindly ask you to raise a ticket with Just Flight Support via the following link: https://www.justflight.com/support In the ticket, if you are able to provide any screenshots/videos that are relevant to what you are experiencing, as well as any steps on how the behaviour can be reproduced, then our support team will be in the best position to be able to further assist with this. Mark - Just Flight