Install R2 Library in X-Plane 12 correctly, fix nested folders and scenery_packs.ini issues, and confirm airport scenery can find its objects.
To install R2 Library in X-Plane 12, download and extract the archive, then place the supplied R2 package folder directly in X-Plane 12/Custom Scenery. The folder containing library.txt must sit at that level. Restart X-Plane so it registers the library in scenery_packs.ini.
Install R2 Library step by step
- Close X-Plane 12. Installing scenery while the simulator is running will not reload the library correctly.
- Download the library. Obtain the archive and its included documentation from our R2 Scenery Library download page.
- Extract the archive. Do not copy the compressed ZIP file into X-Plane. Open the extracted folders until you find the actual package folder containing
library.txt. - Copy that package folder into
X-Plane 12/Custom Scenery. Keep the internal object, texture and folder names unchanged. - Launch X-Plane 12. X-Plane should detect the new package and add an enabled entry for it to
scenery_packs.ini.
The correct structure should resemble X-Plane 12/Custom Scenery/R2_Library/library.txt, although the supplied package name may differ slightly. A structure such as Custom Scenery/R2_Library/R2_Library/library.txt is one folder too deep and will not work.
R2 Library belongs in Custom Scenery, not Resources/plugins or an aircraft folder. Our standard procedure for installing X-Plane scenery libraries explains the same folder rule for other object libraries.
How can I confirm that R2 Library is installed?
R2 Library does not create an airport, aircraft or menu item of its own; it supplies objects requested by compatible scenery packages.
- Open
scenery_packs.iniand confirm that the R2 package has aSCENERY_PACKentry rather thanSCENERY_PACK_DISABLED. - Load an airport known to require R2 Library and check that buildings and other library objects appear without missing-library warnings.
- If an error remains, inspect
Log.txtin the main X-Plane 12 folder. Search for the package name,library.txt, or the missing virtual object path.
Does R2 Library need a special scenery load order?
R2 Library normally needs no special position relative to the airport that uses it because X-Plane loads library definitions globally. The entry must be enabled, however, and duplicate or damaged copies can cause confusing results.
Airport, overlay and mesh order still matters for the surrounding scenery. If those packages are also being installed, use our guide to organising scenery and overlays rather than moving the library repeatedly.
Why does X-Plane still say R2 Library is missing?
A nested package folder is the most common cause, followed by an unextracted archive or a disabled entry in scenery_packs.ini.
| Symptom | Likely cause | Fix |
|---|---|---|
No R2 entry in scenery_packs.ini | The package is nested too deeply or still compressed | Move the folder containing library.txt directly into Custom Scenery, then restart X-Plane. |
The entry begins with SCENERY_PACK_DISABLED | The package has been disabled | Change it to an enabled SCENERY_PACK entry while X-Plane is closed. |
| Only one airport reports missing objects | That airport may require another library, or its installation may be incomplete | Compare the missing path in Log.txt with the airport's stated requirements. |
| Errors began after updating the library | Old and new copies may coexist, or files were merged | Remove duplicate R2 folders and install one clean, fully extracted copy. |
| It works on one operating system but not another | Internal file or folder names may have been changed | Restore the names supplied in the archive; case-sensitive systems require exact matching. |
Do not edit library.txt to silence an error. That file maps the virtual object paths used by dependent scenery, so changing it can create additional missing-object messages.
Is R2 Library compatible with X-Plane 12?
R2 Library is an older object library, but X-Plane 12 can generally read the library and object formats used by it. Individual legacy airports may still show visual differences, deprecated-feature warnings or unrelated compatibility problems.
Installing the library only supplies the requested objects; it does not convert an old airport into native X-Plane 12 scenery. If the library loads but an airport remains faulty, check that airport's folder structure and dependencies using our downloaded scenery troubleshooting steps.