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.

Think I have found the problem. If I generate a flight without changing the weather theme, I get the following: ---- Title=SimLauncher Description=temporary flight to startup P3D AppVersion=10.0.60711 FlightVersion=1 [Fuel.0] Center=100 LeftMain=100 RightMain=100 LeftAux=100 RightAux=100 LeftTip=100 RightTip=100 Center 2=100 Center 3=100 External 1=100 External 2=100 [DateTimeSeason] Year=2012 Day=176 Hours=21 Minutes=41 Seconds=45 [sim.0] sim=L-39 Breit 2010 [simVars.0] Latitude=N36° 40' 20.34" Longitude=W4° 29' 23.42" Heading=133.2 PVelBodyAxis=0 BVelBodyAxis=0 HVelBodyAxis=0 XVelBodyAxis=0 YVelBodyAxis=0 ZVelBodyAxis=0 SimOnGround=1 OnPlatformHeight=-9999999999 [Weather] WeatherType=0 ThemeName=weather\themes\b [Options] Pause=true ----- The line in bold is causing the crash, because isn't pointing to a valid weather theme. Removing or changing correctly such line eliminates the problem. Of course, if I select a specific weather theme from the dialog, the line is generated correctly. Could it be a bug? It's very strange I am only the one who has this problem :blink:

Well, First of all, I want to thank you for providing the simmers community with this excellent tool. I have tried different versions since its initial release, and always has been imposible fo me to launch Prepar3D without a crash. I have this problem with the current 2.3 version. I always configure the same flight (plane, location, time, etc), and always get a crash when loading the scenery. P3D works perfectly in my system if I enter the same settings using the normal menus. Please, tell me what information you need to solve this problem. I always uninstall the previous version before installing the new one. I haven't made a second makerunways pass since the firts version I tried (1.2). Thanks in advance.

Well, you can try P3D in Windowed mode, with the same performance as fullscreen, with VSync working, and without the ATC problem. Try this to hide the title bar: http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=1793 And this to hide/unhide the Windows taskbar: http://www.aviassin.com/taskbareliminator Now, ATC window isn't a problem in P3D B)

Do you refer when pressing the backscape key on the keyboard to reset the zoom factor? Well, it works for me, and also in FSX. I have tried it using a FSUIPC command, and also works without problems, of course, with only one monitor.

It works correctly, also when pushing the backspace key. [CameraDefinition.002] Title = Virtual Cockpit Guid = {C95EAB58-9E4A-4E2A-A34C-D8D9D948F078} Description = This is the description of the virtual cockpit view. Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 1.2 SmoothZoomTime = 0.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=30 HeadingPanRate=75 PanAcceleratorTime=0 HotKeySelect=1

The weather graphics are identical to FSX. The weather engine is based on themes or custom weather (no real weather at the moment). The weather interface (Simconnect) is almost the same as FSX. The weather will be so good as you want with a theme or by an external engine (AS, REX, OpusFSX, etc.) The only difference is that P3D limits the maximum visibility range to 50nm (80 kms), and always seems that has lesser visibilibity than FSX. Some external engines (like AS) doesn't work very well with this issue, creating a rare atmosphere, like a foggy day. This addons need a special configuration in their options until a P3D version will be launched.

More money? Simply ask for P3D support in the future, and then they will decide what to do. :Loser: . If they take things seriously, should give you an answer.

First of all: no TrackIR native support. Until it is fixed, I won't be a client for LM.

Many people think DX11 will be a problem in the future with current addons. Well, you can always use DX9 in P3D V2, and maintain the previous compatibility. Although DX9 is worse than DX11, will take all the benefits of the new rendering engine, with better framerates and other improved graphics effects.I am sure DX9 will be an excellent option in P3D V2. In the future, probably most addons will be DX11 compatible, meanwhile DX9 will be the safe option.Don't care now about DX11. Currently, the most important issue is to get support from the developers in DX9 mode, at very reasonable prices for previous consumers, and to develop a very stable and efficient platform without important bugs and stability issues.DX11 should be now a secundary problem. Do you think DX11 will work without problems in its initial release? It will need several patches until it works correctly.Enjoy your Orbx sceneries and don't think DX11 is a problem for your addons. It will be an alternative for very demanding people, with very capable hardware.

1024 + DXT5 + 4x simple antialiasing. Very good quality and excellent FPS over all weather conditions at complex airports. I am running FSX in a 2600K at 4.8 GHZ + ATI HD6970.Sincerely, I don't understand why people struggle their hardware with 4096/32 bit resolution textures and supersampling antialiasing. And they still want FSX to run at 30 FPS with their PMDG in overcast conditions!!!Some people think they have a supercomputer from NASA. Current hardware can't do more with FSX, even the more powerful systems.