All Activity

Oh and the cabin vs stays at +50 for the entire cruise whilst the cabin alt stays constant. There can be minor occasional fluctuations of cabin vs +50 very briefly, -50 very briefly. But it should be at 0 the vast vast majority of the time. I hope you can keep track of all these as there are a lot. Which is obviously extremely disappointing given how long the aircraft has been out and its price and how it was marketed.

Hi, I don't have the hardware so I am not to familiar. However can you try going into the FS Controls Menu > Scan Input; and then move the throttle through each detent and verify that there is no bindings conflicting as the detents are passed through, including opening the reversers. Additionally do you use SPAD.NXT or FSUIPC, anything that can manipulate hardware as well?

They're working for me.

Newest update broke brake temps for me.

Not sure if related to the enq, but Is your navdata up to date and not mixed in with anything from MSFS2020? :) https://forum.inibuilds.com/topic/36628-how-exactly-do-i-engage-the-ils-or-loc-for-an-automatic-landing-in-the-l-1011/

Even after throttle calibration in the EFB and making sure that Reverse on Axis is on, when I put my throttle into reverse, the throttle in the sim just stays on Idle. My throttle quadrant is the Thrustmaster TCA Airbus Edition Throttle Quadrant. I have tried applying deadzone, going into the game files to turn on Reverse on Axis (was already on) and tweaking and resetting the calibration an bunch of times but it doesn't work. Thanks for any help!

No traction here?

Thanks for the suggestion…. Unfortunately it didn’t work for me.

Perhaps this is a quirk of the real jet, but I doubt it. I have noticed that if I am flying manually with FDs on and I command a certain vertical speed, if the aircraft has drifted away from that vertical speed when you turn the autopilot the vertical speed target switches to the aircraft's current vertical speed and you have to re-command the prior target. For an extreme example, say I have 2000 fpm commanded in the window but am doing 1000 fpm, when I turn the autopilot on the target immediately switches to 1000 fpm. Happy to capture a video of the behavior if needed.

I try to avoid "X is broken" type reports as I know they're of limited utility unless it's something obvious, but I'm not sure what context would be helpful here. I have continued to notice that the autopilot struggles in situations that it very much should be able to cope with. I have observed the following: The autopilot is inconsistent with regards to maximum bank angle and turning rate: When high and fast it sometimes behaves the way I'd expect it to when low and slow -- faster banks to more aggressive bank angles -- but at other times it's the opposite and it will lurch suddenly to the maximum bank angle when high and fast and whip around when changing heading, etc. I assume the actual TriStar autopilot had logic built in to make inputs less drastic at cruise altitude but it seems like if they're represented in your autopilot that they're getting mixed up in different regimes. When intercepting VOR radials or a Localizer/ILS at 30 degrees or less, the autopilot almost always struggles to begin the turn soon enough and turns too slowly to intercept without overshooting. I am not aware of any TriStar quirks that would make this be the case but I am always willing to learn. The autopilot continues to struggle with maintaining course in a crosswind both when tracking VORs and tracking the INS. I am not even talking about significant crosswinds like a 100+ knot wind at a 90 degree angle, even something modest like a quartering tailwind at around 35 knots it will struggle to track the radial. If intercepting a VOR/LOC/ILS radial in heading mode, when the HSI shows even a half dot deflection and you switch to the VOR/LOC/ILS mode, the autopilot will often quickly bank "away" to intercept the radial more aggressively as if you were farther away, and then immediately but more gradually banks back to turn into the radial to track it, resulting in an overshoot.

Hello inibuilds, Huge fan of your a320neo in msfs 2020 xbox. But I’m eager to know when, and if, your a350 will be “published” in the marketplace. Thanks! It’s my all time favorite plane and I would love to be able to fly it one day, since I’m not convinced for now to switch to msfs 2024. N.B.: when I’ve done a flight with your a320neo, I accidentally switched off the engine 1 lever and logically the engine turned off. And I want to know, if this occurs by accident again, how to turn it back on. I tried following the instructions written in the pfd (if that’s what it’s called! *-*) but the engine couldn’t get back on. At least I can confirm that it can fly with one engine only, so kudos to that! Good day, and thanks in advance for your asnwer, Sincerely, Dimthony BROTHERS

Ive been getting this problem since release. Example: Out of VHHX there is a max alt 7000 till WHISKY (its a repeatable scenario). Then you dial in the step climb (100 or 130, cant remember). Change the PMS height to 100/130, sometimes its set to cruise alt, but it makes no difference what number is in the PMS box. Hit VNAV and wait, nothing. Hit TM, nothing. TM and VNAV, nothing. It just refuses to climb. Someone posted a video link to this exact scenario and shows it doing nothing. You can add a V/S of at least 1000, let it start to climb until at least >1000FPM, then hit VNAV. If it is under 1000FPM it just goes back to <insert doing what ever it wants here> Even holding alt at FL130 then doing the VNAV/TM/PMS results in nothing unless you make sure it climbs >1000FPM then VNAV it. There was a post from the flight manual that stated "add new alt, press VNAV" and it will climb. Currently 1.0.5, cleared all caches and old folders. Problems still persists.

I may have mentioned it in another thread but if not I'll add it here that I have updated the team with the added information provided by Joshua

I'll pass this along to the team, thank you

Let's back up a bit. To navigate using the GNS530, one has to select RADIO and VOR in the AFCS. Then to navigate by GPS, press CDI on the GNS530 to select GPS. To navigate by VOR, LOC or ILS; press CDI on the GNS530 to select VLOC. This is the same thing as pressing GPS/NAV in MSFS, but put that aside for the L-1011. For example: I'm navigating by INS enroute through a standard arrival (STAR). Near the last STAR waypoints, I want to switch over to the GNS530 for the approach procedure. I switch from INS to RADIO, select VOR, and navigate by GPS along the approach procedure until time to intercept the ILS (or LOC or VOR depending on the procedure). Then I need to press CDI on the GNS530 to select VLOC. (What I and many others have been doing is to tune the ILS to all 3 radios: Nav 1, GNS530, and Nav 2.). Now the GNS530 in VLOC mode is "in tune" with the aircraft, and I can now select ILS on the AFCS. This is a lot of switch work, but if done in sequence, it will work (with patience). Now the HSI is another matter altogether, and there is a thread around here for that. Long story short, the distance on the HSI, as I recall, only display from the INS. Look up that other thread to make sure. The photos below are not from the TriStar model, but the GNS530 is the same WT model in many MSFS aircraft models, so it works the same as in other planes. Make sense?

Fix for this should be coming in the next update, thank you :)

I’m not sure if I’m recalling correctly but I believe I saw someone here mentioning that the L1011, by default, is being loaded with all bags/cargo in the forward cargo compartment with the leftover in the aft compartment. That could possibly explain the aircraft being forward than normal CG/high AoA at cruise - hence the higher deck angle. Definitely worth it for the team to take a look at!

Wait a sec. If this is true, then how does one change from GPS enroute NAV to an ILS approach if BOTH use the "radio" selection? How does it know whether to follow the nav radios or the GPS? How would it know when to switch from one to the other just by changing from "VOR" to "LOC"? What displays on the HSI when both a tuned VOR AND a GPS route are loaded? Which distance and time values are displayed?

I'll pass this along to the team, thank you

Hi, I'll pass it along to the team for consideration. Thank you.

A reply from inibuilds would be appreciated.

Same. Opened a thread in suggestions to ask if we could have all 3 filled with our flight plan during import.

Folks on the MSFS Forum had discovered that, even if one is not using the GPS, selecting it on the PFB (GPS+INS) then making sure that the GNS530 is in NAV (not GPS) mode, and that it is also tuned to the ILS frequency helped. Then return to the PFB and deselect it so that one is back to INS only displayed. The distinction as I understand it is that the GPS is always active, even when not selected on the PFB as displayed. Unless this has changed since the TriStar was launched. Cheers!

Hello, Right now the PFB only seem to import waypoints into INS1. Could it send the flight plan to all 3 INS ?