All Activity

I'm quite sure you could be able to get the test pattern on the weather RADAR display. Not so anymore in 1.0.5. In all; No test pattern or TEST indication on screen Weather tilt manipulation does not change displayed value of U 3.0 Pressing one mode control button should de-select the previous selection (i.e. Pressing WX while WX+T is pressed, de-presses WX+T) WX+T mode only displays WX on screen. Same as WX mode. (Logical but unverified)

Hi there, if I selected the INS+GPS option in the PFB, if I just modify my GPS approaach will the auto pilot using the INS button follow the GPS approach procedure?

Ok, so I now have v 1.0.5. I understand the logic of 888 on the ground. But now, in cruise, the optimum altitude is still at 888 with an indicated SAT of -37 at FL310.

Assumption: If my understanding is correct I should be able to use the TriStar AP with TM+VNAV modes engaged shortly after takeoff, so say for example by 2000ft, I should be able to engage both TM+VNAV and that should allow the aircraft to climb to the set target altitude at IAS250 <10000ft and IAS320>10000ft. The takeoff, climb pages in the PMS should set the correct EPR into TM system target for each phase of flight. I am seeing several issues with TM+VNAV on stepped climbs <10000ft including - TM with IAS250 does not hold airspeed at 250kts or perhaps it just gets there VERY slowly. It frequently overshoots to 300kts! (v1.0.5 release), and 270kts on previous versions IAS250/3230 does not work properly if there is a step climb below 10000 ft. So say I level off at 6000ft first before climbing further, I then dial in new target alt and hit VNAV, the aircraft will not climb at all. To get out of this stuck mode requires toggling AT modes so moving TM->AT->TM then the PMS suddenly sets the correct EPR for climbing with. After encountering #2, when I get past 10000ft, IAS320 will struggle to achieve 320kts as the PMS unit does not set the correct climb EPR into the TM system, so the aircraft climbs at a low +500ft/min climb rate instead So the PMS+TM+VNAV seems bugged when climbing with steps, and it's all down to the correct EPR not being set when it should be. If I use AT mode to hold an IAS of 250kts instead the aircraft behaves normally. If I engage TM after using AT to climb above 10000ft then TM EPR is set and works correctly. So to me there is some bug with TM+VNAV when doing stepped climbs below 10000ft. It just isn't working, and hasn't been since release.

Remote loading works. All three INS's I had set in RMT.

Ok thank you for your response and acknowledgement. I'm hoping then it may be resolved in an update in the near future.

Just to add to this. I use the Auto FE and he sets the hydraulics. On the little caution panel a bunch of hydraulic related items flash up briefly. You will also notice the brake pressure bleed away to zero with each application of brakes. If you look at pressure in system A and D it often shows no pressure. So the fun part happens on a long-ish taxi (happened yesterday). You line up, press go and press full send on your 226,000kg plane out of Melbourne for Tokyo. A few feet down the runway ALL hydraulic pressure leaves you, now with no working rudder/ailerons. You quickly turn to the FE panel and hit both PTU switches and hope you get some pressure back. Halfway across a grass field the pressure comes back with rudder and ailerons, rotate and airborne. When the auto-FE sets hydraulics, don't believe him and check yourself. Make sure A, B, C and D all show pressure. Have now done an all clear of all caches (WASM etc) and doing another test flight, looks like all 4 systems got pressure this time. 1.0.5

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