I would recommend to those having problems to do a complete reinstall.

Uninstall any P3DV2.1 addons and utiliites first. Scroll down through Programs and Features

and uninstall all of the P3D related programs. As per the instruction/PDF in your original

P3DV2 installer folder, uninstall P3dV2.1 I also clicked on the P3DV2.1.exe in the 2.1 installation folder

and selected uninstall. After that restart your computer.Do a clean install of the latest

Nvidia Drivers; 337.50 beta. Restart your system. Install P3DV2.2

The complete reinstall is recommended by LM on the Download page!

After you fly for a while, restart you computer. After each addon installed

restart you computer.

 

Your millage may vary! Sound familiar :lol:

EDIT: the 337.50 nVidia drivers have different settings for the Prepar3D.exe ... Antialiasing compatibility (DX1x) is not BioShock 2 -- it's 0x00000000. I haven't experimented with NI and 2.2 and 337.50 drivers yet.

 

 

I'm not seeing any change, positive or negative with NI + 337.50 + 2.2... I've tried both AA compat Bioshock and leaving it at 0x00000000 yet nothing seems to change at all... trying to run SS + MSAA. Maybe need to play with more settings, or simply need proper driver support.

 

Anyway, no problems with 2.2... patched from 2.1.10194.0 to 2.2 only deleting the Shader Cache and App Data >Roaming>Locheed Martin... leaving my saved flights and add-on modified files.

 

The finished clouds look stunning and performance any memory management are greatly improved.

 

Shadow map at Med... Terrain and clouds at 20,000 and object 6,000 seems to give decent performance v visuals with the new shadow settings, though I will experiment further.

 

There are two new lines in the cfg for Autogen.

AUTOGEN_TREE_MAX_DRAW_DISTANCE=X    ....I think this maxes out at 12000.000000 mine defaults at 9500.000000

AUTOGEN_TREE_MIN_DISTANCE_TO_LOD=X ....Reducing this from default (2500.000000 in my case) thins-out distant agn density as far as I can see [?]

 

These might be worth fiddling with, to balance distance with density and LOD.

Guys, you're crazy not doing full installs from scratch.

 

I installed this last night along with the newest beta drivers from nVidia and was really, really impressed

 

I had so many settings as far right as possible, all scenery and autogen was furthest right, loads of shadows and reflections ticked (sorry, io'm not that familiar with the settings pages yet) and was getting over 40fps and smooth as anything

 

I looked out to sea and saw a low sun casting long cloud shadows

 

Kudos to LM, this is an amazing piece of software

 

With the release of the Carenado Phenom, solutions available from REX and Active Sky, as soon as Orbx get their UK products compatible this is going to be one amazing simulation

Agree with above poster that people miss an obvious trick by not doing a full install and then complain about issues

 

 

Sent from my iPhone using Tapatalk

I agree 2.2 is huge and so far a vast improvement. I picked up Rex 4 and ASN... The visuals look terrific with FTX global! Does anyone notice a huge performance hit when flying through a thunderstorm with Rex 4 and asn? Any settings you can recommend?

Hearing about how many FPS all of you are getting is pretty useless unless we get to know where you are flying, what settings you have and which addons you are running. I had 100+ FPS over the Sahara Desert, and 10 FPS over New York City with AI Traffic at maximum settings.

 

What matters most to me is that I use a pretty average computer, and I'm getting much better performance from P3D than I do in FSX with a lot more eye candy (HDR lighting, volumetric fog, no autogen popping, AI traffic and a lot of shadows). In P3D I can actually land an aircraft with 10 fps without sweating bullets.

I agree 2.2 is huge and so far a vast improvement. I picked up Rex 4 and ASN... The visuals look terrific with FTX global! Does anyone notice a huge performance hit when flying through a thunderstorm with Rex 4 and asn? Any settings you can recommend?

I did the patch version... i didnt delete all those folders mentioned above though... was too nervous and had already patched the sim before i read it...

 

Its not too late. Paste this line into your file explorer's address bar to navigate to your cached shaders...

 

%LOCALAPPDATA%\Lockheed Martin\Prepar3D v2

 

...back up, and then delete the "Shaders" folder found inside. When you launch P3D again, it will rebuild those shaders (*causing some temporary graphical anomalies, don't be alarmed) and probably clear up some performance hits.

 

Backing up and deleting these P3D related folders is an essential part of the upgrade process, and it cannot be understated. I urge everyone to follow Rob's instructions above, or better yet, perform a clean installation.  This is a hassle, but it's better than the alternative of not getting any updates at all...

I cannot make this sim OOM! I maxed out absolutely everything and checked every box except aircraft labels which I never use. (you don't see airplanes in the real sky with big flashing red letter and number moving along beside them LOL)

 

With every thing complete maxed out flying the bonanza out of CYVR in a major storm the memory usage in Windows task manager never went above 3.8. I was OOMing at around 4.8 to 4.9 in 2.1 so I am miles away. The cloud shadows are fantastic and you can even see that in the release they are way more realistic that in Robs Beta videos but to reduce the VAS usage to that degree! That's astonishing. The reign of terror of the dreaded OOM is over. :lol:

I cannot make this sim OOM! I maxed out absolutely everything and checked every box except aircraft labels which I never use. (you don't see airplanes in the real sky with big flashing red letter and number moving along beside them LOL)

 

With every thing complete maxed out flying the bonanza out of CYVR in a major storm the memory usage in Windows task manager never went above 3.8. I was OOMing at around 4.8 to 4.9 in 2.1 so I am miles away. The cloud shadows are fantastic and you can even see that in the release they are way more realistic that in Robs Beta videos but to reduce the VAS usage to that degree! That's astonishing. The reign of terror of the dreaded OOM is over. :lol:

Which addons do you use in 2.2?

No problem with the upgraded version of P3D v2.2! I deleted only the shaders folder, that's all.

Spirit

 

 

Which addons do you use in 2.2?

 

I will qualify that this is a vanilla install but with that headroom and the fact that I will certainly NOT be running the sim with everything maxed out at 10 to 20 FPS in heavy weather and scenery. I am confident that this will hold true. One other observation. Obviously at 10 to 20 FPS there are stutters! However, I noticed an improvement in those stutters Switching Affinity and Priority in the windows tack manager to All cores and High respectively. Could be subjective but I felt is was quite discernible. So assuming that tweak has the same effect at higher frame rates I would say it is a good idea.

Me neither. Deleting those folders is going to wack any addons installed. I can understand deleting them for a clean install. Those are the same as FSX to perform a complete clean install. But not to update.

Rendi, at the very least you should delete all of the existing compiled shader files! When you next launch Prepar3D v2.2 it will compile new shader files based on the new parameters that have been added to the code.

 

 

Rendi, at the very least you should delete all of the existing compiled shader files! When you next launch Prepar3D v2.2 it will compile new shader files based on the new parameters that have been added to the code.

 

Bill, If after a fresh install I apply and OC profile to the Graphics card with MSI afterburner should the Shader file be deleted and recompiled to account for the Overclock or is that nonsense?

All I did Bill was deleted the prepar3d.cfg and the shader folder. Ran the update and everything is updated and working well! Didnt lose anything. Of course those are rebuild on restart anyway. I also have controller disable because I only use FSUIPC so that may make a difference for some. Oh, had to download and install the new ASN P3DV2 beta. It was causing a weather,dll error. The update fixed that.