Systems

anybody else having issues with the cabin not climbing? i've it in auto or manual nothing i do can get it to climb and just have the cabin horn screaming at me the whole flight! even after i had landed i want to cold and dark panel state and the horn was still screaming at me! what am i missing here ? should that not be configured when the flight engineer does the climb check ?

On all cold and dark starts, these buttons start latched. They should not. Pilot and FO Window heats, even when unlatched, do NOT turn off. They should.

With proper ILS frequency and course put in and the HSI source set to radio, as soon as the localizer is picked up, the HSI course needle turns 30 ish degrees left and the plane just flies right on through the localizer. The course remains correctly set on the MCP. I may be doing something wrong here. (I suspect I am)

The test button for the brake heat on on the Engineer console shows a working indicator, but the brakes do not show any heat buildup even after landing.

Even when the hydraulics are not online, all the overhead systems show OK. They should not. Many should show faults until hydraulics come online.

The button is modelled and can be pressed, but it has no impact on the fuel used counters.

As stated in the title. After a 5 hour long flight, the stated INS position exactly matched the stand coordinates on the chart.

On landings, when I use reverse thrust on my joystick, the takeoff configuration warning sounds. However, it only sounds using my way of activating the reverse thrust on my joystick. My joystick is a Logitech 3D Pro. For reverse thrust, I use a configuration that assigns a button that activates reverse thrust and keeps it activated while I'm holding the button, allowing me to use the same throttle axis movement I use for forward thrust, now controlling the intensity of the reverse thrust. I know most people use other commands, like a button that turns reverse thrust on/off with a single press and using the throttle axis for reverse, but it doesn't work well with most…

Hi, Yesterday i did get Navigraph registrated and the charts did work. Today. The conection is "lost" Re-registrated.. But it wont work. Also the option on what source for charts to use in charts in the PFB is not there.

I noticed that the N1, EGT, N2, etc and the oil quantity, oil press, etc. All read the same. Is there any plan to implement variation in these engines since they use hydromechanical fuel control units, and they vary more than modern FADEC engines. Also, I am really hoping for maintenance items and failures for the APU and engines like run hours, oil quantity, oil consumption, and things like battery wear and tire and brake wear, etc. Like featured on the A340 and A350. Thanks!

Cetain pages in the PFB cause a massive FPS drop and almost doubles the Graphics Queue response times. This low fps remains as long as the page is open, even if the PFB is hidden. It seems to affect the Loadsheet, TO Perf and Landing Perf pages.

The autopilot does not seem to take crosswind in to account when flying in VOR and LOC mode, however in INS mode it does. In this screenshot I have a 100 kt crosswind, with the wind coming from 270 degrees. You can see that the autopilot is flying a heading corresponding to the inbound course on the VOR rather than maintaining a wind correction angle and will over time get further and further away from the radial. If i switch over to INS navigation and fly to the same VOR using INS it will apply a wind correction angle and follow the inbound course correctly. VOR: INS:

During my decent I was descending in VS mode at 2500 and I was a bit high on the path so I opened the speed brakes for a bit and when I closed the speed brakes the nose pitch hard up over 6000 feet a minute on the VSI and I cycled VS off then on and VS window had 8500 feet per minute up I had to quick run the VS back down to 2500 a minute down. The autopilot was very slow to respond even when I ran the VS back down I gained a few thousand feet and lost a ton of airspeed.

INS Only config with drift, waypoints loaded from PFB. Made an E/W error in position update on INS 1, but still tracking route reasonably well. Attached screenshot, INS2 has been updated to correct position within last 2 mins so is accurate. Littlenavmap plot shown to show how on track we are!

Really a minor issue: GW and fuel seems to be displayed in lbs and not in kg´s at the FI panel in it´s specific gauge after pressing the button for display. Units are set to metric at the EFB.

I was looking at the advertising on the store page for the aircraft. I went ahead and pulled the circuit breakers for the INS 1 and INS 2 power, CAPT HSI, and the following and none of those breakers seem to be connected to their associated system or indicator. Is this intended? What is ini was defining as "complete"? Thanks.

I've noticed selecting IAS hold (pitch) at 250 knots during a climb out with climb EPR doesn't perform well. Maybe this is a quirk of the real aicraft but the speed goes to as high as 320 knots without any increase in climb rate. Just wanted to let you know. Thanks 😄

Somehow I can’t stop the APU. Tried several things but the damn thing keeps on running. Assistance is all off. My guess is that I missed something. Help is appreciated

All my other planes (Fenix/PMDG/iniBuilds) are fine and work perfectly the steering and throttle. The Tristar is giving me grief. I need around 50-60% throttle to get the plane moving. When its gets doing and picks up speed over 20knots, I have to back off the throttle a tiny bit and it's enough to decelerate the plane to an eventual stop. It's like the brakes are stuck on (they are not of course). Then comes the steering. I don't really have any. I am using a Virpil joystick with twist feature for the rudder (I don't have pedals). Again it's fine for every other aircraft I own. On the Tristar, when I try to turn a corner when taxiing, it will start t…

The barber pole on the FO airspeed indicator seems to always show about 10 knots lower than the airspeed indicator on the CPT side.

This one could be a me problem but I'm finding if I have the AT set to TM sometimes I'll disconnect on its own and go back to where my throttles are set. Could this be due to throttle noise? Thanks

Thank You for the great L-1011 Tristar 👍 I just made a flight from EKCH to EGSS, which went quite good, considering this was my first flight. It looks complex, but in the end it's not that hard to manage single handedly. Three points... 1. VRAM consumption is quite high, giving me the MSFS2024 GPU warning. I don´t have issues with other addons (PMDG, Fenix, FSLabs, Inibuilds: A350, A340, etc..) 2. It would be nice if the setting for the Gross Weight in the Fuels Gauge (Engineer panel GW / Fuel Wt) would run much quicker, or would be set when transferring the Take Off data from the PFB to the Aircraft, like the Take Off speeds. 3. The Pressurisation Gaug…

Hi, Congratulations on the release! I’ve been enjoying flying the Tristar, it’s a great model with a lot of potential. I noticed something with the TM switch on the glareshield. I expected it to set climb EPR, but instead it shows 000 and commands thrust levers to IDLE. It only sets climb EPR after I turn on the autopilot. Is that how it’s supposed to work? I have setup the PMS properly. Secondly, when flying in FD AOA mode (TOGA) after takeoff the lateral flight director bar is frozen to the center of the 'bird' rather than giving guidance, despite VOR mode being switched on and showing white in FMA. (I am using the GPS) Again, is that the way it's suppose…

Pilot/Copilot DME readout mismatch as per attached screenshot. This was just after retuning NAV2. Once the pilot DME clicked under 100nm, the Copilot DME caught up.

When performing the lights test on the FE’s panel, I’ve noticed a few things that aren’t quite right. First, the fire detection lights are still illuminating when the manual says that they shouldn’t Second, with the APU Master Power switch ON, the 4 red APU fault lights do not illuminate. these 4 lights should illuminate during the test, and then need to be reset by pressing the reset button after the lights test button is unlatched again. I understand, a comprehensive failure simulation isn’t part of this product, but since this test is part of the normal SOPs for most every L1011 operator out there, I really do think it should be add…