Did full uninstall/reinstall.  Performance seems about equivalent with equivalent settings and major issues (e.g. ORBX white boxes) have been fixed.  I'm definitely seeing more microstutters.  Had frames locked at 33 - will try unlimited. Suspect I'll also have to fine-tune my NVidia Inspector settings.  A few oddities with add-ons that hadn't occurred before - for example, AccuFeel installs to the correct location but doesn't get written into dll.xml, so it doesn't show up in the add-ons menu.  I'll see if it helps to add the entry by hand.  Not much time for testing at the moment - more to follow...

Not sure if this has been mentioned yet...

 

Last night I ran the patch and things went well. This morning I uninstalled everything and ran the full 2.1 installer. Probably seeing a slight performance boost, but I figure it is because of the cleaned out directories.

 

One obvious benefit from the clean install: when you exit the flight sim, the exit menu is fully displayed (unlike the patch wherein the "continue flying" button is cutoff).

 

Otherwise, it looks beautiful. This is the first time I'm running it with HDR on. So pretty.

Great to see it's out! After reading this topic I will do a complete reinstall of P3D. I think I will even restore my clean Win 7 system backup so there aren't any traces of anything on my PC. 

 

I also wonder if this new version has an effect on currently compatible add ons. FSUIPC will be updated, that I know, but I wonder about add ons like FTX Global, FTX AU (being the only P3D compatible FTX region I have) and the A2A C172: they all worked with 2.0 but will they still work with 2.1?

 

I downloaded the full v.2.1 and it works perfectly for me.  No black screen if I start after my last exit from 'full' screen. Progressive taxiways now work and the windsocks change with wind now. I can now change my flight plan (and I love how you can now set up a flight plan from the start up scenario menu). The water looks a bit better and MSAA gives better results.

 

FTXG seem to no longer have the odd graphics (which I previously had to change my texture resolution to fix), and there are now power transmission towers, and Orbx street lights (but the lights are still too big and are on too many secondary roads, but that is an Orbx issue). Orbx weather themes now seem to work correctly as well (previously the barometric pressure jumped all over the place). 

 

The A2A Cessna works fine in v.2.1 ... and even works if I have Mipmap VC Panels checked.

 

If anything, my frame rates are slightly better with v.2.1 (but I upped some of my settings, so I cannot be certain that they are better). Overall, I'm very impressed with all that LM fixed in v.2.1.

Hello Happy Campers,

 

I cannot get Nvidia Inspector to show any change in p3dv2 whatsoever. I am running NI v1.9.7.2.

Any suggestions?

 

Regards

Bob

The patch process is slow because the MS patch file reads the file properties for every installed P3d2 file in order to decide whether to overwrite the file. P3d2 has so many texture files that this process is very slow unless you have P3d2 installed on an SSD.

 

Given that you have to delete all the P3d2 user files first before applying the patch , you might as well do an uninstall of 2.0 followed by a clean install of 2.1.

Looks like all my Virtuali stuff is disabled (GSX, FSDT airports etc.) ... hence this warning I get on startup.

Already discussed, answered and solved now:

 

http://www.fsdreamteam.com/forum/index.php/topic,9905.0.html

 

 

One obvious benefit from the clean install: when you exit the flight sim, the exit menu is fully displayed (unlike the patch wherein the "continue flying" button is cutoff).

 

Oh, this is VERY important information ... that means the patch is not matched up correctly with full 2.1 release.  As I understand it, LM are using WPF (Windows Presentation Foundation) to manage that particular aspect of the P3DV2.x interface (I can see they're using Xceed WPF control/tools ... I've used them before).

 

Thank you, that definitely tells me I'm going to need to do the full 2.1 install from scratch ... LM should be made aware of this because it has implications of version file differences in the core product.

Already discussed, answered and solved now:

http://www.fsdreamteam.com/forum/index.php/topic,9905.0.html

 

Thank you Umberto.

Having just tried it and a complete uninstall of the previous version and using the Full download of V2.1. I have to say its has clearly improved a lot for me.

I haven't and won't install any addon's until I get to know the sim well. Did I see right that the F35 is now listed under Indiafoxtecho rather than Dino Cattaneo and wasn't the T-45 and the F-14 also in V2.0? They are not in V2.1?

 

Anyway just for fun I yanked everything over all the way to the right :lol: and checked all the shadow boxes etc. and 4096 textures 8xAA, Texture filtering by 16, 100% traffic across the board. any setting that could be maxed out, I maxed it. Once the default flight loaded up with the F35 I was very surprised to see frames in the 20's. (set to Unlimited). It varied depending in the view. It was as low as about 15 in VC and my trackIr Lagged considerably but it was surprisingly smooth. Flew around for about 15mins climb to 25,000' zoomed the view out to the horizon and could not see any signs of pop-up and then BOOM. Take a way the "B"

 

Anyway at those setting especially the 4096 textures I can forgive that. I will be running whatever gets me solid 30fps.

 

I think the migration from FSX might start soon for me :lol:

 

I should say that I am running an i7 4770K at 5ghz with a GTX780. Once this goes SLI i'll pickup another 780.

 

I really think this will be spectacular now.

 

Just that OOM. Have to keep fingers crossed on that one!

This is what Im using. Excleent AA and performance with a CLEAN install.

 

 

Oh, this is VERY important information ... that means the patch is not matched up correctly with full 2.1 release.  As I understand it, LM are using WPF (Windows Presentation Foundation) to manage that particular aspect of the P3DV2.x interface (I can see they're using Xceed WPF control/tools ... I've used them before).

 

Thank you, that definitely tells me I'm going to need to do the full 2.1 install from scratch ... LM should be made aware of this because it has implications of version file differences in the core product.

 

Thank you Umberto.

Interesting... I did not realize there was any implication to this finding.

No need for a full 2.1 install...the exit menu problem is simply a window size setting in the uisettings.xml file, which is in one of the folders that should have been emptied prior to running the patch (please read the patch install instructions).

 

Wes at LM has posted a simple solution on the Prepar3D support forum.

 

The patch works perfectly if you aren't using the Migration Tool.

 

Best regards

Dennis

My small update (using 2.1 full install):

 

Very stable. I'm using settings (like HDR) that never worked for me before. I'm in and out of menus, changing graphic settings in-game, using ATC, going "in focus and out of focus" on the main window (even running firefox and a music program in the background)... no crashes so far. Seems stable.

 

Just installed Active Sky 2012. It works! (Previously I had the temp issues with P3D 2.0 wherein air temp was something like 200 degrees).

 

Next will be a fully planned out long haul flight with ATC. This always gave me problems. Fingers crossed.

 

 

The patch works perfectly if you aren't using the Migration Tool.

 

Thanks Dennis, I wasn't using the migration tool.  RTFM ... must have missed that, sorry.  Didn't realize or think a UI type file would be on the don't update list for the patch ... but on 2nd thoughts if the UI is replaceable (3rd party flexibility) I can understand why it would not be replaced.

So just to be clear. A vanilla install of V2, plus the patch 2.1 is fine?

 

Really don't fancy another 10Gb download.

Progressive taxi markers work again.