I cannot explore caves do to every single one of them being filled up with invisible flashing water causing me to swim around them in mid air and whenever I go to shoot my bow it flashes about 10000000000x and shoots about 20 arrows back to back not 1 inch infront of me. I can't even swing a one handed weapon either. I am 170 hours in and I have NEVER had ANY game breaking glitches until this one appeared out of nowhere. I just did a quest where there was a Giant in a cave and I had to backpeddle / swim backwards for 10 damn minutes around a rock just to be able to fire 4 arrows to kill the damn thing! No I did not recently change any settings or install any mods, it just came out of nowhere...

Wut?

Pass me some of that skooma, friend.

Upload it on youtube

Sounds like a nightmare. I would like to see a video of this.

You'll probably get more help if you post this on the bugs forum of the platform you're playing on.

First, I would have posted that in the Tech Support section.
Second, try this and see if that fixes your issue (for PC users)

Verify integrity of game cache

Load Steam
From the Library section, right-click on the game and select Properties from the menu.
Select the Local files tab and click the Verify integrity of game cache... button.
Steam will verify the game's files - this process may take several minutes.
Once the process is completed, the Check Window will automatically exit.

Someone has been drinking too much mead, recently...

The underwater problem was recently reported in the Unofficial Buglist thread, though I've yet to hear about the bow problem.

The belief is that the underwater problem one of the many issues with V-Sync. Do you have V-Sync enabled? Try disabling it and see if the problem persists.

Dude ... you just blew my mind !

Hi,

I can confirm some similar behaviour with arrows... just after starting the game and loading a previous save, bows can perform short shots for a little while.
Things generally return back to normal by switching weapon or after a while (should test more closely next time, observing when the problem resolves). From then on, bows behave correctly. I'm playing in 1st person mode only.

This minor glitch happens on an unmodified (no ini, no mods, no modifications from nvidia panel, no exe mods or unofficial patches) 1.3 on XP.
Note i'm not suffering from any ctds or performance/system issues and that the game is fully playable atm (no major bugs found even if i'm still lvl26 - save game is around 7mb).

People who modify the program before the CK comes out should lose all rights to complain about stuff like this. After the CK comes out, they should complain to the person RESPONSIBLE for their problems... ie themselves. This is not Bethesda's problem.

I'll record a video here soon and upload it. The bow problem i described is tied with the water problem, the game keeps thinking im underwater then out of water then under again then out again ect ect like a couple times a second and the bow keeps disappearing and reappearing rapidly due to detecting Im in/out of water. It in fact does it so fast that it doesn't stop the arrow from drawing or shooting and thus shoots arrow after arrow after arrow until u press R to put it away.

::EDIT::

Looks like you cannot record this problem as it only happens when I have around 150fps and using FRAPS brings my fps down to around 30 thus fixing the problem. Looks like to make it go away I need to enable v-sync but screw that, I get horrible mouse lag with v-sync on.

If you really don't want to put vsync back on, you can download and use an fps limiter.


Either that, or keep fraps recording video all the while..

It is clear that they designed the game around it never going above 60FPS. First the mouse issues, time of day issues, now this? I seem to recall a whole thread warning people to never turn off vsync. Can someone find it?

The issue is the presetinterval being OFF and/or v-sync... (For most people.)

The other issue is just save-game corruption, which is setting wrong data in the wrong slots... Dropping an item can break the whole game. Returning a quest item can break the game. Shooting an arrow can break the game. Anything that writes to the save-game data, is breaking the save games. However, even that is random, as to what breaks, or when it breaks. Half the "issues" are all the same issue... save game corruption, not actual quest bugs and AI glitches. Thus the "rare instance" in the mention of the patches.

Sounds like the water-level is changing instead of the light-flicker or fog-flowing... (Corruption) Fog is in layers... if every other layer believes it is water, you are swimming, then not, then swimming then not... until you get to a fog-free area. When you FIRE the bow, your mouse is DOWN, but the interruption of water happens 1000000x a second, thus, one click is treated as 10 shots, as it disables, then enables the bow and the FIRE button mouse is still down, for the next 10x frames. Buffered ON.

Bethesda should force that value ON since it is obviously NEEDED... even if we turn it off, it should ignore it... or force it to reset. Get on the ball... setup realistic MIN and MAX and DEFAULTS theat can't be changed in the INI. You know we are all editing it anyways, creating bugs that don't exist on other people's games. From the invalid values we are using. LOL

NOTE: Never type SAVEINI in the console, unless you can find that INI and DELETE IT once created... it breaks the game. It is NOT the games INI, it is fallout's INI.