- Use the manual option to download this mod, then use "Install from file" with your Mod Manager (more reliable).
- Vortex versions prior to V1.5.6 has a bug that won't let you select "Extra DLC Features". Make sure Vortex is up-to-date.
- If you do not have all the DLC's then make sure the "Extra DLC Features" is set to "None" (if it isn't already)..
- If you want the Keyboard/Gamepad to control Manual Flight you must also install F4SE.
- NMM sometimes treats Patches/optional files as an update to the main mod and offers to 'uninstall' it. Say NO.
- If you do not use a Mod Manager and just extract the files (not Recommened) then you are installing the "Realistic", All DLC's version
- Vortex/MO2 sometimes places FPV_Armored.esp ABOVE FPVertird.esp! Create a dependency rule so FPVertibird.esp is BEFORE FPV_Armored.esp.
- Vortex/MO2 won't allow you to install the "Paint Jobs for Vertibirds" mod. Install the optional patch first.

- If Multilanguage version your Mod manager may have failed to copy/link the "FPVertibird - Main.ba2" file into your game, Use you Mod's file explorer to check.
- Check if you have exceeded your BA2 limit and the game has not loaded the FPV archive (install CMT to verify).
- If you use a Language Patch for FPV you may have missing/corrupted strings for your language in it. Disable such mods to check...
- If using FPV V1.6.x make sure you have not installed any patches/Mods listed as ONLY for FPV 1.7

- Make sure the Mod is installed with a Mod Manager AND Activated.
- Make sure you installed the latest version.
- If you copied files from the mod into your Data directory This is not supported. Use a Mod Manager.
- If you get the message "Some of the enabled plugins depend on others that are not enabled" then change "Extra DLC Features".
- If you do not have all DLC's installed, make sure you selected "None" for the "Extra DLC Features" during install.
- If you installed by using the "Mod Manager Download" button, try "Manual Download" and "Install from File" in you Mod Manager.
- Check the file "C:\Users\\AppData\Local\Fallout4\Plugins.txt" for the lines "*FPVertibird.esp" and "*FPV_Armored.esp".
- NOTE: Recall beacon, Hats, Rings, Vertipad Kits, Holotape etc are in a separate "Personal Vertibird" menu in Chem station
- NOTE: All Vertipads are in their own "Vertipads" section under "Structures" in workshop menu (exists only if you have built a Vertibird)

- There is no Vertipads menu until you build your first vertibird.
- The menu may not appear immediately after you build a Vertibird. fast travel away and back or save and restart your Game.

- If no Menu is displayed then this happens if using F4SE but you did not install the F4SE script extensions (.pex files).
 Try reinstalling FPV with the "Debug" or "F4SE Test" install option - If it works then that is the issue. Install F4SE properly and revert FPV.
- If you DO NOT use F4SE then re-install FPV and select the "No F4SE" install option.
- If the Recall Beacon menu is displayed, but you get this message for any option, then use the "Reset Vertibird" option to repair it.

- The internal state of ALL your Vertibirds has been lost, probably due to saving while F4SE was broken (above).
- They we be unusable until fixed. If F4SE was the issue then fix your F4SE install then :-
- Either revert to the save before you upgraded to V1.6.8, OR Store and recraft your Vertibirds, OR manually do "Reset Vertibird" on them.

- Your mod manager has failed to activate "FPV_Armored.esp", or placed it above FPVertibird.esp in your load order.
- You have an old version of FPVertibird.esp still active (mod manager failed to replace it with one in your latest download)
- You used the "Mod Manager Download" Nexus button and the download is corrupt.
- Try a clean re-install (as per instructions under "Doing a Clean Reinstall"towards the bottom of this article)

- This occurs if the "FPVertibird - Main.ba2" supplied in a mod is missing (bad installation via your mod manager).
- This can also occur when using MO2 if it places FPV_Armored.esp before (above) FPVertibird.esp in the Load order.
  Apparently the latest version of MO2 has resolved this, but I have not been able to confirm this.
- Another reason could be something consuming all Script resources (like SS2). Go well away from a settlement and recall your VB.
  If it returns to you then the install is fine but your scripting resources are being overutilized.

- Some mod has set the player to "Ghost" (immune to physical damage). This breaks many game mechanisms, including FPV.
- Via the console (~) do the command player.setghost 0 then try the recall beacon again. This will verify this is the problem.
- If that is not the issue then some mod is consuming all script resources so the Recall beacon script isn't getting time to run.

- Did you wait until you got the message "Ready to Fly"/"Ready, Choose Destination"? With many Companions it can take a few seconds.
- The same issues that cause "Recall/Command menu doesn't open"  (see above) will cause this, so check that guide first.
- Check your Fallout 4 Data directory for (at least) the following files: FPVertibird.esp, FPV_Armored.esp, FPVertibird - Main.ba2
- Make sure there are no fpvertibird directories under Data/scrips, Data/meshes & Data/materials.
- Note: If you are using MO2 then check this when your game is paused and minimized, or use the MO2 directory explorer function.
- Enable logging ("Advanced debugging") and look for errors in your Papyrus.0.log (in documents\my games\fallout4\logs\script).
- If you have existing FPVertibirds you will also see in there an INFO message for each one. Their version should be at least 1.68

- Did you get "Ready to Fly" message after Companions have Boarded? You can't fly manually via WASD/Dpad if you didn't.
- If you get "Ready, Choose Destination." instead it means your F4SE installation is not working or not supported (VR/Xbox).
- If you installed the default version of FPV then it REQUIRES the pex files (that comes with F4SE) to be installed with F4SE.
- Also If F4SE is not running you will not get a Holotape/MCM option to set the "Manual flying" key.
- without F4SE you can still fly manually, but only by using menu options available via the recall beacon or "Pilot Command".
- If you have F4SE then Check it's working by typing GetF4SEversion in the console (~). It must be at least 0.6.23 (or 0.7.2 for NG)
  If you get "command "GetF4SEversion" not found" then F4SE is NOT running - you have not installed or run it correctly.
- Did you follow the instructions for installing F4SE (starting your game via f4se_loader.exe) and installed the F4SE pex files?
- Are you on SteamDeck? If so - sorry - F4SE does not support the Steamdeck Controls.
- Did you press R to take off first? If you are already flying to a Map destination, did you press R to go manual?
- Check the "Manual Control key" is set to "Ready Weapon" in the Holotape/MCM (or use the key you set it to).
- Make sure no other mod has taken over the R key when you are onboard (If so then change the button via the MCM/Holotape).

- This occurs if the scripts (in FPVertibird - Main.ba2) are from a dfferent version than the mod (esp) files.
- "Your Personal Vertibird is already here" is also a symptom of this.
- This can occur if your mod manager does not activate FPV_Armored.esp  OR places it before FPVertibird.esp.
- Alternatively, if you upgraded but still have some script files in your Data/scripts/fpvertibird directory - that will cause it too.
- It also may occur if you have an outdated mod installed that requires this mod (eg. FPV Pilot/Paintjob Mod or Sorting patch for FPV).
- If you are using the Multilanguage version and use an optional translations mod, then that mod may be out-of-date.
- Make sure your Mod Manager has both esp's activated (especially FPV_Armored.esp needs to be active).
- If the "Load/Unload Power Armor into Cargo" menu choice is missing then that suggest it is not active/installed.

- You are running old fpvertibird scripts somehow. Make sure there is no fpvertibird directory under "Data/scripts".
- If you use MO2 then you can only check this when the game is running. Ctrl-Alt-del (background) the game so you can check.
- Make sure your mod manager replaced the "fpvertibird - main.ba2" correctly if you installed a Hotfix/patch.
- Enable debug logging (as per this article) and look for an FPvertibird "INFO" message in your papyrus.log.0. It should say version 1.638
- No message, a lower version, or an ERROR message about version mismatch means you are running old fpvertibird scripts.

- You are wearing a Vertibird Ring/Hat. Unequip it and try to board again
- Note that Companions with Vertibird Rings/Hats may interfere/act buggy when boarding non-FP Vertibirds.

- Can be because you are trying to travel to another worldspace (DLCs, Diamond City, etc) - not allowed by the Game. Use "Fly to" menu.
- If you have enabled Fuel Consumption then having no fuel will also cause this message.
- If Boarding has not finished (you have not received the "Ready to Fly" message) you may get this.
- Otherwise it can be due to slowly running game/script lag. Close and re-open the Pipboy map should resolve this.

- You have installed a mod that disables fast travel (such as "Immersive Fast Travel"). See if the Author (or I) have a patch to support VBs.
- The game has temporarily disabled all Fast Travel.

- If you have recalled it, then Cancelled the recall, then it is returning to it's departure point still. You need to wait until it lands.
- If it is taking off or landing you will get this message. Wait, it needs to complete this before responding to new commands.

- Your Mod manager has failed to activate "FPV_Armored.esp", or placed it above FPVertibird.esp in your load order

- You have the obsolete "FPVRings.esp" (Rings Replace Hats) mod still active in your load order. Remove/disable it.

- SS2 will consume all scripting resources in a settlement so FPV Boarding, exiting, and Recall menu operations will be unreliable.
- Script resources are mostly uneffected by the power of your CPU/GPU, and are very finite.

- You need to have Pilot Type (MCM/Holotape) set to "Random, Protected,No Inventory".
- [Optionally] Pilot Voice set to Standard/Takeoff Comments (if you want to be able to talk to them).
- After any change (config or Mod installation) you need to "Change Pilot" off the Vertibird's Recall Menu to get your new Pilot.

- Your Mod manager has failed to copy/link the "FPVertibird - Main.ba2" file into your game.
- You have exceeded your BA2 limit and so the game has not loaded the above archive.
- You have missing/corrupted strings for your language (perhaps a faulty language update mod)...

- "Classic Holstered Weapons" is known to be one cause of this, so you need to update the CHW config.
- Either download and install "Classic Holstered Weapons ini Patch" (optional Files), or update ClassicHolsteredWeapons.ini :-
- Put "ExcludedNPCFormId_FPVertibird=FPVertibird.esp|808" under "[ExcludedForms]"
- If you use Warbird for FPV you need to also add "ExcludedNPCFormId_FPVWarbird=FPVWarbird.esp|807" as well.
- If you have Enclave Classic Vertibird (FPV) then add "ExcludedNPCFormId_FPVClassicFO3VB=FPVClassicFO3VB.esp|801" too.
- NOTE: If you are using MO2 then you need to make these changes via the MO2 ini configuration section.

- CTD when entering Workshop can occur if you remove mods that adds Workshop Menus/items (without using the Mod's "uninstall" process).
- Another symptom would be entirely missing menus (such as no 'Special' menu). Note the Vertipads menu doesn't appear initially.
- My mod will correct the 'Structures' menu, but none of the other workshop menus - so you may need to 'repair' those menus yourself.
- If you need to repair your Workshop Menus, use a mod like SMM. Read that mod's description for info on why this happens.
- If you are missing the Vertipads menu (and you have just built a Vertibird) save and restart your game.

- Nothing to do with this mod. When flying, the game is loading and unloading NPC's, while rendering terrain under you, stressing the Game.
- Also many user made mods can't handle rapid activation and de-activation, which is made worse the faster you fly.
- Broken/missing precombines can also stress your PC to the point where the game crashes. I have tools for checking this.
- Check what mods effect the area you are approaching when the CTD occurred. Turning on Papyrus debug logging may help to show issues.
- Install Buffout 4 as it fixes some bugs and generates a crash report that others may be able to help you with.

- When NPC's become 'visible' (loaded) the game moves them to the nearest 'ground' if it thinks they are not on ground.
- Unfortunately due to a game bug, workshop constructions are NOT recognized as 'ground' - like a landing pad built off the ground ...
- This is why Brahman can end up on roofs, settlers inside walls, and Vertibirds buried under the  landing Pad.
- If a Vertibird ends up 'caged' inside a building this way it 'jitters' (the physics goes wild) and causes the game to freeze for a short time.
- My mod tries to fix this, but the fix is also slowed by this 1FPS jitter. Don't build Landing Pads on top of constructions...

- Finding a place to build it can be difficult, try rotating it side on and move around until it turns green.
- You can't build it on badly navmeshed ground or with obstacles (base game issue - not my mod). Spectacle Island is particularly bad.
- Normally you CANNOT build the Vertibird on the Vertipad (the game does not recognize that as 'flat ground'!).
- If all else fails - try using a mod like Place Everywhere...

- Prior to FPV V1.6.8 scripts from F4SE were included because some people fail to install F4SE properly (they forget the .pex files)
- These are from the latest F4SE (which doesn't cause issues if you use an eatlier F4SE), but are V27 script versions.
- If you have an earlier version of F4SE (and didn't install it via your mod manager) then you may get a version warning message.
- To fix, Install the lastest version of FPV (1.6.8 or later) - but make sure your have installed F4SE correctly otherwise it won't work!

- You have to craft the Config Holotape at the Chemistry Station (I hate mods that force it into your Inventory).
- No MCM? You need MCM and F4SE installed/running.

- See the section "No Gun/Your own gun when you board" first - otherwise :-
- Some other 'rideable something' Mod is taking over the Vertibirds. Mod conflict. Check the Description page for Mods that Conflict.
- Your mods are too much for your PC/game and is causing script crash/dumping/lag. This mod is heavily scripted for landing and takeoff.
- CTD's while flying over built up areas (especially Boston) are an indicator your PC is running out of resources - not an issue with this mod.
  The NPC's and landscape being loaded as they come into view is too much for your PC - especially if you have the VB's flying faster.
- If Vertibird just started acting odd, then it's game state can get corrupted. Use the "Reset Vertibird" option in the recall beacon menu.
- If you get "Command failed" when trying to recall it this also means it's state is corrupted. It should auto-repair so try the recall again.
- If "Reset Vertibird" doesn't fix it then at a settlement "store" then Recraft it.
- Hard to fly on Manual? Treat WASD keys as "instructions" to the Pilot which flies in it's own way in it's own time. It's not a bug. See FAQ.

- If you set the "Passenger/Player Vulnerability when Onboard" to "Player also Immune to Gunfire" then the player is set to "Ghost".
- The game has a bug whereby this also makes certain Magic effects no longer apply to the Player.
- Many Hotkey/Consumed/Quickkey triggers (such as WestTek optical effects) use Magic effects so will be broken and no longer work.
- As correct functioned of the magic effect is used to replace a consumed object in your inventory, they will dissappear from it too.
- Don't set "Player also immune to Gunfire" if you want these other mods to function while onboard.

- This is a patch for Power Armor Game Bugs that are not specifically for FPVertibirds, so can be placed anywhere (or disabled).
- Why would you move/disable it? it can conflict with other mods that modify Power Armor, so seperating it was a better option.
- FPVertibirds will not be effected if you move/disable it. It fixes the Stuck PA Perk bug.

- The above mentioned PAVertibirdDockFix.esp changes the PA Effect Enchantment to prevent the stuck PowerArmorPerk Game bug.
- This may conflict with a PA mod that also update this effect. Place your PA mod after PAVertibirdDockFix.esp in your load order.
- If that fixes it then I recommend you also set the Holotape/MCM setting "Keep passengers on board when Docked" to "NO".
- Currently known effected mods are listed in the "Mod Conflicts" section on the Description page. Report yours if it is not there.

- The Holotape/MCM settings are overall game style settings, not realtime changes. You should not have to change these often.
- Front guns/Minigun/Vertibird Skin settings are "Initial" ie. what a new Vertibird gets. They don't change existing ones.
- Use the Recall & Command beacon (even when inside the Vertibird) to change the above for that Vertibird in real time.
- All other Holotape/MCM settings are applied when a Vertibird is boarded/takes off, and are not rechecked until it lands.

- Companions may still board the Vertibird if commanded to "Stay" (depends on Companion mods you have installed). Game bug.
- "E [land]" does not work if flying on manual and F4SE is not installed. Game bug. Use in-flight menu "Land" command.
- Recalled Vertibird sometimes 'bounce lands' (immediately takes off again). Game Bug. It should try landing again, or Use "Land" again.
- Vertibird may 'hijack' player and fly off instead of landing. Same Game bug. Retry the Land command (either E or in-flight menu "Land")
- Rotor noise continues for a time after rotors have stopped. Game Bug. The sound is not syncronised to the animation.
- Changing from 1st to 3rd person and back can sometimes mess up viewpoint when in Pilot Seat. Game bug, Can't fix.
- Sometimes Vertibirds will still move off their Landing Pad, even with my mitigations. Game Bug. See FAQ "The 1FPS bug".
- POV switching via the V key can cause the Turret Minigun Viewpoint to be be locked. Game bug. Use mouse wheel instead of V key.
- The "Change Features" option of the Pilot can cause them to be stuck in an action, naked. Exit from the Looks menu and try it again.
- Sometimes, after Fast Traveling in your VB, you get "[You cannot go that way]" messages while onboard. Exiting the VB fixes this.
- The sound reverts to Interior VB ambience during the Fast Travel blackout - even if you started off in 3rd person view.
- If the "Fly To" Site is a place the player is not allowed then Player will not travel during the blackout (stay in hovering VB).
- There are no entry/exit animations for "Standing" positions so you will fall through the floor. I can't fix this.
- Enclave Assaultrons are hostile to Pilot/VB at Enclave Outposts. Faction bug in AR, to fix use the Enclave Pilot Patch (optional files)...
- BoS quest Spoils of War puts a VB at the wrong dock, so if flying to the Prydwen you will stop and hover. Press E to use other dock.

- Nasty game bug occurs when you go inside any Airship and leave PA suited Companion(s) in the Vertibird (Fixed since V1.6.3).
- A Perk on that Companion may become permanent - currently the PowerArmor Perk on Companions who were in PA.
- This gives the Companion "no fall damage", and confuses some mods into thinking they are still in PA, such as "NPC Outfit Manager".
- All recent FPV versions include a patch to the prevent this problem (can be removed during installation).
- Note this patch can interfere with some PA enhancement Mods (see mod conflicts on Description page).
- If you remove/disable it you should change the "On Landing, Passengers" setting to "Exit after Player" so the issue can't happen.
- Currently there is no fix for companions who have already been affected by this bug ('RecycleActor' will not fix it).
- If you have a mod that gives you're companion problems then you will just have to leave them in Power Armor when using that mod.
- Mod added Companions can usually be deleted and 'rehired', or do a clean re-install of that Companion mod, so can be fixed.
- To see if a Companion has been effected, Select them in the Console (when not in PA) and type "hasperk 1f8a9". A result of "1.00" is bad.

- Make sure any FPVertibirds have landed before upgrading (no need to delete anything).
- Uninstall FPVertibird and any Patches (leave compatibility patches for other mods though).
- Mow Install the new version without restarting (answer YES to any overwrite messages).
- I recommend you select (at least) the same features you used in the previous version during the installation.
- Make sure you have NO 'FPVertibird' directory under data/scripts, data/meshes, data/materials
- NEVER restart the game without FPV installed, unless you are removing the mod PERMANENTLY!
   (this mod NEVER requires a 'clean mod installation' as scraping all Vertibirds has the same effect and is safer for your saves)
- Restart Game. Ignore warnings of missing "FPV..." mods as these were part of the old version/hotfixes and are now built in.
- If you can, you should Store and Recraft your Vertibird(s) to make them 'new' (but it is not required).
- NOTE: To use the "Rename Vertibird" option requres F4SE, Rename Anything, and Textinputmenu installed.

- Scrap/Store (Tab) ALL your Vertibirds, remove any Vertibird rings/hats from your companions, and release any Pilot/Gunner you recruited.
- Craft the Vertibird Utility (as a Chem Station) and activate it. If it finds any Vertibirds then select "Destroy all Vertibirds".
- Save game and exit.
- Uninstall your existing FPVertibird Mod and any patches to it.
- Install FPV V1.7 (and any patches for it) and start your game.
- Recraft your Vertibirds and any rings etc. Re-recruit your Pilot/Gunner, and re-equip your companions with any Rings.

- Remove any special armor/inventory you gave to your Pilot(s).
- Scrap/Store (or Destroy) ALL your Vertibirds. If you have lots then craft the "Vertibird Utility" to Destroy them all.
- There is NO need to scrap/destroy Vertipads, Landing lights, Recall Beacons, or Passenger Rings and Hats.
- Go through the above "Upgrade" process (but install the version you wish to downgrade to instead of the latest).
- Rebuild your Vertibird(s) again

- NEVER start the game between any of the following steps, as you will get errors and loose your existing VB's etc!
- Uninstall the FPVertibird Mod and any patches to it. You should have NO fpvertibird directory under data/scripts, data/meshes, data/materials.
- ReInstall the main FPVertibird mod (multilanguage or English only).
- You should select (at least) the same features you used in the previous installation, BUT leave Install Mode as Standard.
- If using Multilanguage, install the latest FPV Language fix mod you can find on Nexus for that version only (optional).
- Start your game from your last save, as normal.
- If you want to change any of the MCM settings - this would be a good time.
- (optionally) Store (Tab) and recraft your Vertibird(s) at any of your Settlements (this will make sure they are also Clean).

- Remove any special armor/inventory you gave to your Pilot(s).
- Scrap ALL your Vertibirds. This way you will not loose any of their Cargo/stored PA frames.
- Recommended: Craft a "Vertibird Utility" and select "Destroy all vertibirds" to make sure everything is gone.
- Recommended: Scrap/destroy Vertipads and Landing lights. Recall Beacons, Passenger Rings, and Hats can be left (or scrap for parts).
- If all your Vertibirds are scrapped/destroyed you should no longer have a "Vertipads" item in the Workshop menu (under Structures).
- Exit game and uninstall All FPV mods.
- Restart your game. No need for a new game.