Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
I've got the game on PS3, 360, and PC (because I've picked them up in bundles at sales), and have obviously played it a few times - I've even just started up the game again to make sure, and indeed, where the hatch should be is a pile of rocks which utterly covers that corner.
I'm sorry, but your memory's playing tricks.
On the crashing issue, it does indeed crash more often on Fallout 3 than New Vegas. I wouldn't be surprised if this is part of the old memory overflow problem that plagues these two games. I believe that although New Vegas doesn't come up with the "stopped working" mesage, you will notice slowdowns, especially when you get further on in the game and into the expansions - maybe even total freezes.
Personally, much as I love these games, I can't wait for a new engine ro be used for the next iterations.