Hi All,

I just did a test as I am still finding frames are dropping after a period of time and it is nothing to do with traffic this time (I had this after SU5 when using real world traffic)

I loaded a flight in the A32NX at CYHM, Ramp 10. When the flight loaded I had a solid 60fps. I did nothing other than leave the sim for around 4 hours and in that time the fps had dropped to around 32. I tried toggling live weather on/off, online data on/off, real world traffic on/off but nothing made a difference. I went to the main menu and reloaded the exact same flight and the fps were back up to 60.

I was also monitoring my CPU/GPU usage at the beginning and the end and they did not really change. The fps just seems to drop over time.

I would love to hear if anyone else can reproduce this, I am pretty sure you could pick any airport/gate as I think i is more like a memory leak in the sim

Richard

It does sound like a memory leak to me, but I'm no expert.

Interesting that it happens regardless of if you've been flying or not. 

2 hours ago, Republic3D said:

It does sound like a memory leak to me, but I'm no expert.

Interesting that it happens regardless of if you've been flying or not. 

I just loaded up the default A320 and sat at the same gate for 3 hours and the fps haven't dropped,

Sounds like it might be an issue with the FlyByWire A320

Will have to test some more tomorrow

Traffic related?  Sit at a medium sized GA airport and then report back.  Could traffic be an issue even if you are not seeing it where you are at?

Edited October 31, 20214 yr by fppilot

15 hours ago, fppilot said:

Traffic related?  Sit at a medium sized GA airport and then report back.  Could traffic be an issue even if you are not seeing it where you are at?

I haven’t even been flying with any traffic.

The issue seems to be with the FlyByWire A32NX, the default A320 doesn’t seem to exhibit the same issue. I will try again today with a different aircraft and see what happens 

I had this happen once. I assigned the 'cycle strobes' command on a Warthog throttle toggle switch and that switch was closed. The lights were jumping on and off continuously. Which I couldn't see because it was daytime. That quick on/off cycle slowly decreased fps on a long flight or just sitting on the runway, as time went by. Of course the cure was to finally notice and unbind that command in controller settings.

An easy test for this issue is to just move the arrows in the top menu of the controllers window to set all the controller profiles to default. Default profiles cannot be altered nor deleted. They were done by Asobo, remain constant, and so they don't allow this sort of problem.

On Monday evening I deleted the Developer version that I have been using and installed the stable build and repeated the same test for 2 hours without issues. Yesterday I flew 3 different legs all around 2.5 hours each with zero fps drop using the stable version. This morning I moved the stable version and downloaded the developer version again and within 2 hours the fps dropped from 60 to 38 !

I am going to delete this version and see if the experimental version exhibits the same behavior. 

 

Edited November 3, 20214 yr by RJC68

21 minutes ago, RJC68 said:

This morning I moved the stable version and downloaded the developer version again and within 2 hours the fps dropped from 60 to 38 !

I'd say you may have found something repeatable! Definitely something worth sharing back to the devs...

1 minute ago, DylanM said:

I'd say you may have found something repeatable! Definitely something worth sharing back to the devs...

I was thinking the same Dylan,

Just loaded up the experimental version and performing the same test

Richard

Edited November 3, 20214 yr by RJC68

The Experimental version also has zero problems,

It has sat at the same gate for 2.5 hours and the fps are still at 60. I have submitted a bug report with the FlyByWire Team on GitHub.

I am still curious to see if anyone else can reproduce this using the Developer version.

Richard