At any rate....
I've been using both FSX & P3d.
At the moment I give FSX the higher score. Mostly that's due to the crashes & incompatibilities with P3d.
But it's also due to FSX being the more mature of the two.
Once they get the first update out, I think that it'll pass by FSX with ease.
All in all, though, it's a lot of fun. Most of the time I use FSX for a while, and then I'll "play" with P3d.
.
The latest problem has to do with my two 9" DoubleSight USB monitors.
If either of them is set up and running when I start Prepar3d, P3d will crash.
If I were to ask the LM P3d team, they would say that it's because the resolution is 1024 X 600, and Prepar3d V2 requires 1024 X 700 to run.
OK, I can agree with that. Or I might if I were trying to run P3d on those 9" screens.
But these are only used for flight instruments.
The next part of that problem is that I also have another monitor using a USB connection running at 800 X 600. That's the DesktopAviator GPS.
(Side note - If you find this GPS interesting be careful: they also sell the same thing BUT WITHOUT THE MONITOR.
Yes, you do end up getting the knobs & buttons. But just spend a little extra money and get the one with the monitor in it. It's only $230.)
It's not a major problem, just a nuisance. The DoubleSight monitors have an on/off switche behind the top edge. I just have to turn the monitors off before starting P3d.
BTW - Prepar3d V2 doesn't have any problem with the DesktopAviator GPS. On, Off. No problem, it runs.
Once Prepar3d V2 starts, I can turn on the two 9" monitors and run the instruments in the two of them. Everything works fine from there on.
As I said some where or another, I think that the error handling needs a bit more work. There are too many things that'll cause an IMMEDIATE crash.
.
The left hand monitor is turned off in this shot, but this is the way that Windows 7 sees the monitor setup.
Monitor number 5 is the GPS. That's an interesting name that the OS gave to the monitor.
.
.
Programing that GPS is the other incompatibility I ran into today.
Now I know that this is a hardware issue that'll probably affect VERY few people, and will therefor get little, if any, attention. That's fine. I have an easy solution.
The problem pops up when trying to program each button and the concentric knobs into Prepar3d V2.
Where FSX registers EACH button, P3d only captures 9 or 10 out of the 16 buttons.
So I went back into FSX and checked. All button presses registered. So it's not the GPS buttons.
Probably the firmware is sending a signal that FSX does recognize, but that P3d does not.
.
If you have the full (paid) version of FSUIPC you can use that to program the buttons & send the command to P3d.
.
One thing interesting in that picture above - Anyone want to build a "Central Fire Control system"? One person could be flying, and another person could act as a gunner.
upside down, or right side up 
