I installed the patch over an existing 2.0 installation with a few addons.  The patch installed OK, but the sim would crash a moment after loading.  I then removed the four folders of app data as recommended by LM and everything seemed to work after that.  

 

I noticed that any changes to controls will not be saved until you exit the sim.  If you change flights after changing the controls, your changes will be lost.  So best to make the changes and then exit the sim immediately.  

 

The only hitch I had is that when I tried to save a profile of my controller settings, I cannot type text in the box to give the file a name.  I see others have reported that as well.  Anyhow, it didn't matter as I found how to make the changes stick, as related above.  

 

2.1 definitely runs smoother for me and looks better in a number of ways that are hard to pin down exactly.  The terrain shadowing looks better somehow.  I also seem to have a lot more autogen than with 2.0 to the point where I think I can lower my settings a bit -- I have never seen such dense autogen as I had with 2.1 running FXT Gobal and True Landscape France.  I had an OOM over Paris, but not surprising really with the insane amount of autogen I had displayed while flying a jet at 500 knots. 

 

 

Also, the auto-generated doesn't seem to extend as far put as before...

 

What have they done to the autogen? It definitely doesn't extend as far put as before. This is particularly annoying, when flying over forest areas because you can clearly see where the autogen ends... This was much better in 2.0...

I sincerely appreciate the fine work you all are doing in testing out the patch and reporting your findings.

 

I've downloaded the full installer, and plan on doing a clean install this coming weekend.  In the meantime, reading up on what you all are discovering is saving me potential headaches. :lol:

What have they done to the autogen? It definitely doesn't extend as far put as before. This is particularly annoying, when flying over forest areas because you can clearly see where the autogen ends... This was much better in 2.0...

 

 

Yes, I think you're right the radius of Autogen seems much smaller :(

 

 

 

Plus, terrain texture loading seems much worse with 2.1.... but, I see LM are now recommending running an unlimited frame rate - in some cases anyway - and removing the Affinity Mask lines from the cfg if you added them.

 

With 2.0 I could fly a fast jet, or slew across tens of miles and the scenery would keep up, or recover very quickly, in a few seconds... but, with 2.1 even flying a moderately fast AC resulted in blurry terrain, and running out of autogen, with recovery taking minutes. Removing the AF mask entry and running the frame rate at 'Unlimited' now seems the best solution, but I don't think its working as well as it did before.

 

One step forward, one {or two} steps back :(

 

Maybe I'll try a clean install and se what that brings.

 

 

but, with 2.1 even flying a moderately fast AC resulted in blurry terrain, and running out of autogen, with recovery taking minutes.

 

Actually, that's what I experienced with 2.0. Texture loading with 2.1 is much better on my machine... But the autogen is really annoying... This is more than two steps back. Maybe that's their idea to get rid of the OOMs... But it just looks awful...

Actually, that's what I experienced with 2.0. Texture loading with 2.1 is much better on my machine... But the autogen is really annoying... This is more than two steps back. Maybe that's their idea to get rid of the OOMs... But it just looks awful...

 

Interesting... of course no two set-ups will ever provide the same results, however, my terrain loading was sluggish with 2.0 until I added the 'recommended' affinity mask entry to the cfg, which put things in order......  2.1 seems to need a different approach, but for me its still not as good as 2.0 or FSX and now the Autogen [which was one of v2's saving graces] is now buggered.... maybe??????

Anyone knows how to fix the bug of right button? Whenever I click with right button, the P3D closes :(

 

 

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

 

Yes, appears to be fine (just wiped them all out per LM's suggestion and re-installed the patch) so long as you don't or haven't used the Migration Tool.  Be sure to manually wipe out the 4 directories Wes indicated.  This will wipe out controller settings, scenery/airport installs, but existing Aircraft should be unaffected ... BUT you'll need to re-add entries to you EXE.XML and DLL.XML.

 

Be sure to backup those 4 directories first.

 

Typically (but will vary by one's PC):

 

C:\ProgramData\Lockheed Martin

C:\Users\[YourUserAccountName]\AppData\Local\Lockheed Martin

C:\Users\[YourUserAccountName]\AppData\Roaming\Lockheed Martin

C:\Users\My Documents\Prepar3D v2 Files

 

Stutters still appear to be a problem, so far, the only solution I've found is set a framerate Lock at your lowest possible fps.  I'm trying to discover exactly what's causing the excessive stutters ... they were not present (at least not in any significant quality) in V2.0.

 

Rob

Decided to give up on my failed upgrade of 2.0.. started clean.. installed fine..

 

launched it for first time (default f-22 flight).. stepped away for maybe 10 minutes (had throttle full on too).. come back to a message "your computer has run out of available memory" (which is crazy as i have 16GB and only about 5GB was in use, total after load).. 

 

Reloaded.. modified some display settings in the program and have left it "run" now.. so far cant recreate that error.. was very odd.. and perfectly clean.

Michael2, I found the save controller profiles issue minor as well, but I was able to save them by clicking on "Export File" and in the "Save As" box, type the filename there.  This will populate the filename in the Export Controls area, then click "OK" to save it.  Thank you for reporting that the controls will save once you exit P3D.  This was nagging me because the controls had to  be reconfigured every time.

 

I am getting micro-stutters on my end, which I was not seeing in 2.0.  Nothing on "max" here.  I tried with and without SweetFX - which works, btw.

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.

 

I really don't think there's any problem and here's why. I had V2.0 installed and I simply applied the patch, I don't see where the button is cut off:

 

 

My thoughts on this are, I don't remember seeing a "Create Sceneario" button on this screen prior (admittedly I usually just Ctrl+C to close the sim so I could have very well missed it). The added button would make the menu longer and if you didn't delete %APPDATA%\Lockheed Martin\Prepar3D v2 as instructed you would still have an old copy of UISettings.xml sitting there which contains the following entry:

 

Before (from a backed up UISettings.xml):

    <d2p1:KeyValueOfstringP3DWindowPropertiesJ0N217ZL>
      <d2p1:Key>Views.Exit.EndFlight</d2p1:Key>
      <d2p1:Value>
        <FullScreenState>
          <Height>419</Height>
          <Left>734</Left>
          <MinimumHeight>400</MinimumHeight>
          <MinimumWidth>400</MinimumWidth>
          <Top>331</Top>
          <Width>452</Width>
          <WindowState>Normal</WindowState>
        </FullScreenState>
        <IsLoadEnabled>false</IsLoadEnabled>
        <IsResizable>false</IsResizable>
        <IsSaveEnabled>false</IsSaveEnabled>
        <WindowedState i:nil="true" />
      </d2p1:Value>
    </d2p1:KeyValueOfstringP3DWindowPropertiesJ0N217ZL>

After (after letting v2.1 build a new file):

    <d2p1:KeyValueOfstringP3DWindowPropertiesJ0N217ZL>
      <d2p1:Key>Views.Exit.EndFlight</d2p1:Key>
      <d2p1:Value>
        <FullScreenState>
          <Height>460</Height>
          <Left>735</Left>
          <MinimumHeight>400</MinimumHeight>
          <MinimumWidth>400</MinimumWidth>
          <Top>310</Top>
          <Width>450</Width>
          <WindowState>Normal</WindowState>
        </FullScreenState>
        <IsLoadEnabled>false</IsLoadEnabled>
        <IsResizable>false</IsResizable>
        <IsSaveEnabled>false</IsSaveEnabled>
        <WindowedState i:nil="true" />
      </d2p1:Value>
    </d2p1:KeyValueOfstringP3DWindowPropertiesJ0N217ZL>

Note <Height>419</Height> vs <Height>460</Height> between the old and the new. If you still had an original version of UISettings.xml you'd be setting that window height 41 pixels shorter than required for the screen to display properly, hence the cut off "Continue Flying" button.

 

To confirm, I restored the backed up UISettings.xml and here's what the "End Flight" screen looks like afterwards:

 

 

 

This is of course one of the many reasons LM recommends deleting these files, not sure why folks don't heed that advice?

 

Jim

 

Rob I am getting offer stutters also Have tried all type settings no help. Ra great before update. If anyone fines solution ,please advise 

Yes, appears to be fine........

 

Rob

Oh that's great news. I was getting a little confused by some of the earlier reports in this thread. But thanks for clearing that up.

 

I chose to keep a vanilla install from day one while waiting for the official installers for my add-ons, so it seems like flying over slightly ropey scenery for the last few months has had it's advantages, almost

 

Cheers once again for the confirmation.

Hey guys. I was wondering if anyone is experiencing crash to the desktop in v2.1 when you right click anywhere? I crash every time i right click anywhere on the screen and its driving me nuts. Any ideas as to what is causing this?

 

thanks

 

 

Hey guys. I was wondering if anyone is experiencing crash to the desktop in v2.1 when you right click anywhere?

 

Right click is working fine here, and no idea what might cause this, sorry.