- Fri Aug 24, 2018 12:07 pm
Is there a chance you may have other AI packages installed onto your computer? Or have you used any AI packages previously that could be causing a conflict? The failed to create aircraft message is very important as the first three letters in XXXXX let us know if it's actually FLAi or another package.
On my own personal setup, I have FLAi running on my "M" drive under M:\FLAi, and my P3D installed on my SSD under the regular "C" drive. When using the FLAi Operations Center, you can specify where you want FLAi installed. I created a folder called FLAi on my M drive, pointed the installer to that folder, then pressed update. Once FLAi is finished installing it will create the addon.xml for you under your Documents\P3D Add-ons folder. Although the Simobjects.cfg method will work, it's not recommended as everything you need is condensed into your home FLAi folder and connected to P3D using it's native SDK.
Now try this:
1. Navigate to your Documents\Prepar3D v4 Add-ons and ensure there is no folder called, "FLAi" or "BVAI" or "SPAI." If there are then delete these folders.
2. Navigate to your Documents\vPilot Files folder and ensure there is no folder called, "FLAi" or "BVAI" or "SPAI." If there are then delete these folders.
3. Delete your FLAi folder you created in your SimObjects folder.
4. Delete any FLAi effects or texture files you moved over to the P3D equivalent folders.
5. Adding a path called Default Airplanes in SimObjects\FLAi\SimObjects\Airplanes might cause a conflict as it does not follow P3Dv4 SDK for third party addons. This is why we use the addon.xml method. It's quick, easy, and very organized. Editing core P3D configuration files is a huge headache, and one I personally stay clear of. One typo, out of order entry, or in this case the lack of a correct path can cause errors. Delete this entry you've added and save.
6. Start P3D without any AI installed and fly around for a few minutes. Also start Vpilot and ensure there are no AI packages listed in the settings\Model Matching\Advanced tab. The only thing that should be listed is SimObjects\Airplanes.
7. Download the FLAi Operations Center and Run As Administrator. If your computer doesn't give you the option to run it as administrator then that's fine.
8. Create a folder called, "FLAi" on your E drive. You can also use the default Appdata path if you wish to not create any new folders.
9. Go into the FLAi settings tab (Gear box icon) and change the simulator to P3Dv4 regular or with dynamic lighting. This is your choice, but if you use dynamic lighting in the simulator then go with the Dynamic Lights option.
10. Change the FLAi path to the folder you have created in the E drive. Ensure that after you press "OK" the path is correct. If you choose to use the default path, you can just leave it as Appdata.
11. Press Save, then update and let the installer do its thing.
12. Once the installer has finished, open P3D and enable FLAi when prompted. Please advise if you aren't prompted.
13. Load up at an airport with traffic, and open Vpilot. It may run through a self check to detect any new models. You should notice if you go into the Vpilot settings\Model Matching that there are now 1,800 or so models identified. You should also notice under Model Matching\Advanced that FLAI is listed and checked. FLAI should be the only model matching package listed. If there are others please uncheck them as they can conflict.
14. Under Vpilot Settings, click Model Matching\Custom Rules, and add the FLAi Model Matching.vmr. This is located in Documents\Vpilot Files. If there are other VMR files listed please delete these. Press Apply when finished.
Let us know if this fixes it. Although you can use the Simobjects.cfg method, FLAi was not designed to be used this way. An organized sim is a happy sim.