Systems

Hi. In both 1.01 and 1.02 I've noticed that the LOC or ILS buttons do not engage. The only way for me to track the approach path is the VOR function as neither LOC/ILS would work. I know people reported funny behaviour when changing from INS to radio navigation but I've tried it in a flight between 2 nearby airports (TAPA to TFFR), without even turning on the INS, and I get the same issues. Also, I fly in VR. Could this be the problem? I'll try tomorrow in 2D in case it's a VR issue but hopefully this is fixed soon as makes approaches in tricky weather impossible.

Hi, Slightly odd one. I've been doing a few practice departures and climbs up to cruise, getting a feel for the aircraft. I departed from Luton (EGGW) and set course towards Menorca (LEMH) using the following route, the first 9 waypoints entered manually (not imported through Simbrief), starting at RODNI. EGGW/25 N0480F350 RODN1B RODNI N27 ICTAM Q63 CPT UN859 SOPIL DCT BALAN DCT EVPOK DCT NARAK DCT GAI DCT LOMRA DCT ROCAN DCT GEANT N727 SARGO SARG5B LEMH/01 Upon passing GWC VOR (Waypoint 7 - N5051.3, W00045.4) The aircraft should have turned slightly left towards SITET (Waypoint 8 - N5006.0, E00000.0). Instead, it entered a right turn, almost as if it's tryi…

Hello, Been enjoying flying the TriStar but it seems that every time I select IAS and MACH on the pitch mode selector during a climb, the autopilot/FD initially holds the desired speed but then pitches down, causing the the aircraft to accelerate past the speed target and overspeed if I don't intervene with V/S. Over two flights this seems to have happened consistently in both IAS and MACH hold modes. At this point it seems that V/S is the only appropriate vertical mode that can be used for a climb - I can't imagine that this is realistic at all. Has anyone else experienced this?

I have had a few issues with altitude/VNAV. Out of VHHX there is a max alt of 7000 feet untill 17nm past the VOR. The plane will (mostly) settle at 7000 feet in CMD VNAV/TM mode. ALT CAP and should stick at 7000 Now when you dial in a new alt and do nothing else, it will often start to climb by itself. One time dialled in a new alt increase and it started going down, probably as it was in a turn and thats the way the plane was going vertically at the time. According to the normal ops page above it should hold until you engage ALT SELECT+VNAV. There is also a lag of a few seconds between hitting VNAV and anything happening. B…

I noticed this in version 1.0.2 and there is the same issue in 1.0.3. When aligning the INSs and inputting the position into all 3 of them when the selector is in POS, all is well. However after pushing back with the INSs in NAV and having sen the OFP to the INS through the paper flight bag, the position is wrong. Essentially I can't naivgate using the INS. The aircraft thinks it is half a degree to the west of the actual position. This causes the aircraft to fly offset of the track, even though I haven't programmed it for offset. I can't even update the position because after I press INSERT the second time after inserting the Longitude, the value just jumps by itself aga…

I absolutely can't see it in the cockpit so I'd like to have a key somewhere to bring it up. Possible? Thanks for any replies.

latest update, the auto brake doesn't work at all on landing. have not tried a rejected takeoff with the ab. Also, brake temps dont change at all..did a full manual landing and stood on the brakes, zero change in temp. test function DOES work though.

On my last flight v1.0.2 the capt side decision light was permanently on.

Dear all, I made a flight yesterday night without any problem on the EFB. When trying a new one this morning, my EFB is blank (gray empty page). I've tried disabling / enabling the add-on in MSFS2024, uninstalling liveries, but nothing changes. What I don't understand is that I haven't change anything since yesterday night. Just closed the sim and re-opened it this morning. Does someone have an idea of what can cause this ? Thank you for your help. Thomas P.S. : my bad : it's actually the night lighting that is the problem. During the day the EFB is ok. But during night time, with the EFB lightning to the maximum, it's barely visible...

In the V1.03 update, the BOD DIS has been limited to 3 digits instead of 4 digits for some reason. There should be 4 digits to allow 1000's of NM to be added to monitor the TOD along the flight plan route from the departure point. FCOM example of PMS flight setup page. IN V vs, in the sim... limited to 999.

Hi there, Noticed that the cabin pressure controls don't have any affect. Cabin doesn't pressurise until far too late and when it does it's not to what's set using the dials. In fact, I was able to change the dials to any value and this had no effect on anything. Had this issue with other ini products and seems like again, it's happening.

Hi, FL360, all packs on, the cruise level set on the tape, but the pressure gauge shows 0 ft cabin altitude and probably over the gauge max scale delta p. Also the cabin temperature is quite low, below 20 F.

Strange things happens when updating the plane and starting direct on the runway: IRS is aligned and switched to nav mode automatically. The FP is imported into the INS and shown on the screen. WP 0 to 9 are set. But now, after engaging the AP and INS mode in flight the plane does not follow the FP. Changing waypoint tracks 2- 3 or 2- 5 as a "direct to" has no effect. The plane keeps it initial heading. Using the GNS and setting Navigation to VOR FP will be followed as it should do. I’m lost. May you have some hints.

Hi, When using pounds, in cruise the fuel flow gauges show something in the region of 53.5 or something around that. But then on the gauge, it says just above 'x1000' which would be 53,500lbs per hour! Is this a bug or should the text above the readout say 'x100' instead? With the decimal point two digits in, its 53.5. If it was correct, it should be 5,350lbs per hour. Whats the story here?

After version 1.0.3 the standby power system is and shows UNARMED through the UNARMED light and the DC standby bus fail light on the electrical panel. The switch is clearly in the ARM position. If I put the switch in ON, the system works fine.

Hi Seems like V1.0.3 is unusable for me. The ON APU or READY FOR TAKEOFF panel states don't work as they seem to stall and get stuck around "APU initialisation" or "waiting for RPM target", before it times out. Am I doing anything wrong? Was looking forward to the fixes in 1.0.3. and rather disappointed I cannot even start from an easy state...

Desperate to fly this thing, but can’t bring myself to do it without at least some basic hardware connected for AP (altitude, VS etc.). Anyone managed to get basic stuff to work via MobiFlight? Any ETA as to when all this will be opened up by @iniBuilds to routines and templates that could be built? Thanks!

Evening. thought it would be best here. so I e tried two flights one on launch and now another after the latest update. however when running in the ILS freq in Miami for Rwy 09. Which is 110.90 I’m just picking up the localiser on the HSI at all. I am however clearly seeing the Glideslope on the right. I’ve select radio on the button for insgos/radio. But the localiser doesn’t appear to pop up. however on the standby hsi I’m getting the dme to the localiser and the direct of it. But on the primary hsi nothing is showing. is this still a bug as I’m trying to do some ILS app and without it working …

Hello everyone, I have the problem that whenever I want to use the Thrustmanagement mode to climb, it shows the EPR 000 and the engines spool down. I have set everything up correctly including both PMS, have already played around with switching of probe Heat, and many more things. I would be really glad if anyone had a solution or at least knows if this is a bug or I’m missing something systemwise. kind regards Elias!

Could not get the fuel to dump as per procedure. Is it not yet modeled?

Having tested the latest versin 1.02, with the plane spawned on the runway in ready for t/o config, I still see the AP struggling with the vertical modes. IAS hold seems to work, but as soon as I change to VS or ALT hold, the wobble starts. Also, when in VS mode and retracting the flaps, the nose pitches down and the plane starts a temporary decent. Please fix the AP asap, as this current state makes the Tristar unflyable for me and I guess many others, too. Best regards, Wolfgang

Hi, i had like 3 good flight, but now i cant finish a flight, because one or all of the INS freeze on position, and when i check status its back on 90, ALERT flashing, and i cant do anything onwards. Any suggestion what can be wrong, or how can I help myself on this? Also it seems, HSI is out as well, because when i try to finish the flight with radio navigation it doesnt change.. Rotates, but apart from that, radio navigation doesnt work either, and it not rotate to the radio beacon just to 180-360. Not even show the ILS course deviation, however at least the plane captures it.

Per title, the AMP's are not functioning correctly. I've created a post on the discord and bumped already but it hasn't been looked at yet even after several days. Please see linked stream of 1.0.1 behavior. In short - COM1 and 2 when tuned to a broadcasting station will play audio even when that COM's speaker is off but MIC selected on. And even with no MIC selected, the last selected VHF tuned station will still be transmitting/receiving. This makes it impossible to transmit over one frequency while only monitoring the other. Also, where are the tuning controls located for VHF3? None of the AMP's display VHF3 and the first observer and flight engineer AMP's are c…

Whatever I do, I can’t get the plane to move on pushback. Brakes are off, chocks pulled, brakes pressed and released, wiggling the controls, applying thrust, nothing helps. Am I missing something or is this a bug? I am on Xbox and use the built in pushback tool.

TriStar version 1.0.2 MSFS Update 4 version 1.6.34.0 Not sure if I'm missing anything here, I've repeatedly started up the aircraft from cold & dark performing all FE functions manually. But each time I'm unable to set the stabilizer trim to the T.0. perf calculated value such as 3.69 (per my latest attempt). Despite all 4 hydraulic systems pressurized, I'm unable to set the stabilizer trim. When I rotate the trim wheel to the target setting, it slowly rotates back to 2 Solution: In Settings make sure AI Auto Trim is disabled under Assistances