All Activity

Do you use noolaero VDGS?

Aircraft: A350-1000 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: Attached WASM Error: Attached Specs: 9950X3D, 5090 32gb, 4TB storage, 192GB memory Autosave File: Don't have one, screenshot proof attached WASM: Error whilst completing departure data input. Clicked on wind when it happened. YSSYVHHH_PDF_1777251542.e7e7526c.pdf

I have had a few issues with altitude/VNAV. Out of VHHX there is a max alt of 7000 feet untill 17nm past the VOR. The plane will (mostly) settle at 7000 feet in CMD VNAV/TM mode. ALT CAP and should stick at 7000 Now when you dial in a new alt and do nothing else, it will often start to climb by itself. One time dialled in a new alt increase and it started going down, probably as it was in a turn and thats the way the plane was going vertically at the time. According to the normal ops page above it should hold until you engage ALT SELECT+VNAV. There is also a lag of a few seconds between hitting VNAV and anything happening. Back to OPs problem. Did you enter data on pages 1/2/3? (Weights/ToD/Cruise info)

Are u on SU4?

Doing a VHHX to RJTT flight. Diligently populating the INS with the next way points after 9. They all happily show up on the minimap in the centre console. Entered in all new way points 1-6. 6 being the last point needed to get to the ILS. When the INS flicked from 9-1 it deleted all the waypoints and reset them to 0000N 0000E. Had to quickly re-enter the deleted 6 way points. What did I do wrong? Not using GPS or any other function. So now we are following the INS but for the life of me it would not hold an altitude. 3000 set, 2500-3200 given. She was all over the place. Its hard to believe that the first plane that could do a Cat-3C autoland has so many issues holding a set altitude. Or following an ILS. Or over flying a VOR without trying to do a 180 turn. With each new 'update' there is a plethora of items that break.

Hello, I would like to see the implementation of the Autopilot TCAS system. The A350 has the feature equipped as standard and is a major part of the Airbus TCAS philosophy. This is also a feature I would love to see on the upcoming A380 as it has the same system.

Hi, I would be grateful if you could consider these requests for a future update for our beloved A350 1 - When looking a ground charts on the EFB , there's no plane Icon which shows your location , they only appear on the SID/STAR charts , I know we can zoom in on the ANF but it doesn't zoom in close enough so we can read the taxi names while we're navigating our way to the runway using the seat view , yes we can camera zoom in to the ANF but then we can't see where our plane is going , perhaps if you could also add a "follow me" that would also be helpful! 2 - on the Fenix Airbus planes when you import a flight plan using Simbrief, the charts such as ground sid and stars for both airports are pinned already so we don't need to go looking for them , the SID/Star charts are what simbrief recommended. Thanks for your time Shrek!

Wow, I stand extremely corrected

Tried the 350 today - on for 4 hours, ATC gave me a direct to..... WASM crash 😒 That was after I did not fly it for a month or so and yes I did install the update, tiresome and a real shame. Beautiful aircraft in all other respects but unflyable long haul, glad I was not 11 hours in.

Would love to see a a319 and a318 I can operate in career mode

Hi all, I am having an issue where the parking guidance in gsx does not work with the tristar. It's like gsx does not recognise the l101 icoa code as it does not show on the vgds even at the gate. I have the tristar profile installed and ground services all work ok but just no actual guidance to the stop positions when taxing in. Is this a gsx limitation or do I need to change a setting or profile somewhere? Any help much appreciated.

This can be done manually by renaming the file extension of the file shown above. I changed it from .bgl to .bck. Works a treat. This isn't an official solution.

I started another flight from RKSI to KDTW (1.2.5), no time acceleration yet. After 1.5 hours, I got the sim freeze. Plane still flying, displays/AP don't respond. I loaded the last autosave to resume, but this time removed FSUIPC, FSFO, GSX. Have SmartCARS, Sayintentions.ai, Navigraph Simlink running. Will report on how it goes. Btw, before the previous flight (that worked), I uninstalled the A350 completely, re-installed, made sure the WASM folders were deleted, deleted rolling cache, etc.

In that case, do I need to check every single addon in the community folder, or should I only focus on the ones related to the ini A350?

No, it is not the Navigraph integration. It is the "package_order_hint" problem. You have at least one addon not compatible with the FS2024 in your community folder. It has no package_order_hint entry in its manifest.json. This leads to addons sorted and applied in an incorrect order, and the Navigraph navdata does not work like expected. The addon don't has to be active or used in the current flight, it is sufficient, if it is in the community folder. Also the addon itself works flawlessly, but it distubs others. There are many and long threads in the Navigraph forum dealing with this problem. Long story short: You have to ensure, all your addons have an appropriate package_order_hint entry. Either by using only addons released for FS2024 or by adding the entry yourself.

Your lucky I can’t even get 1.25 to install . It’s downloaded but I cannot install it ?

I also have this problem on the Xbox, the external lights don't work only in the 900 variant and in the 1000 it's working normally, and I don't have any light mod bought, I hope that when version 1.2.5 comes out on the marketplace this will be solved

Hi, I'm doing also a simulator (with Mobiflight) and use the A320 Neo V2 aircraft. I'm unable to use at least the upper display (the Chrono) using (L:INI_CHRONO_UPPER) The value stay all the time at zero on my display and also in the behavior, see the snapshot below. Any idea why ? Any update for the lower display (ET) .? Thanks in advance Sergio Sergio

Better Topic to cover the bug My topic can be deleted @Moderators

whats crazy is that your tires still have pressure in them... IRL those tires would be liquid

Clear your WASM folder. Reinstall the latest update and should fix you up.

It works fine when I'm not using Navigraph Navdata. However, once I reinstall and use Navigraph, the same issue persists, and neither reinstalling the aircraft nor the Navdata fixes it. Since it does work normally on occasion—similar to the issue where maps fail to load in the "Enroute" phase—there seems to be a problem with the Navigraph data integration. I'll check if resetting my Navigraph account in the settings resolves the issue and will get back to you with an update.

There are soooo many chinese airliners with a350s, chinese cabin announcements would be amazing!

I started an overnight 8+ hr flight, one that has resulted in the ghost WASM freeze several times in the past and woke up to find the flight still ok and almost at TOD. I even had FSFO, FSUIPC, Sayintentions.ai, spad.next running which i would disable in the past to diagnose the wasm freeze issue The flight was fine but the A/T was disengaged so it wouldn't descend until I enabled it again. Not sure what happened there but great to see the flight was fine otherwise. Thanks iniBuilds for the update and the continued work on the A350. Will try a longer flight with time acceleration next.

This is a WASM Crash. You should file a report in the corresponding thread.