Fallout New Vegas

File information

Last updated

Original upload

Created by


Uploaded by


Virus scan

Safe to use

About this mod

Allows DLC cutscenes to be skipped with Attack, something which really can't be shown in screenshots. (Requires NVSE v1.1 or later)

Permissions and credits
Inspired by http://www.nexusmods.com/newvegas/mods/43139/?

The first time through a DLC, it's worth going through the cutscenes for purposes of exposition. But if you go through the DLC in a new game, you really don't care to watch all of that crap again. Yet, Obsidian were apparently so pleased with their cutscenes that they felt that you should have to watch it over and over again, every single time.

Fuck that.

This plugin requires NVSE v1.1 and the first four DLCs - Dead Money, Honest Hearts, Old World Blues and Lonesome Road. This will not help anyone who's experiencing CTD problems from the cutscenes - you'll need to look elsewhere. But if you just want to be able to flip the bird to the cutscenes, this is for you.

To use: Press your Attack button, whatever you've bound that to, while the cutscene you want skipped is playing. This should work for intro cutscenes and outro cutscenes alike. (It's been reported that the Dead Money outro can't be skipped this way, though; working on this as we speak)

Installation: Extract SkippableDLCCutscenes.esp to your New Vegas Data directory, and enable in your mod manager of choice.

Uninstallation: Delete SkippableDLCCutscenes.esp

Please note, practical difficulties mean this mod hasn't been extensively tested. (I don't tend to keep save files around at the start and end of the DLCs just in case.) The Honest Hearts intro is successfully-skippable; If anyone has any problems with the Honest Hearts outro, or the intro or outro of something else, please let me know.

v1.1 fixes the problem of Dead Money's outro not being skippable. Note that skipping Dead Money's intro or outro is not immediate; pressing Attack will trigger a fade-to-black before any loading screen appears. The plugin attempts to duplicate the post-intro (or -outro) code as much as possible to minimise the possibility of bugs - resulting in what seems like odd behaviour, like this. Have faith, and drop me an alert if it doesn't.