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

If folks would simply follow the very precise steps stipulated for the "patch version" they would not be having these "issues..."

 

These are not "suggestions," they are requirements!

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?

If in doubt; delete the shader cache! It won't hurt a thing, and the new shaders will compile in mere seconds... :Applause:

Is anyone using addons like REX, Active Sky Next and payware mega airports in some heavy weather together with an FPS hungry addon aircraft similar to what the, well lets say PMDG 737 NGX in FSX is?

If so, then please do tell us what FPS you are getting with the new V2.2.

 

Vanilla is one thing and I can also over 50fps with my GTX780 in FSX under DX10 in external view running all addons like REX, AS Next with heavy weather, FTX Global + Vector + Mesh and Frankfurt Mega Airport with the NGX.

But virtual cockpit drops to 18-23fps with some stutters on the two outter monitors - I run 3x24" = 5760x1080 Nvidia Surround.

 

Best regards,

Rene

 

 

If in doubt; delete the shader cache! It won't hurt a thing, and the new shaders will compile in mere seconds..

 

I always do! First thing. I also assumed the 2.2 cfg used different variables. So it should be new also. BTW I'm finding with the new nvidia 337 driver, locking frames at 30 and no Vsync gives excellent performance. previously I let the adaptive Vsync, Vsync on, tri buf, unlimited frames) control the frame but the 30 locked no Vsync seems smoother with either the new drive, 2.2 or both?

Where are these files Rob says to delete, I don't see them anywhere ?.    Thanks

See: http://forum.avsim.net/topic/439035-read-me-first-if-you-are-having-v22-issues-follow-these-steps/

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

Well, it's not so much an obvious trick when a patch is offered as an alternative--kind of implies it *should* work...

Gents, 

 

Compared to V2.1 I have lost about 20FPS. I went ahead and did a fresh install of Win 7 64bit on my SSD. Installed the full V2.2, FTX Global, REX, REX4, aerosoft airports, and Carenado Phenom. 

 

System: MSI Mpower Z77 I73770K , Clocked at 4.7, and GTX 780, Samsung ssd , 8 GB mem. 

 

I updated to the new Nvidia beta drivers may revert to current non beta drivers to see if there is a difference. 

V2.2 looks absolutely amazing, however I have been getting CTD when trying to change display settings as well as sutters while flying. (Most slider about 3/4 maxed out)

 

Has anyone else seen this ? 

 

Thank you!

Hi Rene,

 

I'm starting to slowly reinstall my addons back in, I will be using REX v4 TD, ASN, FTX Global+Vector, although I don't have any mega airports or really FPS heavy payware aircraft (actually might buy the Carenado Phenom as my test bird) but I do, as my own little benchmark test, run a 8/8 thunderstorm with light rain, night scenario at EHAM which has a lot of autogen houses close to the airport.

 

I only have a GTX 670 4GB but I'm running 3x 23" at 6060 x 1080 with bezel compensation.

 

From what I can gather, v2.2 runs bit better than v2.1, so some of the graphics are tweaked up slightly. I don't seem to get much worse FPS in virtual cockpit compared to external view. I had to turn off cloud shadows and terrain casting shadows as that basically ate my fps from about 20 down to 13.

 

Compared to before, I can now run LOD detail, autogen building and vegetation density, texture resolution and AA higher at about the same FPS as v2.1.

If folks would simply follow the very precise steps stipulated for the "patch version" they would not be having these "issues..."

 

These are not "suggestions," they are requirements!

 

If they would be easy to find that would be great!

 

Honstly I expected a readme file to come along with the patch but there was nothing! And the pdf LM provides is not too easy to understand and deals with the de-installation for the most part! I think it is best practise to have an installation guide with the files. On this LM failed ... 

 

 

If in doubt; delete the shader cache! It won't hurt a thing, and the new shaders will compile in mere seconds...

 

Please sir, can you explain how to delete the shader cache?  Maybe this is why I'm having very very poor cloud performance.  I patched but didn't uninstall the 4 folders, and not sure what is meant by adding add ons back to the dll.xml & exe.xml.   I had great perf in 2.1 w/o deleting those, so just tried the same approach w/ 2.2.  It runs, but as I say clouds kill performance terribly here.

I love this sim and it loves me :lol:  P3D v2.2 is the best flightsim ever made....Thank You LM!  I patched 2.1 to 2.2 without any problems.

Well, it's not so much an obvious trick when a patch is offered as an alternative--kind of implies it *should* work...

Fair enough

 

 

Sent from my iPhone using Tapatalk

Compared to before, I can now run LOD detail, autogen building and vegetation density, texture resolution and AA higher at about the same FPS as v2.1.

 

Thanks AutoGyro for your feedback.

Edited April 8, 201412 yr by n4gix
Remove excessive quote.

Please sir, can you explain how to delete the shader cache?  Maybe this is why I'm having very very poor cloud performance.  I patched but didn't uninstall the 4 folders, and not sure what is meant by adding add ons back to the dll.xml & exe.xml.   I had great perf in 2.1 w/o deleting those, so just tried the same approach w/ 2.2.  It runs, but as I say clouds kill performance terribly here.

Noel,

 

1. Click on the windows "Start" button in the lower left corner of your screen.
2.  In the empty box at the bottom, paste in this entry: %LOCALAPPDATA%\Lockheed Martin\Prepar3D v2
3. This should open a Windows Explorer window showing one folder named "Shaders"
4. Click on this folder and hit the "Delete" key.
5. Done!

So now you leave the Enable Terrain to Receive Shadows checked, but keep the terrain slider at zero?  Are you seeing cloud shadows?

 

You missed what the slider affects ... it's controlling the "casting" of terrain shadows over view distance.

 

 

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?

 

A fresh install of what?  

 

There is NO harm in deleting the shader folder.  If you do CTD or have and issue that suddenly terminates P3D, it's a good idea to delete the shader folder prior to starting P3D again.

 

Cheers, Rob.

 

 

Have new shadow sliders been added? If so, can somebody post a screenshot?

 

I updated my settings for 2.2 release here: http://robainscough.com/Prepar3D_Settings_2.html  (see last image on my web page).

 

Under extreme weather (5 layers) with fog, frame rates will drop considerably (7 fps) using these settings.  Like I said earlier setting the "Terrain Shadow Cast Distance:" (any value greater than 0) will induce significant fps drop also.

 

I installed ASN last night and found that some of it's weather depiction to very accurate (looked fantastic), but also VERY hard on performance using my settings (but so is OpusFSX).  But again, I have not done any affinity changes nor worked with NI and I've also introduced an nVidia 337.50 BETA video driver ... so continued tuning will be needed.  For what it's worth, the 337.50 Beta drivers have made no difference in performance on my system -- going back and it does look like the Prepar3D profile is the same (same flags/switches).  I'm going to delete this profile and create my own.

 

Even with my extreme settings I'm not having any VAS issues (2.4GB out of KSEA with A2A C-172, Orbx PNW, Orbx Vector, PILOT's FS Global FTX Edition, REX 4, and now ASN).

 

Cheers, Rob.