Jump to content

LineDX

Member
  • Posts

    176
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by LineDX

  1. Found this article on Avsim https://boeing.mediaroom.com/2025-11-06-Boeing-Pioneering-Next-Generation-Training-Tools-with-Launch-of-Virtual-Airplane May be inibuilds can do similar wirh Airbus specifically by further polishing their a350 as this is the only 350 in the market at this time. Regards
  2. LineDX

    Takeoff Behavior

    Airbus A350 does sometimes look like it “lifts off too early where it seems to leap into the air steeply and smoothly. Here’s what’s going on: ✈️ 1. High Lift-to-Weight Ratio The A350 has a very efficient wing design made of advanced composites and optimized aerodynamics. That means it can generate a lot of lift even at relatively low speeds, so when it reaches rotation speed, the nose comes up and it climbs steeply — giving that “helicopter-like” leap. ⚙️ 2. Powerful Engines The Rolls-Royce Trent XWB engines produce enormous thrust — enough to give the A350 a high thrust-to-weight ratio compared to older airliners. Pilots often don’t even use full power unless necessary. When they do (for demo flights or light loads), the aircraft can climb very quickly — making it look like it’s taking off vertically.
  3. Any update on this @Eddie Regards
  4. Hi @iniBuilds since updating to version 1.1.6 the central MFB contrast buttons don't work as expected. This can be seen in the attached video. Regards Microsoft Flight Simulator 2024 2025 (1).mp4
  5. HI Guys, DCT To LL is not working as expected since updating to 1.1.6 as can be seen in the attached video. In the previous versions, you had to click on the ac icon, then hit DCT TO. and then click on the LL(any point) on ND, but since 1.1.6 even clicking any spot on ND creates a dotted line to the LL/clicked waypoint. Not sure if it is normal or not? The other issue, since initial versions and still present is sometimes clicking a spot on the left side fms creates a dotted line to the left and vice versa. This is not s supposed to be like this. @iniBuilds @Eddie please look into it. Regards Microsoft Flight Simulator 2024 2025.mp4
  6. Same issue here.
  7. LineDX

    Navigraph update

    that did not do the trick for me. Tried it few times, deleted the wasm folder. run sim as admin. No joy.
  8. no battery issue here. but cant update the nav data(navigraph) stucks at 41.47mb.. screenshot attached.
  9. While on the base leg to ILS 10R at OPIS, the aircraft failed to turn onto final when under autopilot. At that point, all instrument inputs ceased responding. The autopilot would not disengage, and no controls had any effect. This appears to be a typical WASM freeze. I had only encountered a couple of WASMs since purchasing the aircraft in February, but after updating to SU3 and version 1.1.4, I’m now experiencing them on almost every flight. Interestingly, the aircraft performed fine with all versions upto 1.1.3 and during the SU3 beta. Something seems off either with the ASOBO sim update or the iniBuilds aircraft version. It happened on VGHS-OPIS on A350-1000.
  10. LineDX

    TCAS bug?

    Had it a couple of times.
  11. V1.1.4 SU3.. when open the doors you see across the fuselage.
  12. Wasm shortly after landing when about to exit the runway. YYZ-IAH landing runway 8r.
  13. LineDX

    Terrain display

    Hi everyone, I've noticed that the terrain display on the ND is constantly sweeping from bottom to top. Is this expected behavior? I don't recall seeing this in previous builds. Regards, Microsoft Flight Simulator 2024 2025.mp4
  14. I noticed it too. There is a switch in ois for arming and disarming the slide in ground operations tab.(blue and yellow) not sure what is normal sop?
  15. Same issue when sending the v speeds from the OIS. It happened only on CYHZ-OPLA ofp from simbreif
  16. That's right. I can't understand how testers miss some of the basic malfunctions before build release. Ini people are talented and dedicated to 350, getting rid of some basic errors will make a vast majority of simmers happy as they are mostly point a to b casual flyers.
  17. Reinstall. Deleting the WASM files first. I had the same issue but after reinstall and wasm deletion did not see this issue.
  18. Tested with 1.1.4. VGHS Rnp 14 worked normal.
  19. Tested it in 1.1.4 on 900. Works!
  20. still an issue in V1.1.4
  21. Same issue after 1.1.3
  22. Same issue with CYYC RNP 17L. Did not capture virtual glide path 3' slope at 4800ft on final approach point. The pfd shows ILS app whereas FMS shows RNP approach. It was fine before this update..
×
×
  • Create New...