In an effort to try to get my add-ons working (AivlaSoft EFB, FSInn) I have renamed the p3d executable to FSX.exe. This works well as long as I do not change aircraft. However, as soon as a traitor changed any other aircraft than what I load with default, p3d crashes. Does anyone else experience this, and more importantly, does anyone have a solution?

Have you tried leaving P3d as is and just creating a txt file and renaming it fsx.exe? or just copy fsx.exe or make a copy of p3d.exe and rename it to fsx.exe?

 

Not sure it would work but can't hurt to try.

 

Vic

Thats what i normally do but for installers :)

Just copy the FSX exe unchanged and put it into the P3D Main Folder. It does nothing, except provide a target if you use something similar to the Flight 1 or the TweakFS registry utility. This way a majority of your add-ons can be transfered

 

I have put up a cookbook method a few times, but it basically is as above but here goes again:

 

Here is my approach for what it is worth. But it is being quickly overtaken by fresh advances. However it remains a good solid backup for any of the other migrators - but the Orbx migrator is excellent so do use that for their earlier scenery.

 

 

1. Copy the FSX white plane on blue background with the word application to its right in the column from the FSX root or main folder, into the P3D root file. (In FSX you find it way down below the folders - in the list of Application files}

 

Having the FSX application in P3D root folder does no harm, but it provides a target to fool installers that that is where FSX is.

 

2. Download and install a reg utility from Flight 1, or I use the one below:

 

TweakFS - Registry Utility for FSX

Version 1.3

TweakFS - Cool Tools for Flight Simulator

June 13, 2008

Website: http://tweakfs.com

Forum: http://tweakfs.com/forum

Email: [email protected]

 

3. Fix the FSX path to the P3D folder (Set Path), just follow the instructions its straightforward, and as you have put the FSX application file in there, it will accept the change of path. That's why we do step one!

 

4. If you are planning to Install the PMDG NGX .. install the two PMDG base files via the above method, run your PTPs through the livery manager as normal. There should be no problem (unless my instructions are too obscure).

 

5. The difficult bit is that you will probably have to copy the Load instruction for the HUD dll from the Appdata\\FSX dll.xml file to the similar folder and file in P3D.

 

If you are uneasy about editing an xml file, then just copy the entire DLL.xml (and I suggest the exe, xml file) from Appdata FSX to Appdata\\\P3D. Saves worry.

 

Without this you will have a HUD but with no content at all. Just a great big sunshade.

 

6. For other aircraft just follow the same steps except for the xml problems. I have all my Carenado installed directly without problem. (But Carenado now has installers released for P3D.

 

Also the Real Air Duke

 

7. The Orbx migrator tool is excellent and sorts things out well. You can install airports using my method, or the commercially available FSXtoP3D Migrator, but people flow is lost. Regional sceneries do install ok, including Misty Fjords. All new Orbx scenery is being released with a P3 installer option. I am sorry to say that for all of Orbx productions there is no installer until you get right into the most recent releases. So technically you need to have them in FSX so you can use the Orbx migrator and not to lose the FLOWS.

 

Pssst, the basic Australian and North American sceneries will install using this method - without problems, as they don't have People and other flows. However if you install individual airports by way of this method, you will get them fine, but without the animation.

 

8. The Aerosoft Airbus X is very much harder and the migration from FSX is discussed at length in the AVSIM forum. BUT the Aeosoft X Extended is being released in two weeks with a P3D installer. Much easier. Also Blackbox Sim has released the A319-320 with a P3D installer

 

9. For standard freeware scenery just copy the entire contents of the scenery add-on folder in FSX including the scenery and texture folders within to the scenery folder in the P3 equivalent. If you are more relaxed, leave them where they are and browse to them from the scenery library and Add. But and but, do copy and replace the two standalone scenery and texture folders within the Addon Scenery folder, so you don't lose those bgls that you installed directly into them - and have since totally forgotten. Payware use their installers to ensure any effects and sound files are transfered over. The registry cheat copes with this for most standard scenery. BUT more and more dedicated installers are being supplied.

 

10. REX Essential has been released with a full P3D installer and it works beautifully.

 

11. Carenado and Orbx now have dedicated installers, and I suspect more devs will also.

 

12. I suggest the FSPS Extreme P3D Booster, but I have read that it gets speed by removing scenery polygons, a bit like your digital camera when you go past optical zoom, to digital zoom. However for me, the key is in their first step: synchronise your fps to the screen refresh rate - works a treat.

 

But the first three steps are vital.

 

Caveat Emptor of course. Make sure you back-up anything you want to change.

Hi,

 

While I appreciate your detailed guide, I do not think this is relevant for the problem I am facing. I'm talking about getting set applications to work during runtime such as AivlaSoft EFB and the recent discovery of getting FSInn to load the aeroplane database. Both these applications requires that the running executable is called fsx.exe in order for them to connect to it correctly.

 

I am not sure why this is the case, and it is definitely not sufficient to have a file of that name in the folder. If anyone can tell me another way to get AivlaSoft EFB working I would be very grateful.

Why not at least try copying the fsx.exe into the root Prepar3d folder, and do the registry tweak, to see if it helps? If it doesn't you can just delete the fsx.exe and move the registry target back...

284

Why not at least try copying the fsx.exe into the root Prepar3d folder, and do the registry tweak, to see if it helps? If it doesn't you can just delete the fsx.exe and move the registry target back...

Because EFB does not work when I launch the P3D.exe executable, regardless of the other files are present in the directory. It does work if I rename the file to fsx.exe, but then it crashes as described above. Copying over the FSX file will not alleviate this problem. The procedure is described in a previous thread I started about getting AivlaSoft EFB to work. At that point in time P3D did not crash when I attempted to switch aeroplanes.

Chances are it's looking in the process list and uses the load address to check some offset in memory. P3D won't be the same. Unless the developer changes the hard coding, I am afraid you are out of luck on this one. Have you contacted AivlaSoft?

There are the occasional programmes that won't work in P3D. Apparently it is usually because of a module structure that is incompatible.

 

I have not persisted with Aivlasoft EFB as I am getting just as much utility from the FSWidgets version (and great support). AES I have found doesn't work either, but believe me they are about the only two (of mine, I mean). It is now up to the developers to make a decision about their estimate of customers that have moved to P3D. And I think the proportion will increase with v1.4, and I have a feeling that when v2.0 comes out there will be a big migration.

 

Frankly it is not bad, when compared with the backward compatability between previous versions of FSX.

kolaf,

 

If you are looking for something similar, but not as nice as the Aivlasoft EFB, FS Commander 9.2 supports P3D and is a nice flight planner and flight following utility that is comparable.

Have you used the resource hacker for your P3D exe file so that FSInn turns on etc.

 

I cannot get the aircraft repositry to load when running P3D but use FSX first and leave it open then rerun P3D and then I can "see" other planes on VATSIM and in Aivlasoft EFB.(does work on my computer with P3D)

 

Have used P3D once on Vatsim on a short flight but it tends to crash with menus.dll error - not found answer to that so have decided not to use P3d when flying multyplayer - its more unstable than FSX on my compt.

Will have to see what 1.4 brings in Sept.

 

Denis the Menace in UK

The menu.dll is a known issue with non full compatible add-ons. What P3D version are you using?

Has any one tried copying the FSX-exe to P3D as Ian suggests, then putt an underscore in front of the FSX.exe file in the FSX root directory? Like this "_FSX-exe". Now go ahead a load in the normal way.

 

Will have to see what 1.4 brings in Sept.

 

Released tomorrow, 20th August or early 21st August in Aus.

Has any one tried copying the FSX-exe to P3D as Ian suggests, then putt an underscore in front of the FSX.exe file in the FSX root directory? Like this "_FSX-exe". Now go ahead a load in the normal way.

No, what would that achieve? I can surely try it, I'm just curious what makes you think it should work.

 

Sent from my HTC One X using Tapatalk 2

as expected

No, what would that achieve? I can surely try it, I'm just curious what makes you think it should work.

 

Sent from my HTC One X using Tapatalk 2

Tried it, and as expected nothing much changed. I launched the regular prepar3d.exe, and everything worked as usual, and none of the addons that required executable to be called fsx.exe worked. Launching _fsx.exe which was the original fsx executable obviously did not work.