All Activity

I have the same problem. When requesting the F-PLAN the MFD or FMGS receive nothing

Did you try placing all three in RMT and then loading them in?

This is a complicated model of a complex aircraft. Did you try using the GPS for an approach yet? How did it go for you?

Does this work when also loading waypoints automatically from the PFB, I cant seem to get to work when loading from the PFB but not sure if this is the intended behaviour? Thanks.

I must have missed that part then, thanks :)

As reported in the v1.0.5 update post, Progressive Aircraft Loading will soon arrive --> So, it's on the way. Just not sure how it will be implemented in the end.

The T.O.PERF sheet in the PFB has a 500,000lb limit on the TOGW even though this should be able to go up to the MTOW of 510,000lbs.

Hello Since SU5 on Xbox x, impossible to use A 350 and A 340 memory issues, do you have any information, thank you.

feels quite complicated to me 🙂

Very interesting. This would explain why while crossing the Atlantic and entering all waypoints manually, I pass directly overhead every waypoint because I keep resetting the airplane's position everytime I enter waypoints.

Are we able to add a load button and timeframes in the PFB? Example, Instant, 5mins, 10mins and Realistic. The simbrief import would just load info from simbreif into the loadsheet and the an additional button like "start loading" would start loading the aircraft at a a selected rate, to allow time to do preping for the flight. At the moment, using the sliders or clicking import loads the aircraft instantly.

Noted for the team, thank you

I agree it cruises at a very high pitch and it does not seem realistic. The attached link covers the first flight of the L1011-500 for Pan Am. Not only is the specially commissioned art nice, but I call your attention to Page 11-13 which is the Aviation Week article on the first flights. I found the conversation on the 4 degree pitch angle and the F/As being challenged interesting and the captain stating that the -500 has the same pitch 2 degrees as the 747 with proper loading. https://digitalcollections.library.miami.edu/digital/collection/asm0341/id/193094/rec/9

I have tested this again. The bug isn't what we think. They DO drift, but every time you enter a new waypoint manually, they magically reset to the correct, actual aircraft position. See video: https://youtu.be/56t3ZEmLk9E?si=uG24GOAz-x2Nync7

I'm seeing engine VIB numbers of 1.8+ during normal cruise. Having watched a few videos from the late 90s, it looks like the engines normally sat in the 0.6 range in the cruise. Did my aggressive autothrust actually damage my engines when it hit .798 EPR in the climb, or is this a bug?

Our L1011-500 seems to be cruising at a pitch of roughly 5 degrees. I was under the impression that it was supposed to be around 3.3 degrees. If so, it looks like the model needs a slight adjustment.

This one falls into the category where I'm not SURE it's wrong, but it feels off. During the climb, I selected INS nav, VNAV for pitch, and engaged the autopilot. I then selected TM mode for the autothrottle, and it began a very rapid climb and increased the EPR to nearly .798 even though the EPR card suggested the climb should be in the .585 range intially. That seems VERY aggressive, and even exceeds the takeoff thrust EPR of .642 for the flight. Does that seem right?

As per the title: certain PMS pages are meant to auto-display during changes to the phase of flight. They do not, and must be manually selected. Additionally, the Landing page has a field for the Vth with --- shown. It cannot be selected and entered.

People are reporting that in 1.05 the INS doesn't drift. In fact, it does. HOWEVER, upon entering any new waypoints, the INS POS is magically corrected to the aircraft actual position. See how all 3 INS units, with POS mode selected, initially show different positions after arrival at the gate, but then, upon entering the correct position into WPT 1, the position values all update magically.

Hi, I'll pass this along to the team. Thank you.

I have the same problem! I’ve tried numerous ILS approaches into EGLL 9L, frequencies & approach coarse correctly set on both sides, nav system set to radio, dh set on both sides, both autopilots set to CMD, the ILS/LOC lights on, and showing as armed or active on the annunciator… and the plane just flies through the approach path regardless of how shallow the intercept is. It was a little ‘flakey’ on release, but it would work… now it just seems completely broken for me. I keep thinking it must be something that I’m stupidly missing…. But can’t for the life of me figure out what. I haven’t had the gps fitted so it can’t be that in the wrong mode. I had installed the TriStar, but have now tried it streamed and had exactly the same issue. This is in FS2024.

Would just like to add that there have been many improvements since release, and I am thankful for those and the continued work that goes into the aircraft.

It really would be great to get these simple bugs cleaned up. Many of them apply to the A340 as well, and getting them all fixed surely would help the A380 development as so many of the systems are shared. Without being fixed the bugs are just mounting and mounting. It would be so awesome to get the A350 basic bug free so one could complete a basic flight without encountering so many bugs so long after release.

THS indication on lower PFD before take off does not match GWCG on TO PERF Page of OIS or THS TO PERF PAGE of FMS. (The aircraft sets the correct trim automatically but it does not match the target value right next to it)/ SPD LIM pseudo-waypoint behaviour is incorrect when there are constraints that affect when the aircraft would accelerate or decelerate. For example on the departure, if there is SPD constraint of 250 kts (or any constraint lower than this), where the aircraft will be above 10000ft, the SPD LIM waypoint should not be in the F-PLN on the climb (nor the corresponding magenta speed change dot on the ND) because the aircraft is not factoring in this 10000ft acceleration at all. It should climb respecting the speed constraints, then when it the constraints are cleared, if the aircraft will be above 10000 ft it will just accelerate to econ climb speed after the constraint. Winds are currently imported when importing the flight plan - this shouldn't be the case, it should be a separate procedure. Altitudes on F-PLN page don't always respect Transition Altitude and Level in terms of format. In terms of flight model, the aircraft still unsticks from the runway at too shallow a pitch, nut full vtol, but the aircraft should require a higher pitch to lift off from the runway. FBW needs work, for example, you use the sidestick to set a required angle of bank within limits of protections but when you release the stick, the aircraft changes the angle of bank, this should not happen but rather the aircraft should keep the angle of bank that was set even when the sidestick is released.

Unlike during position and waypoint entry, beginning to enter coordinates when in HOLD mode on the INS does NOT cause "insert" to illuminate. Also, after entering coordinates for latitude and pressing insert anyway, the value reverts to the previous position UNTIL longitude is also inserted. Then the position updates. I do not have any evidence of what should happen here, but that feels inconsistent with other modes of operation, and therefore potentially wrong.