If its only happening in the FSLabs airbus while taxing with NWS on, make sure the warning notice is off.

8 hours ago, SoJourned said:

If its only happening in the FSLabs airbus while taxing with NWS on, make sure the warning notice is off.

It doesn't just happen in the FSLabs, it happens in other aircraft as well as i have previously stated, and even with the notice off it still happens.

@BlueSwurl, locate your aircraft at a very remote airport such as Alaska, Africa or northern Canada. Make sure there is no major airport within 80nm.

With the Airbus taxi around the airfield at noon with zero weather. Make sure you have taxi, nav and landing lights on as well as strobes.

Use that as a baseline for your tests. If all is well locate to a slightly busier airport and with the same settings try the same test. Monitor CPU1 and GPU using RTSS. If both stay below 100% that's great.

If you stay off VatSim then build up to a more complex airport and test again without any Ai. It might be that some Ai models are not user friendly. The key thing when trying to locate and fix a problem is to only make one change at a time and observe the difference.

It is time-consuming but ultimately the only way to find and fix the problem. Making multiple changes may fix it but you'll never know which of them was responsible. I've never had a problem with FSUIPC over many years so I'm certain you can discount that.

4 hours ago, Ray Proudfoot said:

@BlueSwurl, locate your aircraft at a very remote airport such as Alaska, Africa or northern Canada. Make sure there is no major airport within 80nm.

With the Airbus taxi around the airfield at noon with zero weather. Make sure you have taxi, nav and landing lights on as well as strobes.

Use that as a baseline for your tests. If all is well locate to a slightly busier airport and with the same settings try the same test. Monitor CPU1 and GPU using RTSS. If both stay below 100% that's great.

If you stay off VatSim then build up to a more complex airport and test again without any Ai. It might be that some Ai models are not user friendly. The key thing when trying to locate and fix a problem is to only make one change at a time and observe the difference.

It is time-consuming but ultimately the only way to find and fix the problem. Making multiple changes may fix it but you'll never know which of them was responsible. I've never had a problem with FSUIPC over many years so I'm certain you can discount that.

Had another go with taxiing around, expected issue with the FPS drop as soon as i went above 2-3 knots, but i noticed sudden jumps to 70 or 80% usage during taxi. It would mostly stay at 50, then a sudden spike to 80, then back down again. I've got it narrowed down to a couple possibilities.

1.) There was a windows update somewhere along the line that cocked things up for my sim, and that effectively makes the damage irreversible.

2.) The GPU drivers i had been using at the time were causing an issue, i have newer ones now and they still cause the same issue though.

3.) A few settings may have changed on my PC without me noticing which may affect P3D

4.) Its one rogue addon in P3D, however the only new additions to the sim have all been scenery. Software is rarely installed/

12 minutes ago, BlueSwurl said:

The GPU drivers i had been using at the time were causing an issue, i have newer ones now and they still cause the same issue though.

I'm running 461.72 with no issues. You could try those. Make sure you uninstall using DDU in Safe Mode and then install those.

If you still get the problem we can eliminate drivers.

@BlueSwurl, are you running anti-virus? If so, turn it off temporarily. See if that changes anything.

31 minutes ago, BlueSwurl said:

Had another go with taxiing around, expected issue with the FPS drop as soon as i went above 2-3 knots, but i noticed sudden jumps to 70 or 80% usage during taxi. It would mostly stay at 50, then a sudden spike to 80, then back down again. I've got it narrowed down to a couple possibilities.

1.) There was a windows update somewhere along the line that cocked things up for my sim, and that effectively makes the damage irreversible.

You can actually uninstall Windows updates by going to Updates -> View Update History -> Uninstall updates. If you check the history, do you by chance have KB5001330 installed?  This update is known to slow down performance on some systems.

I had this too with P3D5.1 HF1. I had no FPS problems long time now and I use Nvidia GPU driver 466.27. 

I had a severe fps drop yesterday at ORBX Bella Coola airport in any GA aircraft with steam gauges, no displays in the cockpit. Like you, I had it only on the ground. After setting Grass Lite, instead of Grass Heavy, it seems fixed.

I have a RTX 3090 and even with this and 5 GHz on the CPU, it is not possible to use options like Heavy Grass on a small airfield. So check the airport settings too. 

There was no noticeable fps drop on my system recently, when they said Windows updates are causing this. I can´t remember exactly but it was something with multiple monitors related.

The Nvidia driver is like the ones before the CTD series. No change seen here, not worse not better as always.

Regards

Dan

Edited May 14, 20215 yr by blaunarwal

1 hour ago, Afterburner said:

You can actually uninstall Windows updates by going to Updates -> View Update History -> Uninstall updates. If you check the history, do you by chance have KB5001330 installed?  This update is known to slow down performance on some systems.

I don't have KB5001330, but i do have KB5001337. Unfortunately i tried to uninstall it, going as far as to using cmd prompt, only to find it says it is 'required by the computer'.

I thought i'd make a post just to clear the fog here on anyone viewing or people in this thread at the moment (thank you for sticking around by the way)

Here is an example of FPS being fine when i'm in the air in the default F22 (good, 70-80 on average)

Then, touching the ground and rolling along, it halves to 44, averaging 35-45 fps

But upon stopping once more, voila! A miraculous FPS recovery

It's the strangest issue I've ever encountered in my 3+ years of flight simming. I've dealt with countless crashes, FPS issues and reinstalls but never something as odd as this. What makes it stranger is how suddenly it appeared. I remember it being an issue on flights all the way back in December of last year, and i've never been able to find a fix. It's made me turn away from flight simming in the past few months, which seems petty over just taxiing, but for me it makes the sim virtually unplayable, especially with an aggressive drop in FPS as soon as i touch down.

I don't actually think it's my settings or my PC, and i was thinking that it was a sim problem, but what made me forget that point was that P3Dv5 had the exact same issue on a completely fresh install. 
The only addon i had was literally the FSLabs, nothing else. And yet, i still had the same issue! This is why i'm genuinely lost for solutions or words, it isn't the drivers, it isn't my settings, it wasn't my CFG since i ran a test with that and it didn't work, it isn't any antivirus since i don't use any and P3D is excluded in Windows Defender anyways, it isn't any external tool.
Of course, this problem can be easily fixed by just gaining more FPS to work with by getting a new CPU, which i should do sometime this year, upgrading to an i7-9700k. But, i'd much rather find a solution right now, otherwise i know that my sim will never truly be fixed. (Not that anyone's sim ever is 😅)
 

It is a baffling problem. We’re these shots taken with your usual DLL.XML or with a default one? Maybe copy/paste each here so we can see the differences.

I’ve had issues myself when the wheels touch and leave the ground. I’m convinced very different code kicks in when on the ground compared to being airborne. Only LM would know what.

What extra programs do you run? Maybe they have some kind of impact.

4 minutes ago, Ray Proudfoot said:

It is a baffling problem. We’re these shots taken with your usual DLL.XML or with a default one? Maybe copy/paste each here so we can see the differences.

I’ve had issues myself when the wheels touch and leave the ground. I’m convinced very different code kicks in when on the ground compared to being airborne. Only LM would know what.

What extra programs do you run? Maybe they have some kind of impact.

I've never really touched my dll.xml, and the last its changed was yesterday, so it sure isn't default. But for now, here is the entry i found in the .xml

<?xml version="1.0" encoding="WINDOWS-1252"?>

-<SimBase.Document version="1,0" Type="Launch">

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

-<Launch.Addon>

<Name>FSUIPC 5</Name>

<Disabled>False</Disabled>

<Path>D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll</Path>

</Launch.Addon>

-<Launch.Addon>

<Name>as_connect</Name>

<Disabled>False</Disabled>

<Path>as_srv\as_connect_64.dll</Path>

</Launch.Addon>

</SimBase.Document>

 

As for external programs, i don't really have that many open. During all my tests, the only external program related to P3D open is Chaseplane, which typically does not have any signifcant CPU impact, nor did it change anything when i tested without it.

Thanks, nothing untoward there.

Can you turn off the sound by pressing the Q button and repeat the test?  I would also try to install a newer or different sound driver.

Edited May 14, 20215 yr by Afterburner

1 hour ago, Afterburner said:

Can you turn off the sound by pressing the Q button and repeat the test?  I would also try to install a newer or different sound driver.

Turning off sound doesn't help the problem unfortunately, and all my sound drivers are up to date.