[50% FPS decrease on landing without recovering with A350 in MSFS2024 (and MSFS2020)]

Dear @iniBuilds

9900X3D

4090RTX

Varjo Aero Navigraph Charts

MSFS2024

I posted this in your MSFS2020 section as it also counts for that SIM. Only the FPS numbers are not equally, but the gaps percentwise are the same!

Drastic FPS decrease at TouchDown without any recovery, starting with OAN zoom in and stays low after that

With the A350-900 the FPS gets a roughly 50% decreased  Approaching and Landing. Especially AFTER hitting the ground at landing my 58 FPS went down to 30 FPS and did NOT recover anymore. And this was with TLOD 75 during approach, landing and on ground taxiing!! 

I have already mentioned this in my previous other posts and not seen any reply. Maybe it hasn´t got an attention. I suspect some issues with the ND and navigraph integration, but this is not for sure of course.

Today I started at HAAB Addon scenery flying to OMAA (IniBuilds) with 65FPS in VR! TLOD set to 75. While taxing my FPS went a bit down to FPS 58. During takeoff and climb to 41000 Feet FPS increased from 58 to 68/72. During approach it got a bit decreased while nearing ground but it did stay above 58 FPS.

Immediately at TouchDown, exactly in that moment, the OANS got loaded in, my FPS went down to 32/35 and stayed there! It´s important to note, that I preloaded the arrival airport OAN at CRZ. So at touchdown the only thing happening at my ND was the Zoom. But even after zoom was done, automatecally, my FPS stayed at 32/35 and never recovered. 

I taxied to the gate and shut the aircraft down, with 35 FPS.

Went to the main menu, started a new flight with exact the same plane at OMAA, same gate, gate 610, and my FPS started with 65 to 68 FPS. Starting APU and turning on the batteries did not have any influence on my FPS, it stayed between 65-68 FPS.

Something must be wrong with the code. This is not only happening at these airports but at any airport and any landing after a minimum of 2 to 3 hour, or longer, flights. Competitors airplanes do not have these FPS decrease at touching down. 

Navigraph charts still having inpact on performance during cruise after roughly 1,5 Hour in flight

I use navigraph subscription and navigraph enroute charts. In this case, started at HAAB, I used after the climb out, the IFR High chart during climb and cruise. After roughly 1,5 hours I noticed some lagging while panning my VR HMD (Varjo Aero). I checked my FPS and saw it went down from 68-72 FPS to 55! 

When I clicked on the OIS Navigraph "Zoom Decrease" icon (minus=zoom out) exactly ONE time, FPS immediately recovered to 68-72. This is a phenomen wich occurs everytime after roughly 1,5 and 2 hours in flight.

People who cap their FPS may not notice it. But when you let your system push out maximum FPS, like I did in this flight, you can see how after a certain amout of time (as mentioned between 1,5 and 2 hours) FPS decreases quite dratsically and panning in VR gets a bit of a lag. Latency goes down the drain. 

Please consider

I am not sure if this also influences the above described touchdown issue with FPS decrease. But these 2 findings making cruise and especially landing having less fun. 

OAN loading in at touchdown is already causing stutters, as many people mentioned already. Landing is the most exciting part of a flight for most of us. It is also the performance heaviest part, because nearing an airport causes lots of materials to load....and OAN do have to much negative impact on TOP of this.

But a 50% FPS decrease wich does not recover, is not acceptable. The only ADDONS I used in this flight where HAAB (bought at IniManager and OMAA from your company developped). 

Please take a note of this and parse it to the team to have a serious look at this. My immersion and satsifaction would increase a lot if you are able to make this more usable! I have a top notch system build.....others will struggle much much more for sure.

And I do read this landing FPS decerease issues on many FORUMS and Posts. 

Thanks in Advance and THANKS you delivered this beautiful peace of "aviation". I hope you make it better and more robust.

Regards

Marcus

[roughly 50% FPS Decrease between Takeoff and Landing]

Dear @iniBuilds

9900X3D

4090RTX

Varjo Aero Navigraph Charts

MSFS2020

Drastic FPS decrease at TouchDown without any recovery, starting with OAN zoom in and stays low after that

With the A350-900 the FPS gets a roughly 50% decreased  Approaching and Landing. Especially AFTER hitting the ground at landing my 58 FPS went down to 30 FPS and did NOT recover anymore. And this was with TLOD 75 during approach, landing and on ground taxiing!! 

I have already mentioned this in my previous other posts and not seen any reply. Maybe it hasn´t got an attention. I suspect some issues with the ND and navigraph integration, but this is not for sure of course.

Today I started at HAAB Addon scenery flying to OMAA (IniBuilds) with 65FPS in VR! TLOD set to 75. While taxing my FPS went a bit down to FPS 58. During takeoff and climb to 41000 Feet FPS increased from 58 to 68/72. During approach it got a bit decreased while nearing ground but it did stay above 58 FPS.

Immediately at TouchDown, exactly in that moment, the OANS got loaded in, my FPS went down to 32/35 and stayed there! It´s important to note, that I preloaded the arrival airport OAN at CRZ. So at touchdown the only thing happening at my ND was the Zoom. But even after zoom was done, automatecally, my FPS stayed at 32/35 and never recovered. 

I taxied to the gate and shut the aircraft down, with 35 FPS.

Went to the main menu, started a new flight with exact the same plane at OMAA, same gate, gate 610, and my FPS started with 65 to 68 FPS. Starting APU and turning on the batteries did not have any influence on my FPS, it stayed between 65-68 FPS.

Something must be wrong with the code. This is not only happening at these airports but at any airport and any landing after a minimum of 2 to 3 hour, or longer, flights. Competitors airplanes do not have these FPS decrease at touching down. 

Navigraph charts still having inpact on performance during cruise after roughly 1,5 Hour in flight

I use navigraph subscription and navigraph enroute charts. In this case, started at HAAB, I used after the climb out, the IFR High chart during climb and cruise. After roughly 1,5 hours I noticed some lagging while panning my VR HMD (Varjo Aero). I checked my FPS and saw it went down from 68-72 FPS to 55! 

When I clicked on the OIS Navigraph "Zoom Decrease" icon (minus=zoom out) exactly ONE time, FPS immediately recovered to 68-72. This is a phenomen wich occurs everytime after roughly 1,5 and 2 hours in flight.

People who cap their FPS may not notice it. But when you let your system push out maximum FPS, like I did in this flight, you can see how after a certain amout of time (as mentioned between 1,5 and 2 hours) FPS decreases quite dratsically and panning in VR gets a bit of a lag. Latency goes down the drain. 

Please consider

I am not sure if this also influences the above described touchdown issue with FPS decrease. But these 2 findings making cruise and especially landing having less fun. 

OAN loading in at touchdown is already causing stutters, as many people mentioned already. Landing is the most exciting part of a flight for most of us. It is also the performance heaviest part, because nearing an airport causes lots of materials to load....and OAN do have to much negative impact on TOP of this.

But a 50% FPS decrease wich does not recover, is not acceptable. The only ADDONS I used in this flight where HAAB (bought at IniManager and OMAA from your company developped). 

Please take a note of this and parse it to the team to have a serious look at this. My immersion and satsifaction would increase a lot if you are able to make this more usable! I have a top notch system build.....others will struggle much much more for sure.

And I do read this landing FPS decerease issues on many FORUMS and Posts. 

Thanks in Advance and THANKS you delivered this beautiful peace of "aviation". I hope you make it better and more robust.

Regards

Marcus

[the aircraft is not usable due to WASM-Failure]

2 hours ago, Eddie said:

Very odd. Initial load is the only one that should be taking a while. Clearing your WASM folders as well as re-installing the aircraft entirely may be a fix if you haven't already, same for you @Jure

Let me know if re-installing resolves the issue. Thank you and apologies for the inconvenience! 

After installment in MSFS2024 I noticed that the sim object local cache folder a350-1000 no cabin folder was missing completely. Clean install...nothing there..only the other 3 variants where ther . 

Something is happening and installing is not completely as it was with 1.0.3 or previous versions. 

I noticed because I put my modified camera.cfg in there....with own cockpit view positions. 

[Navigraph enroute map getting Black issue fixed in MSFS2024 as well?]

With 1.0.3. the navigraph entoure map getting black in MSFS2024 (and MSFS2020)issues. The enroute map went black after longer flying and zoom didn't work either. Performance (also in VR) fps dripped when the issue occured. 

Regarding the releasnotes for 1.0.4 this is the fixed for FS20. 

Is it also fixed for MSFS2024? Because the issue was present there as well, exactly the same as MSFS2020. 

Thanks in advance for answering @iniBuilds

[VRAM Not released when switching from Cockpit to Cabin and BAck again]

@iniBuilds

Noticed in VR counted for all versions also 1.0.3 with clear installation after WASM deleted. Even my MSFS2024 got a fresh installment yesterday:

VRAM at Cockpit View = 9.5 GB (in my scenario this morning and earlier scenarios prior days)

VRAM Switching to Cabin View = 10.8 GB ! It  litterally jumped that high instantly. That is + 1.3 GB (I use Low resolutions textures in MSFS2024) FPS instantly droppes from my capped 45 to 30! 

VRAM Switching back to Cockpit = 10.8 GB nothing got released and stays this high. FPS again back to 45

VRAM Switching to Outside View = Stepwise decreasing from 10.8GB to 8.9GB within under 10 Seconds! FPS reduced to 30 and stays there! That is 15 FPS less so 30% less FPS compared to my cockpit view

VRAM Switching to Cockpit View = Jumps to 9.5 GB as initially when stared my flight, seems normal to me

Flying more then 2 hours does slowly increase VRAM IF NOT switching views between Cockpit and Outside.

It goes up from 9.5 GB to 10.5 GB in 2 hours and growths further. Paralell my FPS decreases from 45 (capped ín VARJO Software at 45) to in the 30th and does NOT recover, not even when VRAM got released while switching views from outside to cockpit again.

When switching from Cockpit to Outside again, VRAM gets released again as above descibed, FPS goes down the drain very slowly but steady and while flying hours does not recover anymore.

This is reproducable in every flight with the A350. It is NOT happening with the FENIX (4 Hour flights done) or default planes for instance.

I am suspecting as a cause:

- Navigraph activated or/and

- OIS issues or/and

- Cabin and for FPS decrease outside Textures as well not properly released

Regards

Marcus

 

 

[Total freeze after last update]

I am almost 5 hours in from LFMN to FMEE.....and no issues BUT TCAS is off, I don´t want to risk it today... 😉 

[Total freeze after last update]

41 minutes ago, Swisspilot1986 said:

I use traffic from FlyByWire and I only turn on TCAS on TA/RA during line-up, so it's on standby during taxi where the freeze arised. I've remade my entire flight and now I'm still flying in cruise. Cross fingers!

Be aware, the TCAS freeze with 1.0.2 occured also after hours in flight, but most often during Taxi, LineUp and as I experienced also while on TakeOff roll and shortly after Lift Off.

Report how it goes for you, that would be nice and much appreciated. I keep my fingers crossed for you!

[Total freeze after last update]

1 hour ago, Swisspilot1986 said:

yes WASM was cleared before installing the update in MSFS2024

Did you use Injected AI Traffic and had turned the TCAS on? Or did you leave TCAS on standby?

TCAS ON had several Freezes for me in follow.....leaving it on standby during my flights all went well. I did not try it after the 1.0.3 update though. IniBuilds stated it should be fixed now with 1.0.3

[TCAS working now?]

Does turning TCAS on still lead to Freezes? Or did a fix make it into the 103 update?

Thanks

Marcus 

[LIDO Maps problem]

1 hour ago, xe_operator said:

If you hit Tab to bring up the MSFS2024 EFB, do the LIDO charts appear there?

I need to test this when it happens again. 

What I recall is, that even the ICONS below the Charts-List left in the OIS, (APC, SID, STAR, etc. BUT excl. the PINNED ICON) did disappear as well.  

[Aircraft frozen out of JFK]

1 hour ago, TPGiovanni said:

Hi guys,

Just did the update, took off from JFK and just about pass 5000ft, all the screens froze. The aircraft symbol kept moving, but all the screens and switches got inop.

This never happened to me before, even in the previous version.

It's really annoying and frustrating.

There are people stating they have TCAS issues. When they fly with TCAS OFF, their wasm freezes are gone. Maybe give it a try if you use TCAS on, turn it off and maybe you are lucky to have a work around

[LIDO Maps problem]

9 hours ago, macflo19 said:

Hello,

After 1 or 2 hours of flight, the LIDO charts stop working. They no longer appear on the OIS. I have to switch back to Navigraph charts.
There are also problems with Enroute charts that work at first but stop working after a few moments.
Does anyone know a solution or is this a known issue that is not yet fixed?
Thanks in advance

Florian P

Yes. I have seen this in MSFS2024 as well. After ca. 2 hours the LIDO charts won´t show up when selecting them. The OIS stays black when clicking on charts. Refreshing, searching or resetting the credentials does not have a positive impact on that.

Ones they are disapeared they stay disapeared.

[Any feedback from IniBuilds about currently broken release V1.0.2??]

2 hours ago, Eddie said:

If the product is unusable for you and you have reported the issues you are experiencing and tried all trouble-shooting steps we provide; I see no other way for you to use it until we fix said issues. 

I do not claim anything is enough. I understand its extremely frustrating. The team is very much hard at work on squashing these very very annoying WASM crashes and are hopeful we'll have them resolved soon. 

You are not ignored. You are heard. Our community team isn't very large so we cannot give an immediate response to a post as we monitor both our Discord and this forum, but we try. I again ask for your patience, which I know is something you are reluctant on giving and understandably so, but we are working on it, I promise. 

Thank you

Thanks for replying. 

I am patient but also just honest, open and direct. Sorry if that hasn't reached you. 

Thanks again. I'm waiting finally to enjoy your most beautiful ever developed plane! That's a compliment!

 

[WASM Crash when switching strobe from ON to AUTO (possibly)]

20 hours ago, iFrezeTiger said:

As I was crossing RWY 30, I set strobe to ON and TCAS to TA/RA

This might be the cause of your crash! There are issues identified with TCAS. Leave TCAS standby...

Some are reporting less or no wasm freeze after that. 

[AGAIN AND AGAIN.....]

17 minutes ago, Erik32 said:

This is secound time A350 stop working and all the gaugs stop working.... This time it stop working after few secound when i was taxing.... this start to piss me off. I will add my LOG please INIBUILDS read this and find out what is wrong, I have clear the WASM folder many many times but still not working, have no MOD to A350 either. TCA Throttle,TCA Joystick and rudder stop working too.... nothing is working now.

Description.txt 9.45 kB · 0 downloads

Turn off TCAS or leave it of during flight maybe that's your issue. There is a dedicated topic about that. Maybe you are lucky that you may have a work around

[Not usable product in both SIMS - Any Statement?]

1 hour ago, Eddie said:

Hello,

We are aware of the state of WASM crashes and are working very hard on addressing them as soon as possible. Me replying to you us our form of communication. I can assure you the team is very much aware and trying their hardest to resolve them. 

Thank you

@Eddie

I think the WASM crashes are also related to turning TCAS ON and using Traffic injections...

Because...Turning TCAS OFF or leaving it off, I did manage to get up in the air...wich before was NOT possible...

Just something to check

Thank you too for your effort! regards, Marcus

[Any feedback from IniBuilds about currently broken release V1.0.2??]

9 minutes ago, Eddie said:

This is a forum intended for members and staff to assist where they can. We have a direct support (Contact – iniBuilds Store) line where you are guaranteed a reply so yes there is support. We have not abandoned anything. Any reports posted with logs have been taken into account and most likely already fixed. 

No one is dismissing customer complaints at all. We are taking all feedback, both constructive and even the not constructive. 

Thanks

@Eddie

By all respect, I do think inibuilds need to make an official statement by so many issues and a paid product which is not usable in FAR over 50% of the use.

I respect you and your company and trusted to buy, but I did not expected this. Yes, my expectations are my responsibilty, but the product remains inibuilds.

I think it is time to make a public announcement.

This release and "taste" your (inibuilds) customers get WILL have influence on your next products. I think inibuilds need to avoid a bigger negative impact  

Thanks in advance

[Not usable product in both SIMS - Any Statement?]

I do keep it a bit short:

Initial release - MSFS2020 and MSFS2024 many WASM issues

Update 1.0.1 - Both sims, better then initial release. In my case not a single WASm freeze, made 7 flights all longer then 5 hours spreaded over both sims

Update 1.0.2 - every single time WASM freeze

In my opinion, and as a professional SCRUM Master, this is catastrophic. I see tons of issues reported, not only WASM ctd, but Navigraph integrations issues, GSX issues and so many "standards" not working which should have prorperly tested before release (SEC Flightplans, Checklists, Charts etc.).

@iniBuilds

I did wrote this on your support forum as well, but I think it is time to raise pressure on you, NOT to harm you or be disrespectful, BUT to make my "voice" getting heard 🙂 

And I do hope others join me, because we paid almost EUR 80 for this "state of release".

Currently I tried your latest release.......and it is not usable at my end.

My sims are stable, both...and my issues are 100% A350 related.

Please make a public statement and take reponsibilty AND connect to your customers this way.

Thanks in advance 

I followed all your instructions (WASM clearing, even completely fresh installs A350 AND MSFS2024 as well)

[WASM Crashes 2020 and 2024 since 1.0.2]

It is really anyoing whats going on with this plane. So many CTD I never had seen before. Even my MSFS2020 with A350, and I have a super stable MSFS2020 when using other planes. 

[Any feedback from IniBuilds about currently broken release V1.0.2??]

31 minutes ago, haza2 said:

Have you guys reported back the crash reports by any chance? We would be grateful if you could please.

Kindest.

No, I didn´t and honestly, I do not want to report so many crash reports. I want to use my purchased product without this many issues and just fly.

My Displays and all controls freezed while just turning to the right entering the runway or also during pushback using GSX and clicking Checklist Button to open my Before Takeoff checklist. While entering runways I did not click anything, only used the tiller to turn right

31L OMAA

OMAA/31L N0490F390 KANI2U KANIP N318 LAKLU G216 ALPOR M504 TELEM A791 ARIVO/N0484F410 A791 SEBMA Q19 CEA B465 CTG A599 LINSO/K0891S1250 A599 POU R473 SIERA SIER7A VHHH/07L

WASM Folders where cleared before I reinstalled the product, because when updating, performance is repeatingly worse then when I uninstall and reinstall completely.

Before uninstalling I delete WASM

Uninstall A350

Install A350

Run the sims and choose a light airport to let the files compile and then my performance is 10 to 15 FPS better as when updating (without FrameGen I get 55 to 60 when performance is good, when JUST updating your product AND clear WASM before the updateprocess I get 40 to 45 FPS) wich is strange.

But in MSFS2024 and MSFS2020 now this A350 gets in the hangar till the next update.1

@iniBuilds

Please te responsibilty for this release. I am a SCRUM Master and AGile Coach from profession and I know what I am talking about. But this release is in no way properly tested! Tons of "fixes" which in my case made the product WORSE and increases instabilty. That is not the right way guys/girls!

I have respect for your efforts, but I also want to see inibuilds making a official statement on this "release".

The product is unusable atm

 

[Any feedback from IniBuilds about currently broken release V1.0.2??]

Yep......3 out of 3 aready.....and everytime before takeoff.....no funl

[Systems stopped working during climb]

A support forum full of wasm Crashes...

That's really no fun anymore. And never bin that much on Amy other released plane. How is this possible? 

2 weeks after release the reports, after 1.0 2. don't get less. At least as it seems to me. 

Such a beautiful plane and so many issues...

I wish IniBuilds the best sorting this shortly and quick...because the next time a plane gets released this may become an issue and that would be a pity!

 

[Yay, Panel State save/load...]

1 hour ago, David Whittaker said:

Sorry, forgot to mention...

Would also be nice to have/choose a DEFAULT Panel State,

like PMDG's 737/777, and others.

Thanks again.

Exactly. 

As a user I want to define how to set my plane up. then give this setup a profile name and save it and define, wich saved Profile to be my default startup state (all my knobs, lights, APU, GPU, or External equipment, adirs, etc. should be saved. FMS should be at init or NAVData page.. At least 5 profiles should be able to generate and save, and also make it able to give us users to choose from them and activate them, without the need to set them as default startup profile..

But a minimum viable product which could be easy, is to be able to set one of your already offered profiles as the default startup profile. That would be a great thing. Just, when running on APU, on GPU or with Engines running, the ADIRS should be on and the plane should be alligned! Like in real life as well. Mostly the ground crew prepares the plane before the first flight is done and then the crew jumps in and starts with programming.....almost all the time the ADIRS are alligned.

[ENROUTE CHARTS BLACK]

@richboy2307

I have just done my flight from EFHK to HKJK. After roughly 6 hours I noticed FPS decrease, sudden FPS decrease. from 50 down to 35-40 and heavy stuttering while panning views  in VR. Also exiting VR did not help out. The SIM performed worse as just before stuttering began.. 

I entered VR again. I have noticed, that switching in the OIS from ENROUTE to Everything else then ENROUTE AND CHARTS, did immidiatley recover my FPS to 50 again in VR. I decided to toggle between ENROUTE or CHART and the Other TABS like LDG PERF. I was able to reproduce this FPS drop as soon as I choose ENROUTE or CHARTS. And the drop always was from 50 down to 35-40 and when choosing OIS TABS like LDG PERF or TAKEOFF PERF: FPS increased immidiately and the SIM ran smooth again.

The views where extremely sluggish while having OIS at CHART or ENROUTE and it was immidiately smooth again after going to LDG PERF TAB in the OIS again.

While viewing ENROUTE, also the Navigraph IFR HIGH, IFR LOW and WORLD DAY, NIGHT etc. won´t load completely in. Only half of my OIS was filled with the ENROUTE Chart. the only ENROUTE CHART that would show completely was STANDARD, but FPS decrease and slugish view also stayed while viewing at ENROUTE STANDARD CHART.

100% Reproducable at my end. I am sure it is related to the Navigraph CHART integration in the OIS.

This was in MSFS 2020 and your latest update. I already have deleted my WASM folders before updating to 1.0.1 and also have done that after updating, just to be sure to start with a "clean" setup. 

AMD 7800X3D and RTX4090 with 64GB 6000MhZ RAM. Everything on NVME SSD. Windows 11 latest updates as well.  

[ENROUTE CHARTS BLACK]

1 hour ago, richboy2307 said:

Yes it can be done in flight. The only thing that is inhibited after engines start is changing navdata methods as that will cause a FMS reset.

@richboy2307

The issue may be another one concerning charts like Standard charts and Navigraph charts as well.

I recon, that after several hours (at least 2 or 3 hours) in flight, when using the IFR/VFR maps from Navigraph (day or night does not matter) they do not update when increasing or decreasing zoom. They seem to get stuck. When decreasing zoom, blocks on all sights appear (the blocks don´t get updated with new chart material as you decrease zoom) and stay black, when you decrease enough, so zoom out enough, the whole display becomes black (thats what you see on the OP and second post). Zoom in again may return the previous shown chart parts, untill your plane proceeds and while further flying, no new chart material gets loaded in....so finally all display gets black....

This happens more often to navigraph charts and the standard charts seem less affected, but they are.

My performance seems not an issue.....45FPS and less then 65% VRAM on my 799X3D CPU and 4090GPU