Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

LRBS

Members
  • Joined

  • Last visited

Everything posted by LRBS

  1. Good day, I have a request. I’m currently outside the US, and despite using a VPN, I’m unable to connect to the BB757 to report these findings. Interestingly, I can access my PC and this forum without any issues. Would someone who has a few minutes be kind enough to bring these findings to their attention? I would greatly appreciate the help. https://www.avsim.com/forums/topic/703885-bb757-in-msfs-2024/ And additional issues related to VNAV logic, as seen in this pic. See T/D and T/C markings, please On the next ones, 1. Holding Entry: The aircraft mishandles the holding entry, resulting in confusion and an altitude bust. 2. EXIT ARMED: With EXIT ARMED annunciated, the aircraft wanders excessively, failing to maintain a stable flight path. Your help at this early stage of development is greatly appreciated.
  2. A few discrepancies that hopefully get adressed. During the APP, even the airplane is off to the left from centerline and needs correction to the right (see the ~1/3 of the LOC deviation), the FD shows no correction needed. Small adjustment on the sensitivity and logic. Another issue related to PBD waypoint creation. After creating CRI220/5 it does show correct in legs page as and that WPT part of the active route as CRI01. The FMC must allow the creation of additional waypoints from an existing newly created waypoint (CRI01) without generating an INVALID ENTRY message, regardless of whether the waypoint is stored in volatile/temporary memory or is subsequently deleted after waypoint passage or flight completion. All, easy fixes, thank you.
  3. I want to make one thing absolutely clear: my intention is not to be disrespectful, condescending, or dismissive of anyone's opinions or efforts. That is not the point of this discussion. I have spoken with several 777 pilots and simulator instructors at our facility, and the feedback has been remarkably consistent. We share an appreciation for this development, enjoy the same hobby, and genuinely want to see the software reach its full potential. 15% of the people coming through our facility are known to be very enthusiastic about flight simulation, and they have independently arrived at very similar conclusions. Two recurring areas of concern with this software are pitch response and the implementation of speed trim. These are not casual observations or isolated complaints. Both issues have been identified, documented, and explained to the developer. Unfortunately, for some of us, despite our efforts to bring them to their attention, there has been little indication that these concerns have been adequately acknowledged or addressed. One possible explanation is that these discrepancies may not be immediately apparent to users who have never experienced the handling characteristics and systems behavior of the actual aircraft. That is understandable; recognizing the difference often requires a direct reference to the real airplane. However, this does not make the concerns any less valid. More importantly, these observations are not limited to our group. Numerous desktop simulator users are reporting remarkably similar experiences. The discussions have been ongoing, repeatedly resurfacing even on the developers' own forums, with real-world pilots also contributing their observations. Of course, we cannot completely rule out individual installation problems, corrupted files, hardware configurations, or PC-specific issues. But when essentially the same discrepancies are being reported independently by so many users, across different systems and levels of experience, it becomes increasingly difficult to dismiss them as isolated problems. At some point, we have to look beyond individual user configurations and seriously consider that there may be underlying issues with the software itself. We all want the same thing: a more accurate, convincing, and authentic simulation of the Boeing 777. Constructive criticism should be viewed as an opportunity to improve the product, not as an attack on the people developing it.
  4. Yes, I did hear that, but frankly, that is not a valid excuse. Beyond the unrealistic nature of the demonstration itself, conducting a test flight without proper preflight procedures, correctly configured FMC data, and appropriate aircraft profiles introduces far too many variables. Under those circumstances, there is simply no reliable basis for determining whether the aircraft is behaving correctly or whether a particular system or flight-control characteristic is exhibiting an abnormality. In fact, several things in the demonstration immediately caught my attention. At approximately 1:26: Did you notice the aircraft bobbing up and down as it passed through 100 feet RA, with a deck angle somewhere between 15 and 20 degrees? That is certainly worth examining, particularly in the context of the expected pitch response and stability during the initial climb. Premature flap retraction: The flaps appear to be retracted without any demonstrated reference to the appropriate flap maneuvering speeds or a clearly established acceleration profile. Minimum maneuvering speed: The aircraft appears to enter the minimum maneuvering speed band. Airspeed Low alert: Was the significance of this message even recognized or addressed? These are not insignificant details that can simply be overlooked when attempting to evaluate an aircraft's flight dynamics and overall behavior. How can we meaningfully analyze whether something is wrong when the demonstration itself begins with so many procedural and configuration deficiencies? We cannot establish a valid baseline, isolate variables, or draw technically defensible conclusions from such a flight. A proper evaluation requires a properly configured aircraft, correct FMC entries, appropriate takeoff performance calculations, established operating procedures, and a controlled flight profile. Otherwise, we are not testing the aircraft under representative conditions; we are introducing unnecessary variables and then attempting to interpret the resulting behavior. And to be clear, I have absolutely nothing personal against this gentleman. This is strictly about the technical validity and credibility of the demonstration. However, if this is the methodology being used to determine whether the PMDG 777 has a problem or whether everything is operating as intended, I am afraid there is very little point in entertaining further technical discussion. We cannot establish that an aircraft is behaving correctly by conducting an improperly configured demonstration and disregarding the very conditions necessary to evaluate it.
  5. I am having difficulty understanding the purpose of this demonstration because several aspects of the takeoff and initial climb do not appear consistent with the handling characteristics or expected flight profile of a Boeing 777. A few observations. The transition from the takeoff roll to liftoff appears abrupt, with what looks like an excessive rotation rate compared with the smooth, controlled rotation normally expected of the 777. At approximately 100 feet RA, there appears to be noticeable pitch oscillation. From the video alone, it is difficult to determine whether this results from excessive or poorly coordinated pilot inputs, an inappropriate control technique, or an abnormal aircraft response. More concerning is the apparent absence of a properly established initial climb profile. The airplane does not appear to establish the expected climb profile, while the magnitude of the control inputs and the resulting aircraft response raise questions about pitch stability, load-factor variations, and overall energy management. The apparent airspeed decay toward minimum maneuvering speed during the initial climb is particularly concerning. Ultimately, I have difficulty understanding what this demonstration is meant to achieve. As presented, without speeds, CG, or target power settings, the aircraft's behavior does not reflect the expected operational characteristics or normal takeoff and initial-climb performance of a Boeing 777—or, for that matter, of any airplane.
  6. I removed the PMDG 777 from my PC nearly seven months ago. However, after seeing the same recurring pitch-control concerns being reported here and on the PMDG forums, I decided to give it another try, particularly with the latest update. I would like to share a few observations, and I genuinely hope they are not interpreted as condescending or disrespectful in any way. That is certainly not my intention. My comments are based on my real-world flying experience with this marvelous aircraft, as well as its flight-control characteristics. I sometimes wonder whether some of us desktop pilots either do not experience these issues or simply have not recognized the differences in aircraft behavior. My concern is not necessarily with the theory or programming behind the PMDG 777's fly-by-wire system. It is with how certain aspects of that system appear to have been implemented and how the airplane actually responds to pilot inputs. Let me use rotation as an example. According to Boeing's 777 Flight Crew Training Manual, rotation should be smooth and continuous. Boeing documentation describes typical rotation rates of approximately 2 to 2.5 degrees per second, with the lower rates generally associated with the longer 777 variants. The objective is to achieve the appropriate target attitude without an unnecessarily aggressive rotation. In the real aircraft, with the correct VR, appropriate trim setting, and a smooth, progressive aft control input, the rotation is remarkably well behaved. There is no reason for the pilot to experience excessive control loading or the sensation that the flight-control system is fighting the commanded maneuver. This is where I believe the PMDG implementation deserves closer attention. With the PMDG 777, I experience considerably more aft control pressure and what feels like resistance or conflicting pitch-control behavior than I would expect from the real aircraft. That is not consistent with my recollection of the 777's handling characteristics. There is also an important distinction regarding the Tail Strike Protection (TSP) system. Boeing's system documentation explains that the Primary Flight Computers monitor the tail's proximity to the runway and reduce elevator deflection when a tail strike is imminent. The reduction can be as much as 10 degrees, and the protection can be overridden by additional aft control-column input. Just as importantly, Boeing documentation explicitly states that TSP does not provide feedback to the control column. In other words, the pilot should not experience an artificial forward movement of the control column, a sudden increase in control-column resistance, or an airplane that appears to be fighting the pilot. The pilot may notice a reduction in the expected nose-up response, but that is quite different from the control system physically opposing the pilot's input. And we should remember another important point: TSP is a protective function, not an absolute guarantee against a tail strike. It does not eliminate the possibility of overrotation or prevent a tail strike under every conceivable circumstance. In my opinion, at a properly controlled rotation rate, with the correct speed and trim, there should be no reason to experience the exaggerated pitch-control behavior that I am seeing in the simulation. Unfortunately, even after trying the latest update, I am not convinced that the underlying pitch-response issue has been resolved. I also understand that some may believe submitting another support ticket to PMDG is the answer. I wish it were that simple. This subject has been discussed extensively over the years, with numerous reports, supporting documentation, and repeated discussions on their forums. Yet, from what I can see, the fundamental concerns remain. Unfortunately, the pitch-response behavior and the speed-trim implementation are not entirely new subjects. Similar concerns have been raised going back to the FSX days. I’m not bringing this up to criticize PMDG or diminish the considerable work that goes into developing these aircraft. Quite the opposite: I’d genuinely like to see the PMDG 777 deliver the handling qualities that made the real airplane such a pleasure to fly, listen to real pilot inputs, and stop relying on programmers' interpretations. Ultimately, this is not about personal preferences or how an aircraft feels to someone sitting in front of a desktop. It is about accurately reproducing the behavior of the real airplane.
  7. You are 100% correct. The modeling implementation is wrong/exagerated, as are other systems. They have also exaggerated the TSPS (Tail Strike Protection System) behavior to the point that some users are experiencing this issue. Several users have reported it, yet their concerns appear to have been ignored. As we know, Boeing has documented Improved Climb Performance procedures for several aircraft families, including the 737, 747, 757, 767, and 777. These procedures use aircraft-specific performance data to determine allowable increases in takeoff speeds, including V1, VR, and V2, as applicable. The adjustments are calculated according to aircraft weight, runway length, and climb-performance limitations. Depending on the aircraft and operating conditions, increases can be in the region of 10–15 knots, although this is not a universal fixed additive. The principle is to take advantage of available excess runway to permit higher takeoff speeds, particularly VR and V2, when climb performance is the limiting factor. A higher rotation speed generally results in a lower pitch attitude and angle of attack for a given flight-path requirement. A higher engine-out climb speed can also reduce angle of attack and drag, potentially improving the second-segment climb gradient. From a performance standpoint, each speed serves a different purpose: V1: Must be recalculated as part of the takeoff performance solution to preserve the required accelerate-stop and accelerate-go performance. VR: A higher scheduled rotation speed allows the aircraft to achieve the required flight path with a lower pitch attitude, subject to the applicable rotation and liftoff criteria. V2: A higher engine-out climb speed can improve climb performance by reducing angle of attack and drag, provided the aircraft remains within its approved performance envelope. It would be interesting to see @Christopher Low and others who use this rotation technique experiment with appropriately calculated increases in VR and V2, and report their findings. In our airline operations, we generally kept the rotation pitch rate at approximately 2.5 degrees per second or less. This helped maintain a controlled rotation, avoid excessive pitch rates, and minimize the risk of a tail strike or TSPS activation. Ultimately, rotation speed, pitch rate, and aircraft response must work together to produce a smooth, predictable, and controlled takeoff.
  8. The fundamental purpose of both Fly-By-Wire (FBW) and conventional mechanical/hydraulic flight-control systems is the same: to provide the pilot with precise, predictable, and consistent control of the airplane's pitch, roll, and yaw. The difference lies in how pilot commands are transmitted, interpreted, and translated into control-surface movements. However, regardless of the technology employed, an airplane should not exhibit abnormal instability, unpredictable behavior, excessive control sensitivity, or inappropriate flight-control responses during normal operation. We must recognize that many modern military and commercial aircraft employ sophisticated FBW systems and demonstrate remarkably stable, predictable, and well-behaved flight characteristics, despite the complexity of their flight-control computers. There is also an important aerodynamic distinction: some aircraft are naturally aerodynamically stable, while others are deliberately designed with relaxed or negative static stability and rely on continuous flight-control computer intervention to maintain controlled flight. Nevertheless, both approaches must deliver predictable and consistent handling characteristics. We should also distinguish between two fundamental approaches to flight-control system design: Aircraft-response philosophy: The pilot commands a control input, and the aircraft responds with a predictable and proportional pitch, roll, or yaw response. Aircraft-state philosophy: The pilot commands a desired aircraft response or flight condition, and the flight-control computers continuously adjust control-surface movements to achieve and maintain the intended result. These approaches are not mutually exclusive, and their implementation varies between aircraft. However, neither philosophy justifies abnormal aircraft behavior or an inconsistent relationship between pilot inputs and aircraft response. This brings us directly to this PMDG 777. Even with a sophisticated FBW architecture such as Boeing's, the pilot should never experience flight-control behavior that unnecessarily opposes the intended command, produces inappropriate pitch responses, introduces unexplained oscillations, or creates an abnormal relationship between trim inputs and the airplane's resulting pitch behavior. The Boeing 777's actual flight-control architecture and its documented operating characteristics should be the reference against which the PMDG simulation is evaluated. The objective is not to reproduce an assumed interpretation of what happens inside the flight-control computers, but to reproduce the observable behavior of the real airplane. In our case, the concern is precisely that the PMDG 777 does not consistently reproduce that expected behavior. The pitch and trim responses should be predictable, proportionate, and coherent with the pilot's inputs. When nose-up or nose-down trim is commanded, the resulting aircraft response should reflect the intended change in longitudinal trim condition, without inappropriate pitch oscillations or the sensation of fighting the controls. This is not simply a matter of personal preference or subjective flight-model tuning. It is a question of accurately reproducing the aircraft's handling characteristics. What makes this particularly concerning is that these issues have reportedly been raised not only by experienced users but also by pilots with actual Boeing 777 flight experience, including concerns expressed by one of PMDG's own 777 consultants. These observations deserve serious technical consideration rather than being dismissed or ignored. Ultimately, the complexity of the real Boeing 777's flight-control system should not become an excuse for deficiencies in its simulation. Regardless of how sophisticated the underlying architecture may be, the fundamental requirement remains unchanged: The airplane must respond to pilot commands in a predictable, proportionate, stable, and aerodynamically coherent manner. That is the standard PMDG should be expected to meet.
  9. Tom and Christopher, I think a couple of things are worth separating here. First, the Boeing 777 uses an autothrottle (A/T), and its FBW system does indeed incorporate speed stability. The pitch control law is called C*U. The U component provides speed stability relative to a referenced trim speed. In normal flight-control mode, when hand flying, the pilot's control-wheel trim switches change that reference speed rather than directly commanding horizontal stabilizer movement. The flight control computers initially use the elevators to establish the new trim condition. The horizontal stabilizer then adjusts automatically as needed to offload the elevators and allow them to return toward neutral. However, that doesn't necessarily explain the pitch oscillations being described. During takeoff, the 777's autothrottle transitions to HOLD at approximately 80 knots. According to Boeing's published A/T mode compatibility information, HOLD remains active through at least 400 feet unless the TO/GA switch is pressed again after liftoff. HOLD means the autothrottle is not driving the thrust levers in response to airspeed. The thrust levers remain at their existing position. After that, the active A/T mode depends on the selected AFDS and VNAV operating modes. When VNAV is engaged, the A/T does not necessarily transition to THR REF; it can select different thrust modes depending on the VNAV condition. THR REF controls reference thrust, whereas SPD controls to the MCP or VNAV speed target. A pitch change to capture a target speed or flight path is one thing. Rapid, repeated pitch oscillations are another, and I wouldn't consider the latter an expected characteristic of the real aircraft. I think we're reading far too much into what happens behind the scenes—especially when we cannot actually see what the flight control computers are doing. The bottom line is quite simple: when we apply nose-down trim, we should see a corresponding, smooth, and predictable nose-down response. The same applies to nose-up trim. The airplane should respond progressively and steadily to the trim input, without pitch oscillations, abrupt reactions, or any apparent fighting between the controls. This is precisely where the PMDG 777 implementation is fundamentally flawed. The specific problem is that, when applying pitch trim, the aircraft does not consistently produce the smooth, stable response we would expect. Instead, we see excessive pitch reactions, oscillations, and what appears to be the flight-control system counteracting or hunting around the commanded trim condition. The result is an aircraft that feels as though the pilot's trim input and the flight-control response are working against each other. Having flown the real airplane, I can tell you that this is not how it behaves with or without AP. Whether trimming nose-up or nose-down, hand-flown, the real 777 responds smoothly, progressively, and predictably, without bouncing, hunting, or fighting the pilot's control inputs. I am not asking PMDG to reproduce every detail of the underlying flight-control computer logic. I am asking them to reproduce the real aircraft's handling characteristics and its stable, predictable response. That is what matters to the pilot.
  10. If that's the case, and you actually climbed to FL600, then we are definitely looking at a significant problem that needs to be addressed. From a Boeing 757 systems standpoint, I would expect the CABIN ALTITUDE warning to activate when cabin altitude reaches approximately 10,000 feet under normal warning-system configuration. With the HIGH ALTITUDE LANDING function selected, the warning threshold is increased to approximately 14,650 feet. If a pressurization failure occurs, which I suspect, or if it is unable to maintain the correct differential. This is an important distinction when evaluating the pressurization system at extreme flight levels. There are several other areas I would be concerned about: 1. Minimum and Maximum Maneuvering Speeds What exactly are the minimum and maximum maneuvering speed indications on the airspeed tape representing? How are these values calculated, and do they accurately reflect the aircraft's actual operating envelope at the current weight, altitude, and configuration? 2. Optimum Altitude (OPT) and Maximum Altitude (MAX) What are the OPT and MAX altitude indications displaying, and are they correctly calculated based on the aircraft's current gross weight and performance limitations? This is particularly important when operating near the aircraft's maximum altitude. As you approach MAX altitude, the available margin between low-speed and high-speed buffet becomes increasingly narrow. Even relatively small speed or load-factor changes during maneuvering can bring the aircraft close to buffet onset. At these altitudes, an increase in load factor can rapidly consume the available buffet margin, potentially resulting in significant buffet and, if the aircraft is mishandled, an aerodynamic stall. These are not merely cosmetic indications. They are fundamental performance and flight-envelope considerations that should accurately reflect the behavior and limitations of the real Boeing 757. Unfortunately, there are still issues to be resolved.
  11. No, that's OK. I got the numbers from my old FCOM and what they have in the sim. The airplane is certified for FL420. Looking at the FCOM, I have both engines — clean en route maximum climb at 260,000 lbs or 220,000 lbs, ROC 700 and 1600 FT/MIN. For one engine, I see rated between 2100 FT/MIN down to 700 FT/MIN at FL400. I always hate interpolating the tables; they're always subject to interpretation and too many variables. I personally can't give an accurate number. So I don't know where FL600 comes into play for the 757.
  12. @Fiorentoni and @Ron Lefebvre It's a PFC 737 yoke on a PC. MSFS 2024 menu sensitivities for my yoke PFC: aileron -0.22/0.22 and extremity dead zone 0.09 elevator -0.39/0.39 and extremity dead zone 0.09 Also, I'm using the B737 Force-Feedback Yoke System by RTRhobby. I set it for pitch and roll force in my config file, and surprisingly I get the same feel, except for the stickshaker and autopilot movements. For both, I have the Settings in BB757 menu: 78 I found this discrepancy in flight config related to "control_reactivity_scalar = 5" (not in SDK); perhaps it should read controls_reactivity_scalar = 5. I have mine set to 0.90. Maybe BB757 guys can verify? MSFS 2024 menu sensitivities for RTRhobby all to 0 aileron 0/0 and extremity dead zone 0.09 elevator 0/0 and extremity dead zone 0.09 This is in Newtons (the metric unit of force) compared to a Level D simulator. Elevator breakout 18 N, Elevator moderate pull 65–100 N, Elevator heavy pull 150–250 N, Aileron moderate turn, 25–45 N and Rudder breakout 71–89 N control_elevator_forcebased = 1 control_elevator_maxforce_pilot = 120 control_elevator_minforce_pilot = 4.80 control_elevator_still_force_at_max = 6.00 control_elevator_still_force_to_move = 8.40 control_elevator_dynpres_ratio_force_at_max = 1.20 control_elevator_dynpres_ratio_force_to_move = 0.264 control_elevator_neutral_return_force_scalar = 0.85 control_aileron_forcebased = 1 control_aileron_maxforce_pilot = 45 control_aileron_minforce_pilot = 3.60 control_aileron_still_force_at_max = 3.60 control_aileron_still_force_to_move = 6.00 control_aileron_dynpres_ratio_force_at_max = 0.78 control_aileron_dynpres_ratio_force_to_move = 0.144 control_aileron_neutral_return_force_scalar = 0.85 control_rudder_forcebased = 1 control_rudder_maxforce_pilot = 150.00 control_rudder_minforce_pilot = 9.60 control_rudder_still_force_at_max = 9.60 control_rudder_still_force_to_move = 14.40 control_rudder_dynpres_ratio_force_at_max = 2.40 control_rudder_dynpres_ratio_force_to_move = 0.48 control_rudder_neutral_return_force_scalar = 0.85
  13. I will explain later. Not home right now.
  14. Just to clarify, at about 50% load (around 140,000 lbs), the performance tables show that a B757 will climb at over 5,000 ft/min up to 10K and exceed 4,000 ft/min from 10K to 20K with full climb thrust. So yes, "simply grossly overpowered"- those are quite interesting statements.
  15. I'm sorry, but what you're seeing is very close to the real thing. Other aircraft, like the MD-80/90s, show the same characteristics.
  16. Absolutely outstanding work, guys! I have to admit, I wasn't sure how effective this improvement would be, but it has exceeded my expectations. With this new setting, I was able to fine-tune the aircraft's handling to closely match how I remember the real airplane flying. Even more impressive, the resulting feel bears a remarkable resemblance to what I experienced just a few days ago in the Level D simulator. As someone who has spent many years flying the real aircraft, I genuinely appreciate the attention to detail and the effort that went into this improvement. Congratulations, guys, and thank you for continuing to raise the bar! EXCELLENT JOB!
  17. I'm afraid this doesn't solve the FDE issue; it only masks it. IMHO, stacking curves creates other feel-related problems and isn't a fix at the SDK level.
  18. It's the simplest, easiest, and least time-consuming approach: using a slider is much easier than adjusting each entry and table individually. I don’t necessarily agree with this option; unfortunately, they’re not the only ones doing this.
  19. Given your experience as an active 757 Captain and pilot consultant, I think it would be very helpful if you could share the specific flight control sensitivity settings you use in MSFS, particularly the aileron, elevator, and rudder axis sensitivity, including any extremity dead zone adjustments. That would provide both the developer and the community with a useful reference point and help establish a common basis for evaluating the aircraft's handling characteristics. I believe this is particularly important because several users have raised similar concerns about certain aspects of the FDE. Having your actual settings would help everyone better understand how much of the perceived difference might be attributable to controller configuration versus the flight model itself. I mention this because, having been involved in projects of this nature, I've always found that sharing practical information and maintaining transparency helps everyone involved reach a better understanding and, ultimately, a better result. I think a few specific values from your setup could be a valuable contribution to the discussion.
  20. It’s a little confusing if they’re not changing pitch sensitivity or pitch rate but are introducing a sensitivity slider. As I mentioned, I spent about an hour and a half in the Level D simulator yesterday, and the difference in pitch response was quite noticeable. The pitch rate was slower, smoother, and more consistent, with a steady, positive rate of change. My target rotation rate was approximately 2°/sec, which I remember from flying the airplane and was able to observe in the simulator. Perhaps that’s where they should focus their attention and look for improvements. I also noticed that the elevator trim responded a little faster in the simulator—perhaps 3–5% faster than what we currently have. The trim response in the product feels a bit slow to me. Other than those points, I find the FDE to be exceptionally well balanced and designed, very much in keeping with the real airplane. In my opinion, they’ve done an excellent job with the flight model. IMHO, it’s a genuinely rewarding airplane to fly.
  21. I see, but can't find any "about the requirement for custom control settings".
  22. Do you have a link to that? It would help a lot to take a look and reevaluate. Meanwhile, I just spent an hour and a half in the 757 Level D sim, courtesy of one of our instructors, and came to the same conclusion as @ahsmatt7 about our findings.
  23. Of course, there are limitations, just as there are even in Level D simulators. Surprisingly, some of today’s aircraft add-ons stand out for their flight dynamics, coming remarkably close to Level D simulator standards. Certification, however, is an entirely different game. Asobo is responsible for the underlying simulation platform, its flight-model capabilities, and the SDK and tools made available to third-party developers. When those tools have limitations, or when certain systems and programming aspects are not sufficiently exposed, developers are restricted in what they can achieve, regardless of their expertise. Third-party developers, on the other hand, are responsible for how well they understand and use the tools available to them. They must get the aerodynamics, flight-control response, engine performance, and overall aircraft behavior as close to the real airplane as possible. The SDK may impose limitations, but it does not excuse every shortcoming in a flight model. Some developers have demonstrated that, with the right programming expertise, a solid understanding of aircraft dynamics, and careful testing, it is possible to produce a remarkably convincing simulation within the platform's limitations. Ultimately, Asobo must provide the right foundation, and developers must make the best possible use of it. Both have a responsibility to improve the overall fidelity of the simulation. And, of course, replicating realistic flight dynamics is one thing; meeting the rigorous requirements for actual Level D simulator certification is quite another. As for the YouTube creators, I’m with you 100%!
  24. The PFC, no; RTRHOBBY B737 force feedback has its own proprietary software. Interestingly, both are quite close in feel, regardless of profile. To be honest, I did not expect that.
  25. Just a thought: the Boeing 757 is not a twitchy airplane. Unfortunately, the BB757 shows some of these characteristics, but I believe we can correct them with relatively straightforward flight-model adjustments. My question to this “757 pilot” would be: Which airplane is he using as a reference for comparison? Responsiveness, control sensitivity, and control feel are not interchangeable terms. When he says the nose wants to come up, we need to distinguish between CG, stabilizer trim, and the aircraft's pitch response. For every takeoff, the actual loading and CG must remain within approved limits, and the stabilizer must be set according to the applicable takeoff data. The FMC or approved performance calculations establish the required takeoff parameters; the stabilizer setting is not simply a means of correcting an out-of-balance airplane. The smooth rotation shown in this clip is consistent with a properly executed rotation, and establishes that the CG or trim setting is correct. I would also question the YouTuber's interpretation that the pilot is pushing the yoke forward to maintain speed. From what is visible, the pilot appears to maintain aft control pressure while trimming to relieve the associated control force. Without cockpit indications and control inputs, however, we can't determine the exact control-and-trim sequence from the video alone. Another important distinction: engine power has nothing inherently to do with control sensitivity. The 757's powerful engines do not make it twitchy. An airplane can respond positively and promptly to a control input without being excessively sensitive. We must distinguish between the aircraft's response to a given control input and the control force or displacement required to produce that response. Control sensitivity describes the relationship between input and response; control feel concerns the forces the pilot experiences at the controls. They are related, but they are not the same thing. The 757 should respond positively to elevator inputs without feeling excessively light, nervous, or prone to abrupt pitch changes in response to small, normal inputs. That is the behavior I believe needs attention in the BB757 flight model. The Boeing 757/767 Flight Crew Training Manual emphasizes small, measured control inputs when manually maintaining altitude at cruise altitude and high speed. At those conditions, relatively small inputs can produce meaningful flight-path changes. That is normal transport-category aircraft behavior, not evidence that the airplane is inherently twitchy. Finally, takeoff rotation must be considered in the context of the correct loading, CG, stabilizer trim, thrust, and rotation technique. Across aircraft such as the 707, 727, 747, 757, 767, and 787, the pilot should be able to achieve the prescribed rotation and establish the required initial climb attitude without fighting an abnormal pitching tendency. The aircraft should then be controllable along the intended flight path, with the appropriate speed target—the airplanes will easily settle to a V2 + 10 up to 20 effortlessly. My point is simple: the real 757 is a powerful, responsive, and well-designed transport-category airplane. It should not feel nervous or excessively sensitive merely because it responds positively to the controls. I believe the BB757 would benefit from a careful review of its pitch response, control sensitivity, and stabilizer-trim behavior (by the way, stab trim is slow) to achieve a linear response. Getting these characteristics right would make a meaningful difference in bringing the simulation closer to the real airplane.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.