I have both installed. On different drives/partitions: J:\Flight Simulator X (single partition on a 500GB drive) and I:\Prepar3D (on the 3/3 partition of my 1TB HDD).
After viewing that video, I wonder if he used the same CFG? In other words, is it just a renamed fsx.cfg (to Prepar3D.cfg). Or is it a modified Prepar3D.cfg to have all the same changes in all the same places so that it is "the exact same settings" as in the fsx.cfg?
One other thing to take note of in Prepar3D, is that you do not have a [Trusted] section in the Prepar3D.cfg, so there is none of that crazy nonsense of accepting a gauge as being "trusted" (a pet hate of mine with FSX).


Quote:

Be aware that some payware devs don't support P3D, so support threads with that sim may not last that long or just won't receive an answer. Some seem to get very upset on licensing issues.

The more complex the aircraft, the harder it can be to get into P3D, so without the support of the developer, you have to rely on those who have already made the transition with the product.

My big problem with moving the Captain Sim aircraft over (when I first got P3D), was to forget to add the info into the DLL.xml file! The ones like these:

 <Launch.Addon>
           <Name>Captain Sim 767 Menu</Name>
           <Disabled>False</Disabled>
           <Path>Captain_Sim\Captain_Sim.b767.menu.dll</Path>
     </Launch.Addon>
 <Launch.Addon>
           <Name>Captain Sim 767 Sound</Name>
           <Disabled>False</Disabled>
           <Path>Captain_Sim\767\cs.sound.dll</Path>
     </Launch.Addon>

But once that was done, they worked. ACE does NOT work with P3D. Well I haven't been able to get them to be able to. But then I haven't tried very hard either.