All Activity

I just use package reorder tools, and everything is fine now. thx!!

HI Did you import the waypoints from your OFP/Simbrief at any point? Or were they all always only manually entered? If auto-import was used, there is logic that wipes the INS in order to import the next batch of waypoints, but this shouldn't trigger from fully manual entry normally. Could you please provide some screenshots showing your active modes + AFCS + configuration (flaps/gear) at the time? The team is working to fine-tune autopilot ALT HOLD behaviour particularly during configuration changes (Flaps or Gear) but if you can provide specific examples we can ensure those are specifically checked too. Again, it would be more helpful if you can provide specific examples of scenarios where it didn't work as you expected? This would include steps taken before intercept, and particularly data such as heading, speeds, altitude, weights etc. Specifically with regards to ILS, you should not intercept at angles greater than 45 degree, preferably try less than 30 degrees to avoid massive overshoots or it failing to follow at all. Thanks!

Yes, you entered it correctly, and the current SAT was +40c on the ground. The limitation is that the PMS only knows "current" SAT, not predicted SAT at FL360. Hence its running the OPT calculation with a +40c Temperature, which is way too high at the cruise levels and hence nets in "888" or invalid result. As mentioned above, the PMS references available do not indicate any PMS capabilities to predict SAT at different flight levels, or calculate any ISA deviation on its own. All the logic shows it using "current" temp probe sensor data directly, hence making it unserviceable if temp probes are INOP or malfunctioning even. The SAT entered during pre-flight setup is used only for Takeoff EPR advisory on the ground.

Should be fixed as of EGGP v1.0.4 Update.

That fixed it thanks Peter.

@IniJamir Please check this. Thx!

Hello I just landed at LSGG using INI3501.25. I was SU4 and used Navigraph data. I just upgraded to version 1.25 yesterday, and today my flight experienced two avionics freezes, resulting in a crash. I had flown several long-haul flights without encountering avionics freezes in version 1.24, but as soon as I upgraded to version 1.25, the avionics freezes and crashes reoccurred.

Are u on SU4 or SU5B? And are u using sim default or navigraph data?

I am currently using version A3501.25 to fly ZBAA-LSGG 1.25, and it has frozen twice and crashed. It's too unstable

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 ?