» Fri Dec 16, 2011 8:38 am
There's a similar problem if you're an Archer as well: if you have the daggers out, swap to the bow (I keep both on the Favorites menu, for obvious reasons), and then attempt to swap back to the daggers, it will ignore you as it has dropped the daggers' hot-key assignment. To add insult to injury, so to speak, they're still on the Favorites list.
It does not always do this, but it happens often enough to be really irritating. Where it does always happen is when you equip a spell not on your Favorites list, such as Transmute; this auto-drops the left-hand dagger from the listing and you have to put it back manually. Fortunately for me I don't use the daggers all that often as I play Archer-primary, but when I do want them, such as when getting jumped in the wilderness, it gets annoying having to re-key them. I also ran into the 'improved item' variant, although in my case it was exacerbated by the fact I had 6 of them so improved which rendered it unable to determine which two I was actually using (they're not enchanted).
I can't offer any real solutions to this aside from the usual re-equipping advice, but I can shed some light on why it's happening in the first place.
1) Every item has a unique Ref ID#, which never changes and is used by the game to differentiate between items; this number is what allows multiple copies of the same item to stack in the inventory screen
2) When you alter an item, it is assigned a different, game-specific number as it is considered a new item; this is done for each and every altered item
3) Each degree of alteration, whether that be smithing level or enchantment strength, is a separate category, and items are sorted in inventory accordingly; these can stack, but usually don't due to 2), above
4) Each hot-key may only have one item assigned to it; there is a built-in exception for dual-wielding two of the same item
Because the game's sorting engine does not consider two altered copies of the same item to be identical, they do not qualify for the exception in #4 and thus get tossed from the hot-key assignment. I don't know why re-equipping them makes them qualify to be hot-keyed again, but if I had to guess it would be due to a loophole in the exception code.