This is good to know. But I am keeping my 130 or so add on sceneries which seem to work. I mean that with the best intention and respect to Robert. These legacy sceneires may make my sim  wobbly but for now I am keeping it... knowing the risk unless the sim become too wobbly and fails constantly..then I may have start weeding off the really offensive sceneries.

The alternative is, I have no more than 20 or so addon sceneries.  I was actually amazed that almost all the P3Dv3 sceneries work in v4. Maybe not in the most efficient or clean way I am sure.

I'd rather slowly replace each of the legacy scenery as the add on vendors publish a true v4 alternative for a reasonable price (which they totally deserve for the additional work. 

Just my 2 cents! :)

 

"Seems to work" about sums it up. Seems to work (until it doesn't) is a saying in my business. It's a saying of customers too cheap to do needed repairs and or maintenance because it "seems to work"

A lot of times seems to work will add niggling little problems and annoyances. Many manufacturers won't even deal with you if their stuff isn't installed by their prescribed methods and they don't care if it "used to work like that" or any other deflection type statements that people bandy about. Bottom line is the chaos theory kicks in and there are just too many variables in not doing something the right way and it only compounds the problem tenfold when you start mixing in several more products that aren't following the OEM's guidelines either. 

 

Edit : I suggest actually trying a PMDG with default scenery before just shuffling down the list and loading your sim down with every addon, runs surprisingly good. I'm about ready to wipe V4 again and just write off my previous scenery purchases for this reason. Everyone STILL dumpers their addons into the main sim folder even though they were warned not to 2 years ago...now thats just lazy.sorry.

Aerosoft starter to recompile their products to v4 but when you install their airport they go directly into v4 folder... so aerosoft don t follow sdk 

It does not depend on us , but on the developers... If I had to strictly comply with those rules, at the moment I would have a clean installation of P3D v4, the 747 and a couple of sceneries at most, nothing else and I would have to wait months and months (I would say years...) before all the addons I have for v3 get native for v4... 

1 hour ago, grandfred29 said:

Aerosoft starter to recompile their products to v4 but when you install their airport they go directly into v4 folder... so aerosoft don t follow sdk 

Hi!

I don't know if this can cause any impact on performance or compatibility, but even Flytampa - for example - doesn't use the SDK. You need to install your P3D V3 sceneries with the old installer then delete some files and paste some others. I think this is not a real problem, probably is how the scenery was created.

Regards, Max

This information is super and for a lot of us important. We get a lot nice and juicy stuff from pmdg and besides all of it more support than we can ask for....

Thank you for uplifting our experience. 

1 hour ago, grandfred29 said:

Aerosoft starter to recompile their products to v4 but when you install their airport they go directly into v4 folder... so aerosoft don t follow sdk 

Just move them out of the sim folder and create your own XML file in the "Prepar3D V4-Add Ons" folder in Documents. It's fairly easy. I've just done that with the majority of the sceneries (FlyTampa and Aerosoft so far) and with Ultimate Traffic II...

Interesting post, Robert. Thanks for the advice/warnings. I've have just installed the FlyTampa sceneries, and as far as I'm aware, they aren't "Prepar3D V4 Compatible"... the installer doesn't even recognize Prepar3D V4. 

I don't know what to think here... I haven't gotten any issues with the sim and it's running better than I've ever dreamed of... Pure fantastic and stutter-free experience! I really love Prepar3D V4... 

Well... I fully agree with Mr.Randazzo.

He wrote nothing new or special, for me it's normal, and I don't understand people who want to use old add-ons, even if LM deprecates this thing! I know many of us have spent lots of money in sceneries, planes and so on, but if you decide to jump into the new world of P3D is mandatory to use only v4 "certified" add-ons. In my humble opinion during this period all of us can see who serious and professional developers are and who aren't...  

Regards, Max

 

9 hours ago, Harvgordon said:

Hi Alex,

Update to latest driver: 386.53, no fps loss even with dynamic lights enabled.

Works for me, and the performance is boosted as well.

Latest driver I can find is 382.33.  Am I missing something?

The lastest (non-beta) driver is 382.53.

Thanks for the advice.

I had only two crashes in a heap of flying time now. One was likely down to a GPU driver issue. Fixed. The other probably had it's roots in the 747 FSUIPC issue that got fixed the day I ran into a crash.

Legacy scenery doesn't give me pain so far and I'll keep it in for now. However, once v4 has fully arrived I might just throw it out and re-install the entire system from scratch. Right now, I'm just not ready for such a D-Check ;)

Btw: Do people really try to run XPL scenery in P3D? I mean, really? ...

cu
Roman

10 minutes ago, romangeber said:

Btw: Do people really try to run XPL scenery in P3D? I mean, really? ...

cu
Roman

It's Robert's sense of humour. You'll get used to it. :)
 

It probably doesn't help that most of the default aircraft are compiled with the FSX SDK. Only 3 or 4 are actually P3d native. 

Although it is frustrating awaiting our P3Dv4-compatible versions of software, and that it is very tempting to 'jump the gun' to get things working again, RSR's post has very correctly reminded me to be patient for the new versions of the software.

Many thanks for your timely reminder, RSR

11 hours ago, Nuno Pinto said:

This must be the most useful post i've seen on AVSIM. Ever.

I guess that's why Robert must be the only person here with more likes (higher reputation) than posts!