First impressions:

 

Default scenery - Carenado Mooney - KSEA area.

Incredibly smooth. No FPS improvement, but again it is smooth as silk, and I have done no disk de-fragmentation whatsoever.

The AA is definately better. Not perfect, but better. The water does look a little different but cannot put my finger on it. Maybe a little darker and a more rough wave action.

Everything is maxed except tessalation and radius (still 4.5). Shadows still at medium. I tried a higher setting with no apparent difference, so back to medium.

 

 

This is not detailed as you can see,  but I am very happy with the release. 

 

I would like to find out if anyone has tried Nvidia inspector to see if any of the internal graphics properties can be overwritten. I will try tomorrow.

 

Regards

Bob

[EDIT] It was the Carenado A36 - Sorry

I've only had about 20 minutes with it to check out a few features, but can say at this point:

- the patch installer really does take what I (and I guess others) believe to be an abnormally long amount of time. But it works

- the updates to the "start up" screen really are a nice addition

- performance wise, it seems about the same so far... except I have been going in and out of menus and changing things like crazy and no crashes so far (where I would previously experience crashes). It seems stable so far... but I need to get in a long haul flight. Fingers crossed.

- Check out the night sky if you haven't.... it looks so much better. The stars, moon and water reflection look great!

- Like others have said, when you exit and get the screen asking if you want to exit P3D or continue, the bottom bottom is mostly cut off, but still accessible. (This is just a strange error that we all seem to be experiencing. It is hard to believe that LM didn't notice this).

 

All that said, I'll probably be doing a full download and clean install since I have a number of add-ons lingering in the background.

 

Otherwise- I'm very excited that LM has put so much effort into this platform and look forward to the future.

yup, agree....I am wiping my old P3D2 install and downloading the whole 2.1 pack. Will do a clean install tonight. Want to play it safe. Can't wait to try it out!

Well we know what the forums are going to be all about for the next few weeks........  :lol:

I experience no install problems and experienced no failures while flying around West Palm Beach area.

Time to check some other areas.

 

Fingers crossed.

 

Russ

Im interested int he unlocking gauges/panels with multimonitor FPS hit fix.

I only had Milviz 737, FTX Global Iceland demo and FSUIPC installed and opted to download the Full V2.1 and plan to completely remove V2.0 from my system before installing V2.1. The download is at about 50% after 1 hour but after reading the above glad I'm going down that road. I'll be taken it slow! I hammered a bunch of addons in to V2 when it was released and gave up almost immediately but just a few days ago reinstalled planning for the patch and its been great with virtually no problems at all. Won't make that mistake again and I would encourage everyone else to have a gradual approach to addons and setting with V.2.1. I'll post how it goes tomorrow (A day off co-incidentally enough) :-)

OK, I'm convinced by reading these posts - uninstall and full reinstall for me... have got funky things happening in my 2.0 install so that's probably the best move anyway...

Soemone else had this problem in the LM forum...quote:

 

It works forever and then exits with the error message:

 

"Prepar3d was unable to load some program files and will now exit. Please reinstall Prepar3d to restore or repair the program installation."

So here is what the patch actually does (and why it fails if you don't have the standard installation path):

1. It checks for your current installation path.

2. It verifies which files are stored in your current installation path.

3. It then completely ignores your current installation path and installs the patched files into the standard folder anyway.

4. It then proceeds to change your correct installation path in the registry to the new, broken path where only half of the files exist.

5. Just for kicks it also changes the Prepar3d shortcut on your desktop to the new, completely broken Prepared.exe installation.

Here is how you can manually fix it:

1. Copy all the files from the new, broken installation path into your old installation.

2. Go into the registry and change the path back to the old installation path.

3. Change the shortcut on your desktop to the old installation Prepar3d.exe

Also, a note from Adam Breed....note: if you have third party scenery, this step will wipe out the necessary files for it to work.

 

For the best possible patching result, it is strongly recommended that you delete the generated Prepar3D files/content found at:

• %PROGRAMDATA%\Lockheed Martin\Prepar3D v2

  %LOCALAPPDATA%\Lockheed Martin\Prepar3D v2

  %APPDATA%\Lockheed Martin\Prepar3D v2

  %USERPROFILE%\Documents\Prepar3D v2 Files

These are not manually deleted during the patch. Not deleting these during the patching process gives users the most flexibility, but if you notice any issues it is recommended you delete them

 

Same issue on mine with this error.. havent tried (temporarily) deleting the 4 folders yet and rerunning the patch.. i have quite a bit installed and would rather not have to wipe things.  It happens on the creating shortcuts phase of the install from what i can tell.

Here's a juicy tidbit for those of you awaiting SLI/crossfire support.

 

  

"SLI support still isn't official, but we did make a few tweaks to cut down on frame to frame resource dependencies which should help with SLI performance. Now that it's out, we will submit 2.1 to NVidia to have them work their magic and create an application profile in the drivers that picks the best SLI mode. We will post as soon as we have a confirmed driver set including a Prepar3D v2 profile. We still have more SLI/Cross-fire work to do for 2.2."

Beau Hollis
Rendering System Lead - Prepar3D® Team

 

Excellent!

cheers, C.

The does indeed seem to be a VAS improvement ... even with Vector 1.1 enabled which is doubling many of the bridges and adding much more vehicle traffic.

 

As for AA ... yes, nVidia Inspector settings will work ... AA does seem different, had to resort to using NI overrides which I didn't need to do before.

 

Agree water does look different - more blue.

Here's a juicy tidbit for those of you awaiting SLI/crossfire support.

 

  

"SLI support still isn't official, but we did make a few tweaks to cut down on frame to frame resource dependencies which should help with SLI performance. Now that it's out, we will submit 2.1 to NVidia to have them work their magic and create an application profile in the drivers that picks the best SLI mode. We will post as soon as we have a confirmed driver set including a Prepar3D v2 profile. We still have more SLI/Cross-fire work to do for 2.2."

Beau Hollis
Rendering System Lead - Prepar3D® Team

 

Excellent!

cheers, C.

 

Most excellent news!  Although this release does seem to improve frame rates for me (on a single GPU), I've turned up Vegetation density two notches (one off max), and I'm having no problems maintaining 24 fps lock (testing min with average around 27 fps).

Quote from Beau on February 11, 2014, 17:39

Just to confirm what Saul said above, v2 is a separate product with a separate license. Also as an FYI, 2.1 is available now which has d3d10 fallbacks included to help ease the transition for users without d3d11 hardware.

My emphasis!

Now have micro stutters, add on manager will not work , migration tool not working now, was getting smooth performance with fps 24 to 34 now 15 to 24. all  display settings the same nothing changed . Fusipc not installing now. Will try full new reinstall see if this helps. So far I run better before patch than after.

Anyone else not able to get FSUIPC 4.928 to work? I did the patch which installed well but with FSUIPC in the Modules folder, I get a/c init error. Remove it and P3D starts up fine.

 

 

Vic

Im going o assume since its a new version FSUIPC will have to be update to recognize the update. It was the same for the 1.4 to 2.0.