iFly Simulations 737 – What It Is and How to Actually Use It
iFly Simulations makes two main 737 products: the 737-400 for FSX and P3D v1–v3, and the 737-800 which also works on P3D v4 and v5. When people type "iFly Manual 737" into a search engine, they are usually looking for either the PDF manual that ships with the product or general help getting it installed and running properly. I am going to cover both because the manual is not as useful as iFly would have you believe, and the installation process has a few quirks that will waste your afternoon if you do not know them. The iFly 737-800 is a high-fidelity add-on for Prepar3D. It features a fully modeled cockpit with functioning panels, switches, and circuit breakers. The 737-400 operates similarly but targets the older FSX/P3D v3 architecture. Both aircraft come with their own documentation. The PDF manual covers panel interaction, system operation, and how to configure the aircraft in the simulator. You will find it in the installation folder, usually under Docs or Manuals. iFly also maintains a support website where they post updates and troubleshooting notes. The manual itself is decent for understanding what each switch does, but it does not explain how to deal with the common crashes and performance issues that show up after installation. Installing the iFly 737 is not difficult, but there are steps that people skip and then spend hours debugging. First, uninstall any previous version of the iFly 737 before installing a new one. This is critical. iFly aircraft accumulate config files, registry entries, and cached data across versions, and leaving old files behind causes everything from broken panel clicks to simulator crashes on startup.
Run the installer as administrator. The iFly installer does not always create its directory structure correctly if you just double-click the .exe from Windows Explorer. After installation, go into your Prepar3D install folder and verify that the iFly 737 folders exist under SimObjects and Scenery. If they are missing, the scenery DLL file was not registered properly during setup. You need to add the scenery DLL entry manually if it does not appear in your dll.xml. Open Prepar3D.cfg or navigate to your AppData folder and find the dll.xml file. Look for an entry pointing to the iFly scenery library path. Without this, the aircraft will load but textures and models will not render correctly. I have seen this cause the 737 to appear as a black silhouette at altitude. Once you add the correct path and restart P3D, it fixes immediately.
Configuration – Getting the Right Setup
The iFly 737 uses its own configuration tool that runs separately from Prepar3D. You will find it in the iFly folder after installation. Before launching the aircraft, open this tool and verify that your controller assignments are correct. The default keyboard mappings are functional but not ideal for extended use. The trim wheel and yoke inputs are especially important to map to physical devices if you have one. Check your graphics settings inside the iFly config. The 737 is heavy on the cabin and exterior detail. If you are running P3D v5 on a mid-range system, set the LOD distance to medium and disable the virtual cockpit lighting effects if you notice frame drops during taxi. The interior lighting system is impressive but it costs CPU cycles. On my machine, disabling cabin dynamic lighting improved ground operations FPS by about 12 frames per second without making the interior look noticeably worse. There is also a performance config option called the dynamic detail system. This adjusts model complexity based on your distance from the aircraft. I recommend leaving it enabled. Disabling it does not give you a meaningful performance gain but it does remove some of the detail that makes this aircraft stand out from cheaper 737 products.
Get the Full Details
Running the Aircraft – Common Problems and Fixes
The biggest issue people run into with the iFly 737 is the initial load crash. This happens most often when P3D cannot find the required DirectX components or when the Microsoft Visual C++ redistributables are mismatched between versions. The fix is to install all the Visual C++ packages from 2005 through 2019, both x86 and x64. Yes, all of them. iFly recommends this in their documentation, but the recommendation is buried in a FAQ page that most people never read. Another issue is the autopilot disconnecting unexpectedly during approach. This is not a bug in most cases. The iFly 737 AP has a sensitivity setting that reacts to turbulence and wind shear indicators. If you are flying into a busy airport with realistic weather, the autopilot will disengage more frequently than in stock aircraft. There is a workaround: go into the iFly config and lower the turbulence sensitivity slider. This does not disable the feature, it just makes the AP less jumpy. I set mine to around 40 percent and have not had unwanted disconnects since. Sound issues are also common. Some users report no engine sound or muffled audio after installation. This is usually a problem with the audio device selection inside the iFly sound config, not a bug in the aircraft itself. Open the iFly audio settings and make sure the primary playback device is set to your headphones or speakers, not a virtual or disabled audio output. The iFly sound engine does not automatically switch devices the way P3D does, so this setting needs to match your actual audio hardware.
Performance Expectations
The iFly 737-800 is demanding. On a system with a 3070 or better GPU and 32GB of RAM, you can expect stable 40 to 50 FPS in the virtual cockpit at medium settings with MSAA at 2x. If you push to ultra settings and high LOD, you will drop into the 25 to 35 FPS range during ground operations. The VATSIM and weather overlays add additional CPU load that compounds the problem. The 737-400 version runs slightly better on older hardware because it targets P3D v3 which is less demanding than v5. However, the 400 lacks some of the visual improvements in the 800 model. The trade-off is real. If you have a weaker machine, the 400 is the more viable option. If you have a newer system, the 800 is worth the extra hardware cost.
Where to Get Updates and Support
iFly releases patches periodically. These are available through their website and through the launcher that comes with the product. Always update before reporting a bug. A significant number of forum posts about crashes are resolved by a previous patch. Check the release notes first. The patch history is brief but each one addresses real issues. The iFly support forum is active but slow to respond during peak hours. If you are asking for help there, include your P3D version, your graphics card, your OS version, and the exact error message. Posts that omit this information get minimal engagement. I learned this the hard way after spending two days troubleshooting a texture glitch that turned out to be caused by an incompatible shader mod I had installed for another aircraft. Removing that mod fixed it instantly.
What the iFly Manual 737 Does Not Cover
The manual does not discuss how the FMC interacts with third-party navigation databases. If you use Navigraph or an alternative nav data source, the iFly 737 requires you to configure it through the aircraft settings menu, not through the FMC directly. The process is straightforward once you know where to look, but the manual assumes you are using the default nav data that ships with the product. This assumption causes confusion for users who have switched to Navigraph weeks ago and are wondering why their flight plans are not loading correctly. The manual also does not mention the weather interaction bugs that appear in P3D v5 with certain cloud layer configurations. If your aircraft vibrates excessively or the autopilot behaves erratically during certain weather conditions, check your P3D weather settings. Reducing the cloud layer complexity in the main P3D config file often resolves the issue without any changes to the iFly product itself. This is a known limitation of the P3D v5 rendering pipeline and iFly has acknowledged it on their forum, but it is not in the official documentation. The iFly 737 products are among the more complete 737 simulations available for Prepar3D. They are not perfect, and they require some effort to get running smoothly on modern systems. But once configured correctly, they offer a level of detail and realism that justifies the initial learning curve. The manual is a starting point, not the complete guide. Most of the real knowledge comes from trial, error, and the community forums where experienced users share the fixes that iFly never thought to document.
