Skyrim known issues, A list of known engine bugs and remedies Options

[Thomas Kaira]

Feel free to add to this if you want. So far, I can confirm a couple known issues here.

PC Issues

PC 1. Skyrim was not designed to be played with V-Sync off, and as such framerates beyond 60 FPS can cause major physics bugs and flashing water (accompanied by severe slowdowns). If you wish to not use V-Sync, you will need to limit your FPS using the FPS Capper tool.

ADDENDUM: It has also been confirmed that disabling V-Sync in the game using the iPresentInterval=0 tweak will cause the game calendar to gradually become De-synchronized with the clock, resulting in day turnovers at gradually later and later times. I have checked and it appears that 10 AM is when today becomes tomorrow in my game, and that can cause severe problems for AI schedules relying on a certain day. This cannot be fixed or worked around in any way.

PC 2. Skyrim has an audio bug, and often crashes if you have your audio setting too high. So you have to reduce your computer's sound quality to fix this:

In Windows 7:
Go to Control Panel > Hardware and Sound > Sound
You will see your default sound device. Click it, then click properties.
Go to the Advanced Tab, make sure the default format is set to 44.1Khz 16-bit.
Hit Apply/OK, then run Skyrim.

In Windows Vista:
Go to Control Panel > Sound
Find your default sound device (the one that is checked). Click it, then click properties.
Go to the Advanced Tab, make sure the default format is set to 44.1Khz 16-bit.
Hit Apply/OK, then run Skyrim

PS3 Issues

PS3 1. After approximately 20 to 30 hours of gameplay (to be more precise, once your savegame file size eclipses 6Mb), the game's framerates in exterior environments will drop significantly. There is currently no fix for this, Bethesda will need to address this one themselves.

Xbox 360 Issues

XBX 1. Installing the game to your hard drive introduces a bug where a large number of textures are not scaled properly, and appear at a lower resolution than they should. You can uninstall the game from your drive and play off the disc to prevent this. Patch is pending.

This post has been edited by Thomas Kaira: Nov 20 2011, 04:13 AM

[mALX]

I'm putting this issue to you, Master Chef TK - because if anyone can research it and find the truth of the matter out - you have proven yourself the master at it.


Does anyone know if the inability to re-charge the enchantments on Valdr's Lucky Dagger and Keening are a bug/glitch or do they work without being charged?

Valdr's Lucky Dagger appeared like any unchanted weapon when I first got it, and as a matter of fact I was able to improve it without having the "Arcane Blacksmith" perk. After I improved it, suddenly it showed with a "25% critical hit chance" enchantment, but the charge was at zero. While I have been able to recharge other weapons with no problems, there is no way to re-charge Valdr's Lucky Dagger. I have heard Keening is the same way.

When you try to use them they give the message "This weapon doesn't have enough charge" - so are we getting the benefit from their enchantments or not? Are these weapons bugged?

By the way, my game is still pre-patch.

[Thomas Kaira]

<snip>

I'll need to find those weapons first before I can do any troubleshooting. Please don't tell me, though, I'm still a player and would prefer not to have things spoiled. I'm on 1.3, but it won't matter because none of the current updates have provided a single ESM update.

But I do have another one:

You know those dragons that spawn at word walls? Turns out if you kill them once, every time afterwards when they respawn, they are soulless. You can only obtain souls from dragons spawned in fixed locations once. On 1.3. So 1.2 did not actually fix this.

There's the culprit for people who are not receiving souls from dragons they killed. That means it likely spawned in to replace a word wall guardian dragon you already killed.

Before going on, when I posted this on the official boards, I got several posts essentially telling me "not a bug, it's a feature," saying this was done on purpose to prevent soul farming. For that, let me ask you one thing: if you wanted to keep people from soul-farming those dragons, wouldn't it make much more sense just to have them not respawn at all? Instead of causing the game to behave anomalously and make people think the dragons are breaking as every single other player in the world would think when this happened to them?

As for if the dragon is force-respawned for a Radiant Quest, I do not think it very fair to instruct the player fight a dragon and rob him of his dragon soul when the battle ends because the dragon he was sent to kill had already been dealt with once.

[Grits]

You know those dragons that spawn at word walls? Turns out if you kill them once, every time afterwards when they respawn, they are soulless. You can only obtain souls from dragons spawned in fixed locations once. On 1.3. So 1.2 did not actually fix this.

Oh, I'm glad you brought this up. You saved me some swearing the next time I encounter an empty dragon. I'm with you, I don't think that's a feature.

My game freezing dragon got fixed. Bring on the late nights!