Hi, 

After a at least 6 months of great sim experience on P3Dv5.3 and sometimes looking into MSFS i desided to upgrade to NV GPU 522.25 driver.

At first everything was great in MSFS but without thinking to deeply i ran into alot of problems in P3D. At first i noticed that my CMOS clock (bios) was lagging and dropping out so i replaced the battery as i recall doing it before. 

Power surge from the ASUS motherboard also happened alot with alot of total CTD .

At first i was suspecting the USB connections (due to suspectfully usb switch prior) but further along the road i was suspecting the O/C default on the EVGA GPU. Maybe lowering this and increase the Fan speed will do the trick. hmm. ( it did work shortly on another NV GPU driver)

Lastly i discovered my default settings was absolutely reset to default with all key/joystick commands and importing from backup did not do much good..

 

So fellow simmer

What is your experience when upgrading drivers and sometimes think you need to adjust things ?

What is the first the you look into ?

We have a fellow (small ? :-) )sim love for aviation and sometimes we just break things taking weeks to overcome :-)

Backup of keyboard controls -  is this needed for every USB devices in P3D or just for one ? Sometimes i have strange bindings to hardware in P3d/controls which doesnt exist on the actually hardware.

And btw . Remember "SLEW" has its own capitel in the control section. (jeez :-)

all the best and love

Michael Moe 

 

PS! Sometimes using software like in this episode the NVI O/C modul where you can increase Fan speed for your GPU ,  actually have an effect on stutter and temps.

I am a little aout of body , to find the issue .Temps - OC - or just the "GPU driver"

:-)

 

 

Edited October 28, 20223 yr by Michael Moe

I'd be shocked if the video driver had anything to do with this...with talk of power surges, clock issues and CTDs, I'd be looking hard at the PSU and/or motherboard.

I've spent the last day pulling my hair out after finally upgrading from my very stable P3D v5.1 config to 5.3 HF2.  It did not go well...the sim was randomly slowing way down to 12-15fps with the CPU and GPU barely breaking a sweat and no obvious reason.  After a good 12 hours of painstaking troubleshooting, it turns out a recent Windows update badly boogered-up my sound system, and re-installing drivers brought in some previously-removed and unwanted bloatware (Nahimic/Sonic Sound Studio) that clearly does not play well with the latest Windows changes.  After exorcising those demons I'm finally seeing some really stunning improvements.  But at first blush, I was thinking it was a P3D problem, because the onset appeared to happen when I updated from 5.1 to 5.3. 

Moral of the story--coincidences do happen, especially when tinkering with complex systems.

No problem with this driver in P3D.

3 hours ago, Michael Moe said:

What is your experience when upgrading drivers

Works like a charm.. 

I would tend to agree with Bob: coincidences do happen.

And our systems are complex: OS version?, MB drivers?, PSU spec etc...

Even when you are recording the  tweaks, drivers change and so forth bad news bear will happen.

There is rarely a clear and clean cut solution to a particular problem because the variables are different.

Cheers

1 hour ago, Bob Scott said:

I'd be shocked if the video driver had anything to do with this...with talk of power surges, clock issues and CTDs, I'd be looking hard at the PSU and/or motherboard.

I've spent the last day pulling my hair out after finally upgrading from my very stable P3D v5.1 config to 5.3 HF2.  It did not go well...the sim was randomly slowing way down to 12-15fps with the CPU and GPU barely breaking a sweat and no obvious reason.  After a good 12 hours of painstaking troubleshooting, it turns out a recent Windows update badly boogered-up my sound system, and re-installing drivers brought in some previously-removed and unwanted bloatware (Nahimic/Sonic Sound Studio) that clearly does not play well with the latest Windows changes.  After exorcising those demons I'm finally seeing some really stunning improvements.  But at first blush, I was thinking it was a P3D problem, because the onset appeared to happen when I updated from 5.1 to 5.3. 

Moral of the story--coincidences do happen, especially when tinkering with complex systems.

Don't forget to clean out the old folders from your previous version of p3d when you want things to start off on a new footing!😐

 

For a Clean Uninstall, please manually delete the following 6 folders:
Local Disk (C:) ► Program Files ► Lockheed Martin ► Prepar3D vx (or the modified install location)
Documents ► Prepar3D vx files
Documents ► Prepar3D vx Add-ons
Local Disk (C:) ► ProgramData ► Lockheed Martin ► Prepar3D vx
Local Disk (C:) ► Users ► You ► AppData ► Roaming ► Lockheed Martin ► Prepar3D vx
Local Disk (C:) ► Users ► You ► AppData ► Local ► Lockheed Martin ► Prepar3D vx

From the P3D website

Uninstalling/Reinstalling Prepar3D v5

While the uninstaller removes all files that are created by the installer, it does not completely remove content that was generated during program execution. To completely uninstall Prepar3D, you must manually delete folders and files that are created during runtime. Please be sure to back up any changes you have made to any of the files in the folders. Now, please manually delete the following folders:•

C:\Program Files\Lockheed Martin\Prepar3D v5 (or the modified install location

•%PROGRAMDATA%\Lockheed Martin\Prepar3D v5

•%LOCALAPPDATA%\Lockheed Martin\Prepar3D v5

•%APPDATA%\Lockheed Martin\Prepar3D v5

•%USERPROFILE%\Documents\Prepar3D v5 Files

•%USERPROFILE%\Documents\Prepar3D v5 Add-ons

3.Now you should restart your computer. After your computer has restarted, if you would like to reinstall, simply follow the Installing Prepar3D v5 section.

 

regards  Jorge

Deleting all these files can be done very simply. 

Assuming that you only have one version of P3D installed, and this is installed on the C drive: in File Explorer, go to the C drive, and in the search box in the top right corner type "prepar3d". When the search is finished, delete what is found. If P3D is installed on a drive different from C, do this on both the C drive and on the drive where P3D is installed.

If you have several versions of P3D installed, in the search type "prepar3d vX" instead, where X of course is the version number that you want to remove.

Jorgen

Thanks for all your insight. I am not sure what is going on but MSFS and PMDG must be lighter on my system as i have no issues here even on higher cpu clock settings . Maybe its related to DX11 in MSFS vs DX12 in P3D/fslabs.

Hopefully I can nail the issues with lower GPU Clocks on the EVGA GTX1080TI FTW3.

Thanks Michael Moe

And, most importantly when it comes to drivers, if it ain't broke don't fix it

16 hours ago, seamaster55 said:

Don't forget to clean out the old folders from your previous version of p3d when you want things to start off on a new footing!😐

 

For a Clean Uninstall, please manually delete the following 6 folders:
Local Disk (C:) ► Program Files ► Lockheed Martin ► Prepar3D vx (or the modified install location)
Documents ► Prepar3D vx files
Documents ► Prepar3D vx Add-ons
Local Disk (C:) ► ProgramData ► Lockheed Martin ► Prepar3D vx
Local Disk (C:) ► Users ► You ► AppData ► Roaming ► Lockheed Martin ► Prepar3D vx
Local Disk (C:) ► Users ► You ► AppData ► Local ► Lockheed Martin ► Prepar3D vx

Oh no--I have a very complex configuration with nearly 350 sceneries, and if I took the scorched-earth approach you suggest, it would wipe out all of my add-ons and require a complete rebuild, which for me is a major project that entails 80-100 man-hours to accomplish even with the detailed documentation I keep on my system changes.  I try to only do that for a major sim platform release (e.g. P3D v5 to v6) or a full new system build.  I typically do that maybe once every 2-3 years.  IMHO, the ability to upgrade/reinstall the core P3D software platform without having to reinstall and reconfigure all my add-ons was one of the biggest improvements to P3D ever made.

In my case, the monster in the machine was definitely the sound utlities.  Killing the Nahimic service stopped the slowdowns.  There's a fair bit of discontent in some of the gaming forums about the Nahimic/Sonic Studio bloatware that ASUS embeds in their driver packages causing stutters and other system instability.

How would you find out if this Nahimic/Sonic Studio had installed itself Bob? Where would it reside?

 

Edited October 29, 20223 yr by cowpatz

On 10/28/2022 at 11:17 AM, Michael Moe said:

What is the first the you look into ?

Try the following:

1.  cmd (run as administrator), in the command window type "sfc /scannow"  if it reports errors and fixes them, run it again to make sure no more errors, then reboot PC

2.  If problem persists, download latest DDU (guru3d), manually downloaded latest nVidia drivers (526.47 as of 10/29), boot into Safe mode, disconnect all internet connections (wireless and/or hardwired), run DDU

3.  Boot into Windows normally (all internet disconnected), install nVidia drivers, reboot PC

4.  Connect wireless and/or hardwire cable to NIC and boot back into Windows

5.  Delete P3D shaders

I've not experienced any issues with 52x.xx drivers, I did have problems with 516.xx drivers that was fixed when moving to 52x.xx drivers.

On 10/28/2022 at 11:17 AM, Michael Moe said:

Sometimes i have strange bindings to hardware in P3d/controls which doesnt exist on the actually hardware.

This is common, I would recommend you go thru every detected USB device in P3D controller section and manually remove all button/axis mappings, then map only those you use.  

14 hours ago, cowpatz said:

How would you find out if this Nahimic/Sonic Studio had installed itself Bob? Where would it reside?

In Windows go to Control Panel -> Administrative Tools -> Services and see if Nahimic is listed there.  You can right-click on it there and in Properties, open the Startup Type dropdown and select "Disabled".  This seems to work better than trying to find/uninstall or otherwise remove it, as something in the ASUS driver package keeps automatically reinstalling it.

Just a quick heads up on this  - i did a 6 hour FSLabs flight without issues in P3dv5.3HF2 this weekend with some changes to the flight.

* -  100MHZ (1868 mhz ) on the EVGA GTX1080TI FTW3 via NVI Inspector

* Reset all controllers and all commands

* Did not use FFTF

Normally switching from Chaseplane VC to Cinematics would lead to Total CTD with restart.

On approach and landing i did noticed 2 things. On approach my autopilot disconnect did not work (z directly or via input) and no spoilers deployed on landing.

Both worked after loading the same flight on approach so the bindings must be good.

Thanks

Michael Moe

 

Edited November 2, 20223 yr by Michael Moe