'

 

Ouch, would have to reinstall ORBX, whooof, that there is a whole week.

 

No...simply Global, which takes five minutes. All this talk of having to re-install scenery is unfounded following an uninstall/reinstall of all three. All my FTX enhanced regions and airports are fine, Flytampa, etc. 

Just like so many others, I'm just waiting for the Orbx objectflow.dll and the ASN update.  Once they're available I'm ready to go.  I have no fear of the v3 update.

It is REALLY important to follow the uninstall instructions ESPECIALLY:

 

 

%PROGRAMDATA%\Lockheed Martin\Prepar3D v3

%LOCALAPPDATA%\Lockheed Martin\Prepar3D v3

%APPDATA%\Lockheed Martin\Prepar3D v3

%USERPROFILE%\Documents\Prepar3D v3 Files

 

 

Several issues posted here and elsewhere can easily be solved by following the above. If you have some really customized settings, save the specific file and reenter the settings AFTER the install. I suggest that you do NOT just copy the old back over the new or you might lose some of the updated changes.

 

Personally, I just copy the entire folder set to a temp folder and do the install. Then I add back my custom settings. I keep the backup for a while JIC something unforeseen comes out of the woodwork.

 

I recommend using a program like WINMERGE (free)- http://winmerge.org/?lang=en - to compare files - makes it easy to spot and change differences.

 

Vic

 

Just to be clear...this procedure is required only when doing an uninstallation and a full reinstallation of P3D. 

Has anyone got Ezdox working in V3.2? Just wondering before I install

The way I understood it as long as you only update the client your scenery files won't be touched meaning your Orbx files won't be touched so no need to reinstall any Orbx products.

 

The only thing with Orbx when you update the client is the objectflow dll which needs to be updated by Orbx to be compatible with 3.2.

I installed client, scenery, and content. All of Orbx enhanced regions and airports are fine, minus objectflow atm of course. Global will need reinstalling since it replaces default textures in the P3D root. No worries on this end. Can't imagine it being any different elsewhere. 

No...simply Global, which takes five minutes. All this talk of having to re-install scenery is unfounded following an uninstall/reinstall of all three. All my FTX enhanced regions and airports are fine, Flytampa, etc.

 

 

No...simply Global, which takes five minutes. All this talk of having to re-install scenery is unfounded following an uninsall/reinstall of all three. All my FTX enhanced regions and airports are fine, Flytampa, etc

 

 

Great. Now as clear as water - clean water! Thank you!

Rob and others here, I don't think (speaking for myself and apparently some others on here, too) that it's so much a matter of being negative about the updates, it's more a matter of wanting to fly more and tinker less.  Of course, the obvious answer to that is "Well, just don't update, stay where you are."  The problem with that is, at least in my case, that I actually would like to keep up with the Jones', but to do that seems like a non-stop continuous battle sometimes.  I'm still trying to get things sorted with 3.1 and now I'm looking at maybe starting the whole mess over again to go to 3.2.

 

Jeff, your comment seems to be more about "add-ons" than about the base P3D product.  LM can't force 3rd party devs to do anything ... I think it's fortunate we now have the ability to install just the main Client update so we don't mess up any 3rd party products.  A very easy process

 

1.  Download the much smaller (file size) client installer from your account page

2.  Uninstall the V3.1 client from your PC

3.  Install the V3.2 client from your PC and if prompted re-activate license

 

Are you tinkering with LM's core P3D product or the add-ons?  If the answer is the "add-ons", then you need to contact the content provider and give them your feedback.  Tinkering is not a requirement to get base P3D working well ... I've always recommended less to no tinkering.  I tinker to help others, but in my daily flying my P3D.CFG has no special entries and any other 3rd party adjustments are done thru those 3rd party configuration tools.

 

Flight simulation is as simple or as complex as you want to make it ... buying 3rd party add-ons can increase the complexity ... but this is true for any  software one installs be it from Microsoft Windows Updates to nVidia graphics drivers updates to application/game/sim updates.  The more "open" the environment the more end user management will be required, but in the same token the more that environment can do for you with greater rewards.

 

Not sure what you mean by can't find any aircraft for P3D?  I've got well over a 100 aircraft working in P3D without EMT, of those 100, about 80 are designed for P3D V2, V3.

 

But if you want to talk about complex that really has NOTHING to do with LM/P3D ... I just went thru a diagnostic process with my older GoFlight modules (166A, T8, P-8) under Windows 10.  For some bizarre reason Windows 10 USB settings were preventing my GF 166A from displaying the com/nav/xpndr frequencies on the unit's LED display (in P3D the controls worked, but actual frequencies were not showing up in the 166A display).

 

Hit Google search and got lucky and found someone with the same issue and a potential solution (only for Win8.1) ... turns out that I had to manually locate each GoFlight device (in Device Manager) and uncheck "allow windows to turn off device" in the Power Management tab.  BUT, that was not "enough" to solve the issue.  I then had to proceed to monitor changes via device manager as I plug/unplug each GF device to figure out which device is which and get the VID for each device.  THEN, RegEdit (Run as Admin) and find the appropriate registry location and edit two more settings changing them from 1 to 0 ... repeat this for each GF device I have (I have 24 of them).  So once complete, reboot my PC and viola, my older GF devices are working correctly.

 

When I have to do stuff like this to be able to Flight Sim "using my GF gear", I ask the same questions as you ... this isn't LM's fault, not Xplanes fault (I use GF for XP10 also) ... it's either GoFlights fault or Microsoft's fault ... considering my GF devices worked well under Win7, then I'm gonna suggest it's Microsoft's fault ... after I did this process, I immediately updated my long standing FS document with my long long long list of bits of information I've gather over the last decade or two covering many different Flight sim platforms (yes even MS Flight, FS8, FS9, XPlane versions).

 

As I get older my tolerance does get less for stuff like this, and I do question my desire to stick with FS, but it was my choice to use GoFlight, my choice to upgrade to Windows 10, I made my FS world more complex.  Fortunately once resolved and a few flights under my belt, all is forgiven and forgotten ... until the next time ... the reward does take some work, but I suppose it's also that extra work that increases the level of satisfaction

 

Agree, not for everyone, but some of it is self induced.

 

Cheers, Rob.

I did a full (clean) install to 3.2. However I'm not noticing any shoreline wave animations. Is there a certain slider that I need to play with?

Just to be clear...this procedure is required only when doing an uninstallation and a full reinstallation of P3D.

Correct! Should have clarified that.   With the Client install only, it is not necessary, but if you run into issues, it is the first thing that LM will recommend.

 

I find it easier to delete them all, protecting those files that I have modified and resetting them as necessary.

 

If you just blindly delete those folders, you will have to reinstall your add-ons.

 

Should have clarified that - Thanx @Solrayz!

 

Vic

Jeff, your comment seems to be more about "add-ons" than about the base P3D product.  LM can't force 3rd party devs to do anything ... I think it's fortunate we now have the ability to install just the main Client update so we don't mess up any 3rd party products.  A very easy process...

Rob, you are spot on.

I upgraded to V3.2 and absolutely believe it is the best version yet! LM has done an excellent job.

 

LM could create the cure for cancer yet some people would be upset because it is in a liquid form instead of a pill.

Edited March 9, 201610 yr by n4gix
Remove rediculously excessive quote!

I just started a multiplayer session if any wants to join in. It seems mine is the only one that is public anyway :smile:

I did a full (clean) install to 3.2. However I'm not noticing any shoreline wave animations. Is there a certain slider that I need to play with?

The water slider and the special effects.

 

Best regards,

Any comments on performance yet? Beau kept mentioning that 3.2 would include performance updates.

 

I seem to see better performance now. Did the Client only install. Definitely seems to have cured my blurries I was having with 3.1 though only took the A2A Cherokee for a low & slow spin. Relatively smooth only a couple small stutters. I am impressed.

Not trying to sound sarcastic, but I just did the SUPER SIMPLE client upgrade from v3.1 to v3.2 with not troubles at all. I followed the upgrade instructions provided by Lockheed Martin, and I was installed and running in less than 10 minutes. All that I had to do after that was to re-activate and choose the "Don't Run" at the dialog prompt for Orbx's ObjectFlow dll.

 

The I did a test with V3.1 vs. v3.2 sitting at FlightBeam's KSFO with Orbx's Northern California Scenery, MyTraffic 6, PrecipitFX, FsFx 777 effects, and Prepar3D's default Building Storms weather then taking off in the PMDG 777. My first impression was WOW NorCal and KSFO seem to be working even though Virtualli and ObjectFlow hadn't been updated...cool to that. The performance impression was that v3.2 is a BIG step in the right direction in performance from v3.1.

 

The flight out of KSFO was very smooth and looked great as the big 777-300ER climbed with FsFx's 777 effects across the wings and contrails off the wing. I was getting but smooth low FPS when looking back at KSFO with traffic in v3.1. In v3.2 I was still experiencing good smoothness, but much better FPS. This is just with the client updated, so I'm VERY much pleased with the improvements made in the v3.2 update.

​Everyone is going to have a different setup and set of add-ons, but I wouldn't hesitate to upgrade to v3.2. At the very least everyone should do the client upgrade and see how it runs for their machine. It's another step forward for Prepar3D.

Is anyone using Ezdok with 3.2, and does it work?