Acktu

I found a reference photo of an L-1011 with an LTN-92. That would be amazing if we could use this unit, since it uses a navigation database similar to a modern FMS. The LTN-72 is cool, but let’s be honest, entering those coordinates and being limited to only nine is a pain in the neck. Besides, as far as I know, coordinate systems like the CIVA and LTN-72 were mainly used for oceanic crossings. I also think modeling an LTN-92 would attract more people to buy this plane, since it’s a step closer to how a modern FMS works. No need to enter coordinates and instead use navigation fix names. Something for iniBuilds to think about. 😉

This is a huge problem for me too... Even though I have Spad Next (Similar program to Mobiflight), I can't even find how to control any autopilot functions though the in-sim controller setup window. Love the plane but it's sat in the hangar until I can operate most autopilot functions though my hardware. I don't like to be reaching for my mouse for every autopilot adjustment.

I’m no expert, but visible exhaust smoke generally requires combustion. During motoring, the engine is just spinning from the APU air, so you wouldn’t expect actual smoke. Any oil or residue burning off would happen once there’s enough heat from ignition, not before fuel is introduced.

That sounds like a bug.

Transfer will be available in the future, a few months from now. We all have to wait. https://forum.inibuilds.com/topic/36125-will-the-tristar-be-available-on-your-website-for-direct-purchase/#findComment-87755

I support the suggestion for the other variants! Many more were produced than the -500. I would gladly pay. I had not seen the first picture of those boarding stairs. Those stairs alone are so unique that they warrant the inclusion of the -1 variant!

I agree. Both the PFB and speed card should not be emissive. At night, it should require lighting from a lamp to be seen.

By any chance, prior to you trying to start the engines, did you select cold & dark panel state from the PFB? I say that because whenever I select that state, I can't start the engines, I would have to quit the flight and reload.

Speaking about arming the spoiler, I find it odd, that those two little lights are pointing away from the pilot. I haven't noticed any other annunciator around the cockpit that the pilot can see and verify from his point of view if the spoilers are armed.

Here are all the other displays: Altitude: ALTITUDE_SETPOINT_0 Vertical speed: INI_VS_PID_SETPOINT_2 Auto throttle: INI_AT_TARGET NAV 1 Course: CPT_HSI_NAV_1_COURSE NAV 2 Course: CPT_HSI_NAV_2_COURSE Edit: Once the rest of the autopilot bugs are fixed, I plan to share a snippet (for those with Spad Next) to operate this plane using a boeing MCP.

Thanks for the confirmation.

I am currently in latest and greatest L-1011 version 1.0.1. I can't seem to find out very basic controller mappings for most autopilot functions. The only one I was able to find out is AP disconnect and AT/TM disangage. However, I tried, "Autopilot ON" and I see the switch move to CMD, however it does not take control of the plane. Also, how can I toggle spoilers? "Toggle arm spoilers" which is what I use for other aircraft, does nothing. I also can't find ALT or HDG hold. Again, very basic AP functions I would like to map to my controller but this plane for some reason doesn't have any controller mappings unless I am blind. Has anyone figured out AP mappings, or is this bugged?

SIMCONNECT:AUTOPILOT HEADING LOCK DIR

That would be very useful, as a lot of us are trying to figure things out. I am seeing that making a switch move doesn't trigger any actions in the plane.

There was no official paint kit for the YS-11 but at least we had a bunch of liveries first in ini manager and then in Flightsim.to. So far I see nothing for the F27. As much as the F27 plane itself is very appealing to me, it's of no use if I can't fly with bespoke liveries from the airlines that flew it.

Liveries for 2020 (and 2024) are starting to show up here: https://flightsim.to/liveries/other-liveries-msfs2024/ It seems they removed them from ini manager and are now available in flightsim.to from same creator (Jviation)

You have a point and I didn't think of 2020 and assumed the OP was in 2024.

Now put a James Taylor album on the turntable to play "You've Got a Friend" 😉

Hello. I can't do engine maintenance because it says the engine covers are in place. 🤷‍♂️ Of coarse, this is not in EFB for compatible version, so I got around it by changing LVAR:INI_COVERS_ENABLED to = 0 While on this subject, I vote to get rid of engine covers on Premium version, in my opinion it's a gimmick. I can understand in General Aviation but you never see engine covers on airliners at a gate or ramp. At least make it an option to not have them in place when initiating a flight in cold/dark cockpit.

OK I found a work-around, so this is definitely a bug by the EFB not saving the buffer and not the actual plane. Since these values are different from other users, I'll outline the steps until developers fix this bug. What I did is used ChatGPT (other AI tools will probably do the same thing) to do the hard work for me, so it's super easy. Tell ChatGPT: "I need you to modify all of the "_min" and "_max" values. For each set, make values 0.2 further apart:" Open ThrottleData.ini from Steam: %APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\microsoft-aircraft-a330\work MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\microsoft-aircraft-a330\work Copy and paste it's entire contents of that file into ChatGPT and it should provide you with the edited results. Copy and paste the results back intoThrottleData.ini, save and restart sim. Hope this helps others, as it was a pain to catch the detents properly. Now it's super easy. I am using HC Bravo throttles.

I am not sure that changing buffer calibration is working. Even if I set those % numbers to extremely high percent, I see that hitting the detents is extremely small and any deviation from that exact point takes it out of detent. A good way to reproduce this is by loading ThrottleData.ini into Notepad++. Leave your throttle in idle and hit "Set IDLE" with a specific buffer. Notice the idle_min and idle_max values in the ini file. Now change the value in the idle buffer and Set IDLE on EFB again. Notepad++ says the file has been updated. Now note the values in the ini file have not changed from the last time, even though you set a different buffer value in the EFB.

Great. I've updated navigraph and now it does not crash to desktop! I usually update AIRAC once in a while to save on the monthly fee since I don't fly online. Hopefully going forward it it won't be a requirement to have the AIRAC updated continuously. Thank you for the quick support!

Thanks. My AIRAC is 2205 so it is a bit old. I will resub to get latest and I'll report back.

Greetings. I can reproduce this bug 100% of the time, which unfortunately for me, makes the A310 unflyable. Basically, right after I enter the departure and destination into the INIT page, as soon as I hit the button on the MCDU, I crash to desktop instantly. I've provided a video which shows step by step. Let me know if there are any logs which can be helpful and where to find them. The only things in my community folder besides some add on planes (PMDG, Fenix, etc) and scenery is: GSX, fsltl and FSrealistic. I have not installed the A310 enhanced package.