[P3D5] - Flight Sim Labs - Airbus A320 & A319 & A321 (Aircraft)

Установка в P3Dv5

См. README.txt

Known causes of CTD

• 1. Incorrect anti-virus exclusions - here is what you should have:

(Your P4D Add-on Folder)\FSLabs

(Your P4D Add-on Folder)\Spotlights

C:\ProgramData\FlightSimLabs\LAAS


Recommended for performance reasons:

(Your P4D Install folder as a whole)

(Your P4D Add-ons Folder as a whole)



• 2. Unicode/non-English characters in the install/documents path - does your Windows user contain any non-English characters (such as accents or umlauts etc.)? We discovered an incompatibility whereby if you install the A320-X in a folder whose path has Unicode characters (such as paths that contain people's names in French accented characters or German umlauts etc.), you get this crash. The solution is to install to a path (any path of your choice will do - for example: "F:\FSLabs\Prepar3D v4 Add-ons" if, say, the F: Drive is your fastest disk) which does not contain Unicode characters.


• 3. Your "Water" graphics settings are set to "Ultra" - try dropping them to "High". You must restart P3D after making this change - P3D must not be loaded with water settings at Ultra.
• 4. You are running EZDok v2.5.0.11 or earlier - this version is incompatible with Prepar3D v4.1 and causes crashes, instability or freezing. Get the latest v2.6 or better and - this is important - go to %appdata%\Roaming\Lockheed Martin\Prepar3D v4\ and delete cameras.cfg and CustomCameras.xml as they were corrupted by EZDok.
• 5. Prepar3D crashes and the Event Viewer suggests a crash in FSLSounds.dll (or any other FSL dll). This is because something caused an error in a previous load of Prepar3D and Windows decided to intervene and permanently mark that DLL as unsafe. You need to run "regedit", find the registry setting for
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
and in there, edit the entry for Prepar3d.exe to REMOVE any mentions of
Data = $IgnoreFreeLibrary
(or the other FSL dlls accordingly).
Then, restart the sim - you'll get the error message once again, but click Yes, and the application will work correctly this time.
Also, make sure your sim is marked and running with "Run as Administrator".

Скриншоты