As for SGSS I'm sorry if I spoil your joy but if you use SGSSx4 in dense clouds I don't think you'll be as happy anymore with the performance...

 

Thanks for the confirmation to my  own question. I just made a complete backup making it easy to roll back to 3.1 should I want/need to so will give it a go.

 

Still though I would love to hear about those parts that will not get updated doing it like this and what those other things really are and how you'll notice it in the sim.

 

No impact to the fps here.. and I run @1600p!

I only recently upgraded from a gtx780 and I notice few (if not any) improvement with a 980ti (see my disappointment in the other threads)... until I discovered the SGSSx4, now the damn little devil is finally giving out some power and I'm a happy little child.

Read this thread will answer your question

 

http://www.avsim.com/topic/484828-p3d-v32-sode-or-gsx-update-information/#entry3385352

Acutally that's a little shock for me.

 

Who guarantees it's only the Autogen folder being overwritten when installing the Contents package? Perhaps there are some texures / effects... as well which no one just happend to detect being overwritten as well?

 

Kind regrads, Michael

Acutally that's a little shock for me.

 

Who guarantees it's only the Autogen folder being overwritten when installing the Contents package? Perhaps there are some texures / effects... as well which no one just happend to detect being overwritten as well?

 

Kind regrads, Michael

 

True but as far as I can tell no problems other than controller binding not remembered only for some not all

Hi Gerard,

 

it will install in c:\Users\Your Name\AppData\Roaming\Lockheed Martin\Prepar3D v3\dll.xml

 

But I have manually moved all entries to c:\ProgramData\Lockheed Martin\Prepar3D v3\dll.xml (same also for exe.xml)

Not to advice since you end up with double entries at two places because some

programs check and add the entries during startup at the old location for example ASN ;-)

Stop using SGSS AA and retest ... even my two Titan X's can't deal with SGSS AA in dense clouds, nothing can ... setting yourself up for failure.  As posted by myself and others, no need for SGSS AA in V3.2.

 

Cheers, Rob.

 

Indeed that's why I prefer no SGSS with 5 layers of clouds and volumetric fog :-) Because I find the cloud environment far more important for obvious reasons...

OK but why do you suggest I do anything else than uninstalling/reinstalling the actual client since that is the only one LM recommends in their guide? What else will I get doing it the way you suggest?

Richard - you are doing it the RECOMMENDED way. The ONLY update that is NEEDED is the CLIENT. All the others are OPTIONAL - not required. As to what you might miss but not installing the optional items - check the changelog under CONTENT and SCENERY.

 

If there is anything there that you feel you MUST have, then you might want to run that installer also (after uninstalling that specific item).

 

It is a very neat and painless upgrade process and we seem to be having page after page of confusion. It is the same as when we upgraded to 3.1.

 

Just as there are some who are not aware that you can download JUST THE module you want to install rather than the 10G full install, there are some who didn't read the release notes where LM states that only the CLIENT is necessary.

 

For me - there is nothing I see in either the content or scenery that affects me, so it's only the Client I am concerned with.

 

SO, if you just update the client - you need not update *ALL* your add-ons, just those like ASN, ORBX, GTN750, etc that hook directly into the client dll. Your scenery, aircraft etc are all just fine. If you update the scenery - then YES you will have to reinstall you scenery.

 

Vic

Hi, Vic, you're sure you'll never need the GSX menu?

 

Kind regards, Michael

Just installed the client and content and so far no problems other than i wait for ORBX and ASN.

 

Now it's time for some Flytampa EKCH - ESSA tests

 

Michael Moe

I uninstalled and reinstalled client, scenery, and content. Orbx global was the only reinstall, as it replaces textures in your p3d/scenery folders, and maybe elswhere within the root p3d folder. All other 3rd party sceneries ok, aircraft addons ok. I also had to reinstall my environment theme textures in REX and my HD moon textures. That is all. 

 '

 

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

FS 2 Crew just posted this on Facebook.  Quote Below copy and pasted.  

 

Note regarding RAAS from www.fs2crew.com and the newly released P3D v3.2 update.

I had a couple reports users had crashes on loading P3D v3.2 and the crash report cited RAAS.

I just tested RAAS in P3D 3.2.

No problems.

What I did was:

1. Uninstalled 3.1 cleanly, including deleting any leftover folders from P3D.

2. Fresh download and clean install of 3.2.

3. Installed RAAS normally.

 

Everything worked perfectly.

So I guess if you had a problem, something got mucked up when you installed 3.2 over 3.1.

Clean installs are best in our view.

Richard - you are doing it the RECOMMENDED way. The ONLY update that is NEEDED is the CLIENT. All the others are OPTIONAL - not required. As to what you might miss but not installing the optional items - check the changelog under CONTENT and SCENERY.

 

If there is anything there that you feel you MUST have, then you might want to run that installer also (after uninstalling that specific item).

 

It is a very neat and painless upgrade process and we seem to be having page after page of confusion. It is the same as when we upgraded to 3.1.

 

Just as there are some who are not aware that you can download JUST THE module you want to install rather than the 10G full install, there are some who didn't read the release notes where LM states that only the CLIENT is necessary.

 

For me - there is nothing I see in either the content or scenery that affects me, so it's only the Client I am concerned with.

 

SO, if you just update the client - you need not update *ALL* your add-ons, just those like ASN, ORBX, GTN750, etc that hook directly into the client dll. Your scenery, aircraft etc are all just fine. If you update the scenery - then YES you will have to reinstall you scenery.

 

Vic

Thanks for the confirmation Vic!

 

For now I'll stay with just having updated the client since I honestly don't even know what some of those other things in the scenery and content packs actually do.

Hi, Vic, you're sure you'll never need the GSX menu?

 

Kind regards, Michael

LOL! For me, yes I am sure but, as I said, if you NEED something that is in another module, you'll have to update. I'd venture a guess that there are more who do NOT use GSX than those who do but the logic still applies. Apply the update process to your individual needs.

 

Vic

Stop using SGSS AA and retest ... even my two Titan X's can't deal with SGSS AA in dense clouds, nothing can ... setting yourself up for failure.  As posted by myself and others, no need for SGSS AA in V3.2.

 

Cheers, Rob.

Much agreed! I think 3.2 is a great release. The autogen building increased draw distance is very noticeable, there are some subtle improvements to rendering re reflections and shadows etc, Night Environment products work brilliantly, water objects ie ships/floatplanes dont exhibit strange movements... all good, and installed in seconds ..so why people are running scared with negativity is beyond me... k

including deleting any leftover folders from P3D.

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

vgbaron wrote:

"SO, if you just update the client - you need not update *ALL* your add-ons, just those like ASN, ORBX, GTN750, etc that hook directly into the client dll. Your scenery, aircraft etc are all just fine. If you update the scenery - then YES you will have to reinstall you scenery."

Maybe I'm misreading something and this will turn out to be a dumb question, but since ORBX is a scenery addon wouldn't that mean that I would also have to add all the ORBX scenery files?

 

Jeff

vgbaron wrote:

 

"SO, if you just update the client - you need not update *ALL* your add-ons, just those like ASN, ORBX, GTN750, etc that hook directly into the client dll. Your scenery, aircraft etc are all just fine. If you update the scenery - then YES you will have to reinstall you scenery."

 

Maybe I'm misreading something and this will turn out to be a dumb question, but since ORBX is a scenery addon wouldn't that mean that I would also have to add all the ORBX scenery files?

 

Jeff

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.