:smile:

I have been there Greg. What I then do is make one folder with all set-up files (including add-ons) and specific config files (like gsx profiles, simconnects etc). I just then fire all set-ups in order. It looks like below for me -

 

01 P3D Setup

02 FSUIPC

03 ORBX

04 REX

.

.

.

.

so on.

 

Ohh yes, it do add some peace to mind that I am truely on the latest version.

 

Regards

Prayog

As it is, the Client update requires (if my understanding is correct) a reinstall of FTX Global and Vector, REX, updates to AS2016 and FSUIPC, Q400 etc.... So I'm thinking, just do it 'properly' first time.

 

No,  A Client Only Update will Not effect Planes or Scenery,   You will have to Update Utilities only like ASN\AS2016  GTN 750\650 fsuipc and so on. 

 

Only 2 Action's you take after a Client Update is,  Delete your Prepar3D.cfg and your Shaders folder and let them rebuild again fresh.  This will return your settings back to Default, So you will have to readjust your In-Game Graphic\Scenery settings again after you do this,  Start Prepar3D and go into settings to adjust sliders and so on 

 

======================

 

You will only have to Reinstall Orbx Global (Run the Installer again) if you Update Scenery.

 

Updating Prepar3D using the Update Installers works flawlessly,   but Personally speaking I always like to do a Complete Uninstall and then Reinstall again  

My experience :

 

- the scenery looks better. I cannot descrive the differences with v3.3 but it looks a little more 'real' to me

- I have some jitters when there a lot of clouds that I did not have before, but the eopn beta for AS16 might have to dop with thta. Clouds look better than before , so perhaps also more impact on performance

- PTA makes my photoscenery look great like it did in v3.3

 

Now I am going to play around with water.

Rob made his "Wave adjustment"package for v3.1 and I used it up to v3.3

I will try the default v3.4 water compared to Rob's adjustments.. 

No,  A Client Only Update will Not effect Planes or Scenery,   You will have to Update Utilities only like ASN\AS2016  GTN 750\650 fsuipc and so on. 

 

Only 2 Action's you take after a Client Update is,  Delete your Prepar3D.cfg and your Shaders folder and let them rebuild again fresh.  This will return your settings back to Default, So you will have to readjust your In-Game Graphic\Scenery settings again after you do this,  Start Prepar3D and go into settings to adjust sliders and so on 

 

======================

 

You will only have to Reinstall Orbx Global (Run the Installer again) if you Update Scenery.

 

Updating Prepar3D using the Update Installers works flawlessly,   but Personally speaking I always like to do a Complete Uninstall and then Reinstall again  

 

I updated Client and Content but did not delete the cfg or shaders.  I guess I need to do that next.

 

btw, for anyone with FSL Spotlights, you need to update or P3D will crash almost immediately after you start it.

After 3 hardcore business days at the Munich Oktoberfest i am currently testing my stresstest flight in the aerosoft Airbus from aerosoft EDDF to orbx EGFF. Orbx global and england etc. installed.

 

This time also with ASN16. The sim still feels extremly smooth as mentioned some days ago.

I can not experience a vas issue, normally when climbing out of eddf direction netherlands the 3.2 and 3.3 p3d didn't release much memory. Now i get 300mb back when far enough from eddf. Durrently over the channel remaining vas is still 914 mb. Will se what happens over london.

 

Usually into approach to egff i get OOM. Will report back.

 

Carsten

 

 

This time also with ASN16. The sim still feels extremly smooth as mentioned some days ago.
I can not experience a vas issue, normally when climbing out of eddf direction netherlands the 3.2 and 3.3 p3d didn't release much memory. Now i get 300mb back when far enough from eddf. Durrently over the channel remaining vas is still 914 mb. Will se what happens over london.

 

This is exciting stuff, I haven't been able to fully stress my p3d 3.4 as I was busy testing pre-release builds of Flyinside.  Will do a stress VAS flight with 777 over FTX PNW and FTX Cali

This is exciting stuff, I haven't been able to fully stress my p3d 3.4 as I was busy testing pre-release builds of Flyinside.  Will do a stress VAS flight with 777 over FTX PNW and FTX Cali

 

Curious what everyone uses these days to monitor VAS while in flight, particularly if using goggles (i'm guessing with goggles its not possible, as basic onscreen text things dont appear like fps).. is it still fsuipc and a command there (i forget which)?

Why should i delete the cfg?

Curious what everyone uses these days to monitor VAS while in flight, particularly if using goggles (i'm guessing with goggles its not possible, as basic onscreen text things dont appear like fps).. is it still fsuipc and a command there (i forget which)?

 

This is easy, I can still see my monitor from the nose hole I just have to tilt my head to see the monitor, or I can go to flyinside menu and see my desktop (the FSUIPC counter is right up there), and i hear the FSUIPC dinging.  That tells me VAS hit is near or the sim just goes kaput and then I know I ran out of VAS.  But luckily all my flights are saved with 5 min interval by FSUIPC - so I now never really worry about VAS anymore

Is it just me or is there a noticeable drop in performance with traffic add-ons like MyTraffic6 in 3.4 vs. 3.3?

I noted a drop in performance compared to the v3.3

Is it just me or is there a noticeable drop in performance with traffic add-ons like MyTraffic6 in 3.4 vs. 3.3?

 

Not here - no impact to performance with MyTraffic...

Why should i delete the cfg?

I did not delete the p3d.cfg either...

What is the reason to do so ,as there are no new menu features ,as far as I have seen...

Thanks to Poppet's great contribution...

 

...I went from v3.2.3 to v3.4.9 with no problems.

 

Deleted the Client.  Applied the Client

 

Deleted the Content. Applied the Content.

 

Did not interact with the Scenery at all.

 

v3.4.9 ran the first time, no problem with all my Orbx and other custom scenery intact.

 

Did not delete my .cfg file.

 

Checked on first  run under the HELP, and saw P3D reporting as v3.4.9

 

Oh...I did one pass of the Orbx Central for P3D v3.x after applying the Content msi.

 

Regarding my on-board graphic memory load in.  Of my 8 GB's available,  v3.4.9 loads in 2804 GB's of texture and maintains that on average for the duration of my usage session. 

 

Cheers,

I noted a drop in performance compared to the v3.3

I saw about 3 FPS increase from v3.2.3.

Thanks to Poppet's great contribution...

 

...I went from v3.2.3 to v3.4.9 with no problems.

 

Deleted the Client.  Applied the Client

 

Deleted the Content. Applied the Content.

 

Did not interact with the Scenery at all.

 

v3.4.9 ran the first time, no problem with all my Orbx and other custom scenery intact.

 

Did not delete my .cfg file.

 

Checked on first  run under the HELP, and saw P3D reporting as v3.4.9

 

Oh...I did one pass of the Orbx Central for P3D v3.x after applying the Content msi.

 

Regarding my on-board graphic memory load in.  Of my 8 GB's available,  v3.4.9 loads in 2804 GB's of texture and maintains that on average for the duration of my usage session. 

 

Cheers,

I saw about 3 FPS increase from v3.2.3.

 

 

You "deleted" client and content...?????