All Activity

Another Ghost WASM crash. YBBN - NZAA about 1.3 hours into the flight. Trying to set up a simconnect log file to see what is causing the issue. However, pretty much going to park this plane till ini release an update and fix what ever they did that started this problem.

Works for me, both NAV radios tuned to the ILS, and intercepting from underneath the GS seems to do it. Maybe you're out of the engagement envelope?

I've discovered two issues in the current version of the A350 model: 1. Pitch trim indication during touch and go training During a touch and go, when initiating a continuous take‑off, the pitch trim indication should appear on the PFD as soon as the thrust levers are moved out of idle. However, the iniBuilds A350 does not behave as expected. As a result, the aircraft does not automatically pitch trim to the take‑off position, and it begins to auto‑rotate before reaching Vref speed without any sidestick input. According to the real‑world A350 FCOM, the pitch trim indication on the lower right PFD should appear during a continuous take‑off under any of the following conditions: move the thrust lever out of idle detent disarm the spoilers retract the flap for one detent flight crew press the PITCH TRIM button The aircraft should then auto‑trim back to the take‑off position, but it should not rotate without sidestick input. 2.Brake temperture After a normal full‑stop landing with the MED autobrake(no BTV, disconnect the autobrake and use very light mannual brake when slow down to 50kt ), the brake temperature rises from the normal 30‑40 °C to over 200 °C, which seems unrealistic. Even stranger, with the brake fan turned on, the temperature still continues to increase. According to the FCOM and FCTM, the brake temperature should drop immediately when the brake fan is activated. Could anyone leave me some solutions or help to pass the feedback to the develop team?

same here, in 1.0.2. ILS or LOC will not engage. Not flying in VR.

I like the added smoke on startup, but it should only happen once fuel is introduced, not on the starter motor.

Could the performance data card be duplicated on the captains side of the instrument panel. In VR, this would make seeing all the different airspeeds from the card much easier. Thanks

Yep to both. GMT and weight updated right before TO. If I engage TM with AP off: With AP ON:

Alright, but what about when switching from MIN to NORM or vice versa? Would there be no difference in APU gauge readings between those two modes?

To follow on from the above, I've also tested after completely unplugging all controls except my mouse, keyboard and a single Xbox-compatible controller, with the keyboard/mouse settings being the MSFS 2024 defaults and the controller being used only for general controls but disabled for airplanes and the L-1011 500 specifically. There are no other controllers connected or detected, so the issue definitely isn't somehow caused by my controllers.

Ah, they hadn't been, no. Simply didn't occur to me to remember to check them; there's a bit of a mental disconnect between half the product being updated thru the store and half of it outside. I've tried it again now after updating the liveries and am no longer seieng the issue with the aircraft otherwise loaded up in the same way, so either the liveries fixed it or it was an intermittent / temporary glitch of some kind. Thanks!

I reported this on the Discord and indeed, the only way I got it working was to stream the aircraft. I couldn't get it to work at all with the aircraft installed locally. Logging in while streaming and then installing locally didn't work, as I was immediately logged out. That being said, it keeps logging me out (presumably with each update..?). Since the last update, I'm struggling to log in again even while streaming the aircraft. To outline the problem step by step, the QR doesn't appear on first load of the aircraft. Trying to link through my browser results in an error message (The user code is expired, invalid, or already linked to an app). If I press 'Refresh Code,' the QR code now appears and I can link, but even though it's showing as linked in my Navigraph account, it just doesn't work. This really needs fixing. Edit: Okay, it's decided to start working again all of a sudden: I logged out of the L1011 from my Navigraph account Logged in via the PFB (it didn't work. The QR code was still showing despite linking 'successfully') Restarted the sim and now the PFB is showing I'm logged in Bit of a faff.

Just tried again but with a Simbrief import so there's no doubt over whether the coordinates were correct. Same thing happened. The INS gets stuck on 6 > 7, when it should change to 7 > 8. Looks to be correctly positioned on the moving map display. It seems to get confused as soon as I fly over the waypoint. I get the sense the aircraft feels as if it's 'missed' GWC VOR and tries to have another go by turning back. Approaching GWC. Leg 6 > 7. Correct coordinates and positioning on the map. Aircraft turns right overhead GWC. INS stuck on leg 6 > 7. Distance starts increasing. Aircraft now off track according to the moving map.

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.

Interesting - with this does the INS show 78 as the correct leg and does the moveable map make sense to the waypoints that you've entered?.. just incase of input error (although you've proved it twice) Waypoint N5060.0E00000.0 is a good one because even if you get E/W mixed up it's the same location. So should be fairly safe from error. However interesting that the distance is increasing with leg 78 would only indicate that it thinks the waypoint is somewhere else.

In my case, the front cargo door kept opening and closing continuously, making it impossible to load cargo, but I just tested version 3.9.2 and it has been fixed.

As I pointed out, you will not see any change in APU parameters. Going to MAX MODE fully opens the APU inlet guide vanes...you can't see that. It may raise the APU TGT as more air goes through the open inlet guide vanes to the load compressor but not necessarily. When you're starting engines, the packs are turned off, galley power is turned off, ATMs are off...the load on the APU is greatly reduced so you may actually see a decrease in TGT. The only time we ever manually used the MAX MODE spring-loaded position was if we got an INLET FLOW light (probably due to ice forming in the inlet duct) that caused an automatic APU shutdown. After 3-5 minutes and the INLET FLOW light going out, we would then start the APU in MAX MODE.

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 trying to double back to GWC. This happened a few days ago. I shrugged it off as user error, perhaps a bug. I tried again today and the exact same thing happened at the exact same point. I managed to get it into heading mode to turn it back towards the next waypoint (SITET) but I noticed the distance to the next waypoint was increasing instead of decreasing. Clearly it hadn't sequenced properly. I had to do a manual track change from waypoint 7 to 8 to get it work properly. Am I doing something wrong?

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

Are you able to upload a video of this occurring, additionally just to verify, nothing else managed to rebind or is still binded that is now causing a potential conflict.

hi there! since the new update the yoke on the cpt side shakes while on the ground. the yoke on the fo side doesnt do this.

Fuel Pumps.mp4

Hi, As requested. ACS Switch.mp4

OK thanks. Any idea of timeframe and are other users reporting the same issue?

It is still being investigated by the team from what I can see, has not been forgotten. Thank you 🙂

Hi Jamie, another update but the throttle calibration is still not working. Do you know when it's going to be fixed or looked at?