Discover the best VR mods and add-ons for X-Plane 12, with cockpit tools, performance helpers, scenery choices and common problem fixes.
The best X-Plane 12 VR add-ons are AviTab for cockpit charts, XChecklist for checklist procedures, BetterPushback for VR-friendly ground handling, X-Camera for saved viewpoints, and FlyWithLua NG with a conservative performance script such as 3jFPS12. Add scenery only after maintaining stable headset frame timing.
Which X-Plane 12 VR add-ons are worth installing?
For most VR pilots, the useful shortlist consists of cockpit tools that reduce trips back to the monitor and one carefully chosen performance aid.
| Add-on | Best use in VR | Main caveat |
|---|---|---|
| AviTab | Charts, documents, airport diagrams and a moving map inside the cockpit | Charts and documents must be supplied separately; aircraft integration varies |
| XChecklist | Interactive checklists that remain visible in the headset | Best results require an aircraft-specific clist.txt file |
| BetterPushback | Planning and controlling pushback without removing the headset | Use a build explicitly compatible with X-Plane 12 and test it with each aircraft |
| FlyWithLua NG and 3jFPS12 | Dynamically reducing visual load to protect VR frame timing | Old scripts or multiple scripts changing the same settings can conflict |
| X-Camera | Saved pilot positions and specialised camera workflows | It does not improve headset tracking or increase frame rate |
AviTab is the best first installation because it keeps reference material inside X-Plane 12. In an aircraft with native AviTab integration, it behaves like a panel-mounted tablet; otherwise, it can be used through its plugin window. It does not include licensed navigation charts, so pilots remain responsible for supplying suitable and valid material.
XChecklist is especially useful with complex aircraft. It can display checklist items and automate some confirmations when the aircraft's checklist file supports them. Without a suitable clist.txt, the plugin has little to show.
BetterPushback removes one of VR's awkward monitor-dependent tasks. Compatibility can differ between aircraft, particularly those with custom steering or ground-handling logic, so test the tug before relying on it for an online or tightly scheduled flight.
3jFPS12 is useful when scenery complexity causes intermittent slowdowns. It runs through FlyWithLua NG and adjusts visual detail to pursue a chosen performance target. Set a realistic target for the headset and runtime; aggressive settings can produce obvious object-detail changes during flight.
X-Camera is optional rather than essential. It earns its place when an aircraft loads with a poor pilot position or when saved cockpit and external views matter. Our practical X-Plane 12 plugin shortlist covers these tools and their broader non-VR uses.
Are scenery and graphics add-ons good for X-Plane 12 VR?
Scenery can make X-Plane 12 VR far more convincing, but it usually costs more performance than a cockpit utility.
- Detailed airport scenery gives the clearest benefit during taxi, take-off and landing. Install airports for places actually flown rather than filling the simulator with overlapping packages.
- X-World overlays suit low-level VFR flying where plausible buildings, roads and landmarks matter. Dense objects can increase CPU load.
- Locally stored orthophotos are the better choice when predictable loading matters and ample storage is available.
- AutoOrtho reduces the need to keep every tile locally, but streamed tile loading can cause pauses when the network, cache or storage path cannot keep up.
Our comparison of X-Plane 12 graphics and scenery upgrades explains the trade-offs between orthophotos, overlays, mesh and detailed airports. In VR, introduce one scenery layer at a time and test over a demanding city or hub rather than judging it from an empty rural runway.
Which VR mods should be avoided?
The most troublesome VR mods are old X-Plane 11 scripts, competing performance tools and utilities whose windows can only appear on the desktop.
- Legacy private-dataref scripts: Scripts written around X-Plane 11 rendering behaviour may do nothing in X-Plane 12, cause visual faults or stop working after simulator updates.
- Stacked optimisation scripts: Two tools adjusting level of detail, clouds or resolution can continually overwrite each other and create pulsing visuals or inconsistent frame times.
- Post-processing injectors: Effects designed for a flat monitor may not appear correctly in both headset views, and graphics hooks add another failure point.
- Screen-based camera shake: Artificial head movement adds little when the headset already controls the viewpoint and can make VR uncomfortable.
- Legacy window injectors: A detachable operating-system window is not automatically visible in VR. The plugin must expose a VR-compatible X-Plane window or provide an in-cockpit display.
How should VR add-ons be installed safely?
Install VR mods one at a time over a working X-Plane 12 VR baseline, then test each addition in both 2D and VR.
- Confirm the base simulator first. Establish correct runtime, controller, centring and graphics behaviour using our X-Plane 12 VR setup procedure.
- Check simulator compatibility. Use the X-Plane 12 release of a plugin or script rather than assuming every X-Plane 11 package still works.
- Install it in the correct location. Plugins normally belong under
Resources/plugins, while FlyWithLua scripts go in that plugin's scripts folder. Our installation and folder guide for X-Plane mods covers aircraft, scenery, plugins and scripts. - Test one aircraft and airport. Verify that the simulator loads, the plugin window appears in VR and cockpit controls remain usable before adding anything else.
- Read
Log.txtafter a failure. Remove the last plugin or script and check for loading errors, missing dependencies or duplicate installations.
A mistake we see constantly is an add-on folder nested one level too deep. Another is keeping two copies of the same plugin, one globally and another inside an aircraft package. Both can prevent loading or produce unpredictable behaviour.
Why does a plugin work on the monitor but not in VR?
A plugin usually remains monitor-only because it uses an ordinary desktop window rather than X-Plane's VR-capable plugin interface.
- If the window has a VR placement or visibility control, enable that before entering the cockpit.
- If it is a separate operating-system window, it may never appear inside the headset without explicit VR support.
- If controllers cannot operate the panel, test the same control with the VR mouse and then in a default X-Plane aircraft. Success in the default aircraft points to an aircraft manipulator or VR-configuration problem.
- If performance collapses only after enabling the add-on, remove scripts first, then disable scenery layers and plugins in reverse installation order.
No single mod fixes poor VR performance. AviTab and XChecklist improve usability; BetterPushback removes a monitor-dependent task; dynamic detail scripts protect frame timing by sacrificing visual range. That small combination is a better starting point than installing every graphics enhancement at once.