Sign in to follow this  
G-YMML1

The risks of downgrading P3D version from 3.4HF2 to 3.3.5

Recommended Posts

Hi,

 

Just wondering if someone took this path already and what was your experience. I'm planning to roll back from 3.4HF2 to 3.3.5 and replace the Client/Content/SDK only. Are there any risks associated with such downgrade OR should I implement some counter-measures first?

Thanks

Dmitriy

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Main risk is if you have add on version without backwards compatibility you would have to reinstall older version. Someone stated in hf2 topic he reverted client only I'll try same

Share this post


Link to post

Add-ones should be fine. PTA and AS2016 are two only suspects, but they both have backward compatibility with the previous versions of P3D

Share this post


Link to post

What's wrong with 3.4?

 

Mark

 

SLI is hard broke, and VAS issues

 

Regards

Share this post


Link to post

What's wrong with 3.4?

 

Mark

 

Excessive VAS usage + unrealistic clouds' rotation (HF2) that in turn affects clouds' shadows.

Also, HF2 made some mess with winter textures for GEP3D users. The fix Nick posted did not help

So...anyone with true experience?

Share this post


Link to post

SLI is hard broke, and VAS issues

 

Regards

I just went from 3.3.5 to 3.4 + HotFix and all seems to be well. Just had to update FSUIPC to get things to work. However, I'm not running SLI and have been flying XtremeLabs Lear almost exclusively which is probably a much lighter hit than tubeliners.

 

Cheers,

Share this post


Link to post

I'm going to give it a shot tonight, I suppose I can always go back to 3.4 if needed.

Share this post


Link to post

Well,

I was able to find and install 3.3.5 client, but I find neither Content nor SDK for 3.3.5 available. The latter is needed badly as Traffic Tools module from 3.4 does not work in 3.3.5 Client environment. 

Would really appreciate your help here.

Share this post


Link to post

The one thing no one mentioned:  Lockheed-Martin does not provide support for prior versions.  If you have something that isn't working in a prior version... you're on your own.

Share this post


Link to post

So, there is no way to get the old SDK for 3.3.5, right?

Actually, I don't need the entire SDK - merely a single file, TrafficToolBox.dll version 3.3.5. Right now I have 3.4.8.
 

Share this post


Link to post

Just recently I rolled back to 3.35 (from 3.4 HF2). I did not observe any issues except  textureloading/bluriness which accompanies me through all my installations since v2.5.

Share this post


Link to post

 I'm planning to roll back from 3.4HF2 to 3.3.5 and replace the Client/Content/SDK only. Are there any risks associated with such downgrade OR should I implement some counter-measures first?

 

It works. The only thing you loose is support from LM if needed.

  • Upvote 1

Share this post


Link to post

I went back to 3.2, by reinstalling Client and Content. VAS management is much much better.

 

The only problem is having to install a back-level version of the Majestic Dash, which doesn't have backwards compatibility.

  • Upvote 1

Share this post


Link to post

I went back to 3.2, by reinstalling Client and Content. VAS management is much much better.

 

The only problem is having to install a back-level version of the Majestic Dash, which doesn't have backwards compatibility.

 

Where did you get the Content? LM has only the Client installers

Share this post


Link to post

 

 


Where did you get the Content? LM has only the Client installers

 

I always archive everything I've ever downloaded.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this