Which X-Plane 12 libraries work? Check FJS, PM, RuScenery, AR, RA, RE and NAPS compatibility, dependencies and missing-object fixes.
Most conventional X-Plane 11 scenery libraries can load in X-Plane 12 because both use library.txt virtual assets. Install a library only when an airport or scenery package lists it as a dependency. Keep one copy in Custom Scenery; duplicate, merged or nested copies commonly cause missing-object errors and unpredictable asset selection.
Which X-Plane 11 scenery libraries work in X-Plane 12?
Libraries containing standard OBJ8 objects, textures and library.txt exports are usually compatible with X-Plane 12. A library does not normally add visible scenery by itself: an airport or regional package must request one of its exported virtual paths.
| Library contents | Expected X-Plane 12 result |
|---|---|
library.txt, OBJ8 objects and PNG or DDS textures | Usually load without modification |
| Legacy facades, forests, lights and material definitions | May load with warnings or look different under X-Plane 12 lighting and weather |
| Animations using custom datarefs | May remain static if their supporting plug-in or script is incompatible |
| Bundled binary plug-ins | Need separate X-Plane 12 and operating-system compatibility checks |
| Copies of X-Plane 11 default assets | Should not be installed over X-Plane 12 files |
An older library can be operational without using X-Plane 12-specific materials or lighting. That is a visual limitation rather than proof of a failed installation. Airports, mesh and orthophoto packages have different compatibility considerations, covered in our broader XP11-to-XP12 add-on compatibility guide.
Named X-Plane 12 scenery libraries
The table separates packages with an XP12-compatible maintained release from legacy libraries that may still load. Every one is needed only when installed scenery calls its assets; installing the full list does not improve default X-Plane 12.
| Package | Purpose | XP12-compatible or maintained release | Needed only by dependent scenery? | Correct source |
|---|---|---|---|---|
FJS_Scenery_Library | Shared objects and textures exported under FJS library paths | Yes; use the maintained XP12-compatible package | Yes | The official FJS library package from its maintainer, or an authorised copy explicitly supplied with the dependent scenery |
| PM Library | General airport, building, vegetation and regional scenery assets | Yes; an XP12-compatible package is available | Yes | The official PM Library package named in the airport documentation |
| RuScenery | Russian and Eastern European buildings, vehicles and other regional objects | Legacy package; many conventional assets work, but no maintained XP12-specific release is available | Yes | The original legacy distribution referenced by the scenery author; avoid modified or partial repacks |
| AR Library | Shared airport and regional objects exported through AR library paths | Legacy package; no maintained XP12-labelled release is available | Yes | The original author package linked or identified by the airport documentation |
| RA Library | Airport and regional scenery objects exported through RA library paths | Legacy package; no maintained XP12-labelled release is available | Yes | The original author package specified by the dependent scenery |
| RE Library | Shared buildings, airport details and other scenery objects | Legacy package; no maintained XP12-labelled release is available | Yes | The original author package specified by the airport readme or dependency list |
| NAPS Library | A large collection of airport and urban objects used by many older custom airports | No maintained official XP12 release is available | Yes | There is no maintained XP12 source to recommend; prefer an updated airport that has removed or replaced the dependency |
For packages we preserve, check the description and version information in our X-Plane add-on and scenery-library collection. Do not assemble a library from folders copied out of other airports, and do not trust a similarly named package to satisfy a dependency.
For every library below, confirm the requirement in three places: the airport readme, its download-page dependency list and Log.txt after loading that airport. The path reported in the log is particularly useful, although its virtual prefix does not always match the visible folder name exactly.
FJS_Scenery_Library: is it required?
FJS_Scenery_Library is required only when the airport documentation names it or Log.txt reports an unresolved FJS asset path. Install the complete maintained release, not a second copy extracted from another scenery package.
Is PM Library XP12-compatible?
PM Library has an XP12-compatible release, but it is not a standard component of X-Plane 12. Install it when the airport readme or download-page dependency list names PM Library, then confirm in Log.txt that the requested PM assets load.
Does RuScenery work in X-Plane 12?
RuScenery is a legacy library whose conventional objects often work in X-Plane 12, but it does not have a maintained XP12-specific edition. Use it only when the airport documentation requires it or the log identifies a RuScenery path, and check the loaded scene for old lighting, texture or facade problems.
Is there an AR Library XP12 release?
There is no maintained XP12-labelled AR Library release to install speculatively. If an airport readme and dependency list name AR_Library, use the original complete package and verify the exact missing path in Log.txt; AR, RA and RE are separate libraries.
Does RA Library XP12 work?
RA Library is a legacy dependency rather than an X-Plane 12 default library. It can supply conventional assets in XP12, but install it only when the airport documentation or Log.txt specifically identifies RA Library, not merely because AR or RE appears elsewhere.
Does RE Library XP12 work?
RE Library can load standard objects in X-Plane 12, but no maintained XP12-labelled release is available. Check the airport readme, its dependency list and the failed virtual path in Log.txt before installing the original author package.
Can I use NAPS Library in X-Plane 12?
Some old NAPS Library assets can load, but there is no maintained official NAPS Library release for X-Plane 12. If an airport readme and Log.txt confirm the dependency, the safer resolution is an updated airport package that replaces those assets rather than an unverified NAPS re-upload.
Do I need it? A direct troubleshooting flow
You need a scenery library only when one of your installed scenery packages declares or requests it.
- Identify the affected airport. Load the location that produces the warning, close X-Plane and inspect the fresh
Log.txt. The scenery package path near the error usually identifies the airport responsible. - Match the dependency. Compare the missing virtual path with the airport readme and download-page dependency list. Similar initials are not interchangeable:
AR_Library,RA_LibraryandRE_Libraryare different packages. - Install one complete release. Remove or back up an older copy, extract the package and place its root folder directly in
X-Plane 12/Custom Scenery. Do not merge releases. - Check the folder depth. The expected pattern is
X-Plane 12/Custom Scenery/Library Name/library.txt, notCustom Scenery/Archive Name/Library Name/library.txt. Our folder-by-folder library installation checklist covers extraction and placement. - Reload the affected airport. Restart X-Plane, or use its scenery-reload function where appropriate, then revisit the same location and inspect the new log.
- Remove an unused library. If no installed airport or scenery package lists or requests it, the library provides no benefit. Remove the whole package rather than individual objects.
Why does X-Plane 12 report missing library objects?
A missing-object warning can indicate four different faults, and each needs a different fix. Search Log.txt for the airport identifier, library name, reported virtual path and phrases such as Failed to find resource, Failed to load resource, Unable to locate object, could not be found, missing the texture and Error loading the scenery package.
| Fault | How to recognise it | Correct fix |
|---|---|---|
| Missing dependency | The airport names a library that is absent, and the log reports one of its exported virtual paths | Install one complete compatible copy of that library |
| Folder nested too deeply | The files are present, but library.txt sits inside an extra archive or version folder below the package root | Move the complete library root directly under Custom Scenery |
| Outdated library release | The library loads, but the airport requests an asset added only in a newer complete release | Remove the old copy and install the full updated package without merging files |
| Airport references a removed asset | The latest complete library loads, but its library.txt no longer exports the exact path requested | Update or replace the airport; the fault cannot be repaired by repeatedly reinstalling the library |
Capitalisation and spelling also matter on case-sensitive file systems. If the airport package itself is nested, incomplete or installed in the wrong place, use our custom-scenery installation and missing-object checks before changing the library.
Do not rename random object files or add improvised exports to library.txt. That can hide the immediate warning while producing incorrect objects, broken textures or failures after the next update.
Does scenery_packs.ini order matter for libraries?
Ordinary dependency libraries do not need to sit above the airports that use them in scenery_packs.ini. X-Plane resolves their exported virtual resources separately from the visual layering used for airports, overlays, orthophotos and mesh.
Priority can matter when two packages export replacements for the same virtual path. Duplicate releases are especially troublesome because X-Plane may select an asset from a different copy than expected, so keep one clean version of each library.
Should I keep a library that loads with warnings?
Keep a required legacy library only when the dependent scenery displays correctly and the messages are harmless deprecation warnings. Missing buildings, blank textures, failed resources, broken animations or repeated scenery-loading errors indicate a real compatibility or installation problem.
A library producing no visible change is not necessarily broken. It supplies objects only when scenery requests them, which is why loading default scenery does not provide a meaningful compatibility test.