Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Same thing happened to me. It's either a side effect of tcling, or the other vault doors are just as broken as 111.
Only way around it is to tcl through, or hit ~ then click on the vault door, then type disable into the console. The entire door will disappear.
You can use the 'tcl' command to noclip into/out of bugged vaults.
However, if you're playing a saved game after the failed vault opening animation, you've likely lost access to VATS.
I believe I've found the fix for that issue.
I've made an Imgur album explaining the cause and fix: http://imgur.com/a/770N4
Here's a short textual summary of the fix:
1. During normal gameplay (not in VATS, a terminal, a conversation, a menu, etc.) , open the console and run the command 'DumpInputEnableLayers'
2. If you see a Layer there, note it's number. Not the hexadecimal one, the normal integer one -- such as '0'.
3. Run the command 'ResetInputEnableLayer [#]' to remove the restrictions that layer had.
I find it hard to believe there's something we're doing on our end that's out of the ordinary that causes it since almost all past bethesda players edit .ini's and this doesn't seem like a very widespread problem. Which is unfortunate since who knows when it will be fixed.
I gave what J-BwB : Lesser Evil said a shot. I went back to the console I never used to preserve my VATS and spawned a little bloatfly with "player.placeleveledactoratme FF000DB2" and while it was attacking me, clicked the panel. The door started to open, and I used VATS to kill the bloatfly.
Feel free to give it a shot guys.
I've heard speculation that perhaps it occurs if you have set 'iFPSClamp=60' in your config fies, but I don't know if there is evidence to back that up.
I can confirm that iFPSClamp=60 seems to be the cause of the problems. I deleted that line from my .ini file and then reloaded a save just outside the subway that leads to vault 114. Replayed that subway section and activated the vault door where it then opened as it supposed to.