Warmbrak

I always enjoyed Heinz contributions to the X-Plane community. Rest in peace Heinz.

There are a lot of add-ons and different setups that may cause a patch to fail; hence why LM recommends a fresh install to ensure it will work as intended. I am sorry if the patch did not work for everyone, but there is an alternative. The time wasted posting here and debating the issue to death could have been spent on a re-install. I had to do this for V2.2, but the end result was awesome. This time round the patch worked for me, so I can't complain. My advice is to suck it up and re-install. Just do it and move on.

If you are a FTX customer, why not visit the FTX forums where there is a dedicated Prepared V2.2 OrbX scenery compatibility list? This way you can know which OrbX products have been converted to be compatible with P3D V2 before you buy them. The list is a bit limited outside of Australia at the moment, but it is slowly catching up.

All I can say is that there is a lot of content on this forum where people have gone through the same process as you. People put a lot of effort into compiling compatibility lists, performance tweaks, hardware discussions etc. There is just way too much information to summarise in one post. My advise is that you ready the stickies on this forum, and look through the posts of relevant topics. If you have any specific queries there are many people around that will gladly help you out, but I suspect you may have to take a few hours and read through these first. There are answers to all your questions in this forum, but you are going to have to read through them yourself.

There should be no difference between a hot-fixed/patched Prepar3d 2.2 and a fresh install. Unless you have installed many add-ons and want to start with a "clean" simulator, I can't see the point.

Next week it will be even closer...

No, FTX Global itself is not causing the OOM's; many are running it without any problems, including myself.

P3D v2 as my primary GA sim.

I installed the TBM850 without issue in P3Dv2, and it appears to work ok. The performance is not that great however, and I am experiencing a 30fps drop compared to other aircraft which I assume can be contributed to the G1000 not being optimised for use in Prepar3d (yet).

Awesome! Working now, thank you so much.

My first attempt to get it working has not been successful. I have it installed in FSX, and simply pointed the installer to my Prepar3d V2 folder. It installed fine, but did not show up in the menu. The files are located in the Prepar3d V2 folder under A2A where it should, but no joy. I have since uninstalled my FSX version, and will try to install again. I will report back if I get it working.

There is a difference between posting observations and basing opinions on how unsupported addons perform in P3Dv2. Popular threads are regularly opinion based and pointless, much like this one.

It depends. For instance, with the Aersoft Twin Otter there is very little impact on FPS. With the Carenado TBM 850 there is a severe penalty (FPS between 25-30, down from 60), but could be due to the aircraft not being optimised for Prepar3d V2. I noticed AI aircraft having very little impact on performance. Same with shadows. I have buildings and terrain receiving and casting shadows with almost no noticeable impact on frames, whereas it is very noticeable for others. I am running a GTX 780 to be fair. So it appears that with optimisation traditional performance hogs can perform better than in FSX; it is really hard to tell at the moment, and to say the sim's performance will drop further with additional AI, weather and PMDG is likely, but not quantifiable.

Training can be entertaining B) . These guys have a lot to be proud of; would be great if they featured a Lockheed L-1011 in future.

I am willing to give up on FSX-only addons and stay with P3DV2; it is that good. I will keep FSX installed in order to install and migrate addons, but that is it. I respect that some folks want to stay with FSX, but P3DV2 is the future.