All Activity

First of all great job with this aircraft already. I’m still a fs2020 user and for me the main issue regarding the sound is that even in cruise we hear the engines quite a lot, both in the cabin and the flight deck. Whereas on the real liners (all commercial aircrafts) the engine sounds are quite high during take off and landings. But as we gain airspeed the airflow becomes the most present sound and the engines are not heard anymore. Personally I always end up reducing the engine sounds manually through the EFB during the climb. It would be great if the engine volume could be adjusted according to the airspeed. Thank you for lessening to our feedback and keep doing your great work!

Hi, When you disconnect the autopilot, does your speed start slowing down? As soon as the AP is disconnected, manual trim is required. The aircraft will pitch up or down depending on where your manual trim reference is set. Thanks!

I'm not entirely sure, it can't hurt to try the hotfix though!

I am using MSFS 2020. I routinely disconnect the autopilot about 5 mile final, autothrottle on FMS speed about 165 knots, flaps 2, gear down, stable with wings level, descending about 700 fpm. When I do this, the aircraft seems to be trimmed slightly nose down, and a slight amount of right aileron trim. So if I don't immediately correct it with the sidestick, the airplane will steepen its descent and begin banking slowly right. It does not seem to me like the correct behavior, and--yes--I have checked the calibration of my sidestick.

Pretty sure they use Javascript, it's also why the OANS when the airport map pops up on touchdown is why there are no stutters compared to the a350

Does the 350 use virtual displays? There’s a hot fix (616.86) which fixes: This hotfix addresses the following: Intermittent flicker may be observed in browsers when navigating to certain websites [6673430] Fixed an issue where virtual displays could not be created after updating to driver 616.56 [6674464] Remote Desktop Protocol (RDP) sessions may display a black screen after updating to driver 616.56 [6687328] https://nvidia.custhelp.com/app/answers/detail/a_id/5906/~/geforce-hotfix-display-driver-version-616.86

If you're willing, I’d recommend giving this tool a try. I use it myself and can vouch for it. It’s helped tremendously in certain situations. Note: If you do decide to use the tool, restart your PC afterwards, then try jumping into the A350. https://flightsim.to/addon/92765/msfs2024-cache-removal-tool

No, look at the ETA at the various waypoints. It’s clear there is something fishy going on here.

RTX5070Ti It’s an odd one as when I made this initial post I had got it working again, but after doing a couple of flights in the Fenix, I decided just to try and load up the 350 again as I was planned a flight in it tomorrow,, and I have the same issue as before, aircraft fails to load and GPU hangs. I originally installed the driver on its release day on September 3rd. I don’t think anything should have changed between then and you installing it now, to warrant me doing a driver reinstall.

We are still doing some testing on our end, but I can assure you it has been logged with the team and they are aware. Thanks for your patience and understanding!

Any news on these stop bars please? I cured the taxi light issue by moving EGLL to be above EGCC and EGSS in the scenery order in dev mode or at least thats what I think cured it. The stop bar issue remains.

Update: Just installed newest driver (616.64), restarted PC and loaded in perfectly fine. I'm not entirely sure what could be causing the issue. What GPU are you using? Thanks!

Interesting. I am currently on 610.88 and having no issues. I will update drivers and report back. Thanks for your patience!

Hi, I have not been able to test this yet on my end with 2020. however I did test it in 2024 and had no issues. If you can, is your SIM and AIRAC up to date?

Well, further edit @iniKyle Issue isn't solved. Same error comes back due to gpu hang and causes the sim to CTD. Issue is only with the A350. Fenix A32X, iFly 737Max, TFDi MD11, i have 0 issues Might be worth you guy as developers logging an issue with Nvidia? not sure just us FS users can create enough momentum for them to investigate? Another thread in relation to this driver https://forums.flightsimulator.com/t/nvidia-geforce-game-ready-driver-616-64/775593/3

Hi again, Just checking in to see, if there are any news or findings since I haven´t heard from you?

Thanks for the clarification! I have moved it over to 2024 for you 😊

Hi again! One more thing! I've made a mistake by creating this topic here in the MSFS 2020 forum. In fact however, I am using MSFS 2024, not MSFS 2020. What can I do? Do you need me to repost this over there as well? Sorry again for the inconvenience and thank you!

Hi, Absolutely. Should it happen anytime again, I'll make a recording for you. Thank you!

Hi, I’ll have to take a look at this on my end, as I don’t recall ever experiencing this issue myself. If you’re able to grab a video the next time it happens, that would be greatly appreciated and should help us investigate further. Thanks!

Hello guys! I have been experiencing an issue with the Airbus A350's (latest 1.2.6 build) terrain display on the ND, and I'd like to ask for help. The terrain display intermittently fails to initialize for an entire flight. When the issue occurs, TERR can be selected normally on the ND, but no terrain is displayed and the TERR indications remain: HIGH 0 LOW 0 The problem is intermittent. For example, the terrain system may work normally on one flight, fail completely on the next flight, and work normally again on a subsequent flight without any changes to the terrain database or aircraft configuration. When the issue occurred, I verified the following: OIS → 3rd Party showed Terrain downloaded. Navigraph was authenticated. ANF was working normally. The iniTerrainV2.bin terrain database was present. Liveries are installed normally through iniManager and are not being dynamically linked through MSFS Addons Linker. I have also found reports from other users, describing basically the same behavior. I would be happy to provide screenshots, logs, flight details, or perform additional troubleshooting if there is specific diagnostic information that would help identify the cause.

I’d love to give you an estimate, but unfortunately, I really don’t know at this point. It’s a strange issue, some users are experiencing it while others aren’t, which has made it difficult to track down the root cause. Thanks again for your patience and understanding!

Thanks @iniKyle. Is there a rough estimate as I can see this problem has been around for half a year already?

Hi, Sorry to hear you're also experiencing this issue. It has been logged with our team, and we're hoping to have an update or fix available as soon as possible. Thanks for your patience and understanding!

Hi, Please check your keyboard bindings in the sim and make sure nothing is specifically assigned to YAW. Let me know if this helps! Thanks!