Loden1111 Posted December 2, 2010 Posted December 2, 2010 (edited) I am rather suddenly having an issue after almost 100 hours of play where as I approach a corpse the Courier appears to jump to the other side of the corpse. When I very slowly approach the corpse I get the notification it is there but cannot open it. Any ideas?- Update: after several minutes I can access corpses. When I am in the no-access condition I cannot use iron sights to aim or communicate with companion. Edited December 2, 2010 by Loden1111
Rabbit1251 Posted December 3, 2010 Posted December 3, 2010 Open your Pip Boy (nothing will happen) and then fire your weapon. Your Pip Boy will then open. Close your Pip Boy and you should be good until the next time this happens. And I thought that I was the only one having trouble with this. Rabbit
bushwackAR15 Posted December 3, 2010 Posted December 3, 2010 Open your Pip Boy (nothing will happen) and then fire your weapon. Your Pip Boy will then open. Close your Pip Boy and you should be good until the next time this happens. And I thought that I was the only one having trouble with this. Rabbit I've had the same thing happen, usually with a shotgun mod I'm running. I've never tried opening the Pip-Boy, but firing a shot seems to fix it for awhile.
Rabbit1251 Posted December 3, 2010 Posted December 3, 2010 If I try to fire nothing happens. But if I hit the 'TAB' key first firing will then open my Pip Boy instead. This glitch seems to happen only when I'm in combat. Multiple combats will mean that I have to keep repeating the process. Rabbit
Loden1111 Posted December 4, 2010 Author Posted December 4, 2010 Thanks. It works. Hit tab, pull the trigger, and the pop-boy opens then full functionality until it happens again. It is a bit of a rush when a Deathclaw is slashing at you, but at least the pip boy opening halts the time flow. You saved me from my next step which was to uninstall, reinstall and start over which would have been a real bummer!
thc1234 Posted December 5, 2010 Posted December 5, 2010 This happened to me as well, D3D performance "fix" was at fault for me.
Recommended Posts