All Activity

I got this too

This is how assumed it would function ( I bought the manual on ebay). But its not currently working in that function for me. I will try an uninstall and do a fresh DL and see if it works after that.

That’s usually caused by incorrect parking alignment or a scenery compatibility issue with the A320neo v2. Try parking exactly on the stop marker, turn off external ground handling mods, and test at a default Asobo airport to see if the jetway attaches correctly there.

I tried setting the DH to 200 feet on both the captain and FO side radar altimeters. That seems to have cured the flashing but the FO's DH lights stayed on until I clicked repeatedly 5 or 6 times in rapid succession.

Sitting at the gate setting up and both the DH light on the artificial horizon and the DH light on the radar altimeter are flashing intermittently. Different durations between flashes, different durations of being lit.

I know 1.0.5 was supposed to cure the pneumatic system, but I am still seeing the cabin climb gauge start low and move to 0 upon initial load in, and when bringing the APU bleed and Pack 2 online there is a 500-1000fpm descent rate on the cabin climb gauge followed by an oscillating climb/descent pattern that eventually settles on 0. After takeoff, if you take off with only Pack 2 operating, when you bring the next pack online the cabin moves to full scale descent on the cabin climb gauge, and then it reverts to the previous climb rate. Bringing the 3rd pack on bumps the climb rate down a bit briefly and then it returns. There shouldn't be such a dramatic descent when you bring the 2nd pack online.

This was a previously reported bug that I think was supposed to have been fixed in 1.0.3 or 1.0.4 but I still see the same behavior.

In 1.05, all fuel pumps initially show their flow bars after power up. However, once ANY pump is selected, the others immediately switch to OFF. It appears that they are initialising in the wrong visual state, but the pumps are actually off. I'll try to capture a video of this occurring.

I'll pass this along to the team, feel free to add videos or images detailing the issue at hand, thank you :)

Lockheed L-1011 Training Manual_INS_Remote_Loading.pdfLockheed L-1011 Training Manual_INS_POS_Update.pdf Excerpts from TWA's FCTM for the L1011. It's a slightly newer INS, but the procedures work as described. I included inflight position updates too. For remote loading: Simply select "RMT" on all of the units, select WPT mode, and enter your coordinates for each waypoint. The waypoint thumbwheel must still be advanced manually on each unit before entering the next set of coordinates. NOTE: THIS CANNOT BE USED FOR INITIAL POSITION LOADING. Think of it as being somewhat like a copy-paste function. You have to select the waypoint you want it to go into on each unit before pasting the value in. Otherwise it will put it might overwrite the last waypoint you programmed, if you forget to advance the thumbwheel. The AP can use data from INS 1 or 2, it depends which Autopilot CMD switch you turn on. Left one is INS 1, Right one is INS 2.

I concur, this has broken in 1.05. It was working before.

Hey guys, Since v1.0.5 it seems that the rudder and stab positions have been stuck at L30/full down respectively and do not seem to be responding to control inputs; only the ailerons and spoilers' position indicators seem to be working at the moment. I don't believe this issue was present in v1.0.4. For reference, the screenshot attached was taken at cruise flight.

We're on update 1.0.5 and looking at the manual download it still shows version 1.0, while I know you've added some new features in recent releases. Please make sure you're also going back and updating your manual to include procedures, etc., for those new features.

Sounds good, I'll pass it along to the team then. Thank you for checking :)

@IniJamir The sharklets are locked to short under "option managed by livery" in the OIS. Unless there's another way to change it as you can on the default-white livery? The Asian Carriers Pack II is still on version 1.0.1.

Is climb power still being looked into because this plane still (1.0.5) has too much power and the EPR and N1 synching needs to be corrected.

Hello all I am using this great AIRCRAFT starting in FS2020. Now in FS2024 and before SU5 all was running fine. But now I have these problems 1 - If I start a flight and choose a runway (so not in Cold and Dark), the aircraft crashes but the sim set it "in the right way" .. 2 - I have got a WASM pronlem (orange screen) and had to restart the sim 3 - There is a problem with the data SIMBRIEF send - they are not well received by the Aircraft - For exemple the ZFWG was wrong and the P-FPLN is not received (the Recieve F-plana button is not active) Thank you for your help

Hi, can you upload a video to either YouTube or Google Drive and then link it here so I can better assist with the issue at hand. Pushing in the Knobs set them to Managed Mode and Pulling them out set them to Manual mode

Hello, The issue appears to stem from something deeper within the simulator. Our current theory is that when SimConnect becomes overloaded with data, it effectively “pauses” WASM, causing it to stop updating. Its not pausing the A350 WASM, but the whole WASM module function of the sim itself. This isn’t a true WASM crash, which also makes it very difficult to reproduce or pinpoint, as it doesn’t trigger anything in the debugger. The functions being executed at the time of the freeze vary between reports, with no consistent pattern, and they don’t show any inherent issues—those same functions run normally in other situations. Hope this gives you some insight into the issue which has been known about and being combatted.

This issue is known; It’s a cue to let the user know the sim is paused but since SU5 we’re seeing it trigger more when the system is under strain during loading or complex calculations as well as when there is diminished perf.

Mystery solved, some settings in SPAD.neXt, couldn't find anything, so probably some corrupted data in the profile. I exported the profile, delete and import, problem solved.

Glad I could be of assistance, enjoy :)

Hi, can you try switching the winglet between long and short for me, also verify that there wasn't any livery update for the Xbox package, I don't think there was but just to make sure. Let me know, thanks.

Thank you for this, I've added it along for the devs to see :)

Hi Jamir, completely uninstalling and reinstalling it has worked. Kind regards, Ruben