Dumpcore

Migration Tool is an excellent solution for a lot of people, but if you don't want to pay for it, such tips are well worth. I have installed hundred of addons without using EMT, and without touching anything else. Also, dynamic links are very useful to solve some compatibility problems that EMT can't do.

If you don't need FSX more, don't have EMT, and want to install FSX addons into Prepar3D V2, take note of this two tools to make easier such migration process: 1) Symlinker https://code.google.com/p/symlinker/ With Symlinker you can create symbolic links to folders and files. It is extremely useful for creating a virtual FSX directory structure (and P3D V1), linked to the original Prepar3D V2 folders and files. Examples (symbolic -> original): A) Main FSX folder: E:\FSX -> E:\Prepar3D V2 B.) FSX and P3D V1 scenery folder: C:\ProgramData\Microsoft\FSX -> C:\ProgramData\Lockheed Martin\Prepar3D v2 C:\ProgramData\Lockheed Martin\Prepar3D -> C:\ProgramData\Lockheed Martin\Prepar3D v2 C) FSX and P3D V1 config folder: C:\Users\USER\AppData\Roaming\Lockheed Martin\Prepar3D -> C:\Users\USER\AppData\Roaming\Lockheed Martin\Prepar3D v2 C:\Users\USER\AppData\Roaming\Microsoft\FSX -> C:\Users\USER\AppData\Roaming\Lockheed Martin\Prepar3D v2 D) FSX config file (hard symbolic file): C:\Users\USER\AppData\Roaming\Lockheed Martin\Prepar3D v2\FSX.cfg -> C:\Users\USER\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.cfg E) FSX documents folder: D:\Usuarios\USER\Documents\Flight Simulator X Files -> D:\Usuarios\USER\Documents\Prepar3D v2 Files 2) FSX Registry Utility http://www.tweakfs.com/store/free_tools.php With this tool you can set in the Windows Registry the FSX path pointing the Prepar3D V2 path. So, addons will be able to find your Prepar3D main folder for installing them. With this two tools, you will be able to install almost 100% of FSX and P3D V1 addons into Prepar3D V2, without any problems. This includes changes in DLL.xml and EXE.xml files, scenery, autogen and terrain annotations , and documents files. Of course, compatibility of addons is another question.

With an affinity mask of 84, you only get 3 cores running with P3D. With a value of 85 you have the four cores running, with HT on, but without using such threads. I have a value of 85, with HT on, and Prepar3D has an additional core for terrain loading, with is very good to avoid blurries and for loading the scenery. I dont't know exactly if P3DV2 can make use of TH threads, but what I am sure is that HT isn't harmful for P3DV2, and that is better to use four cores than three. Briefly, you can have safely HT on, which is good for the general performance of your OS, and should try to use the four cores for the best performance of P3D. Of course, if you get worse perfomance, use an AF of 84.

Thanks for your feedback. The problem and the fix has been reported in the LM forum B)

Well, try now this hint: 1) Open your saved flight with a text editor 2) Search this line in bold: </Section> <Section Name="Window.1"> <Property Name="Order" Value="0" /> <Property Name="Active" Value="True" /> <Property Name="Undocked" Value="False" /> <Property Name="Maximized" Value="True" /> <Property Name="Locked" Value="False" /> <Property Name="ScreenUniCoords" Value="0, 0, 8191, 6143" /> <Property Name="UndocCoords" Value="0, 0, 0, 0" /> <Property Name="Title" Value="Virtual Cockpit - View 00" /> <Property Name="CurrentCamera" Value="{C95EAB58-9E4A-4E2A-A34C-D8D9D948F078}" /> </Section> 3) If it has the value "True", change it with a "False", then save the file. 4) Open your saved flight and check it it works. It worked for me.

Well, thanks for the hint!! Now, I am trying to figure out where is the problem in the saved flight....

Yes, it works. This bug seems to be present if you save a default flight different from the stock one. If it is your case, do the following: 1) Delete (or comment out) the line starting with "SITUATION", in your Prepar3D.cfg The correct line should be: SITUATION=FLIGHTS\OTHER\Prepar3D 2) Activate the preview scenario window in your Prepar3D.cfg SHOW_SCENARIO_WINDOW=1 3) Launch Prepar3D and select the scenario, vehicle, time and date, etc. Try if now it works, and remember, don't save any default flight. With luck, we could report this bug to LM.

The only addon I have installed is FTX Global 1.1. Anyone without this addon?

Interesting. I still have this poblem with the Mooney Acclaim

ATI and NVIDIA cards affected. Clearly seems to be a bug.

The question isn't if it will or not be fixed, the important question is when.... P3D V2 has a new system of partial patching. Hope LM provide a bugfix patch very shortly...

1) No. You'll get a smoother movement, but with the same FPS. 2) Technically yes, legally no. 3) Almost all Flight1 addons can't be used in P3D, by legal reasons. 4) Yes 5) Yes. You'll need to update to newer versions of the installers, with the compatible modules for P3D. 6) P3D doesn't support DX10. Version 2.0 will support Dx11, but not 64 bit. If you really want to improve your FSX experience, try the Steve Parson patch for DX10. It works very well with NVIDIA cards, fixing almost all DX10 bugs. You'll get much more FPS, without stutters. Some addons won't work, but it is a worth try. Later, P3D V2 probably will be the best option.

I use EFB and don't have such problem loading the flightplans into P3D and the GPS. I have tested it both local and remote configurations.

I have the same problem. Tested with various parking positions, and always ended in the water :lol: (I like airports near the sea....)

Thanks very much for your effort. Now it works perfectly. In relation to the parameters included in the flight, it could be interesting to get a template from the user, and then change only some parameters (position, aircraft, time, date, weather, etc.). So, each user could personalize their own template (p.e. the default flight), with the specific parameters they want (engines running or not, battery, alternator, lights, etc.). It is only a suggestion. Again, thanks very much.