Xbox one bugs after 1.3

[Echo]

Now bear in mind, I may be an exception for experiencing as many bugs since 1.3 on Xbox; however, I will list all I have experienced. I will also include bugs from other players I know on console.

•Unable to perform ripostes with one handed weapons.
•Not experiencing any encounters on any road such as wayfarers or bandits.
•Screen stutters horribly when locked onto opponent.
•Unable to complete bandit camp clearing quest if you stumble into them and kill them before you were meant to.
•Npcs leaving persistent items on the ground in towns.(brooms and polearms everywhere!)
•Stuttering occasionally on horseback, but mostly in towns.

These are just the bugs I have encountered or have seen recordings of for console. I reinstalled, made new playthroughs, but to no avail. On a side note, I can’t seem to get the treasures of the past content to appear in the game. Will there be a patch to fix this in the future?

[Humannoyed]

I started a new playthrough after 1.3 came out, oddly I didn’t experienced some of the bugs you are mentioning here.
Riposte was working (I used long- and shortswords most of the time), encounters were about the same as in v1.0, and no stuttering while locked on.
This is baffling.
[edit]I can’t say anything 'bout the bandit camp-thingie, but the stuttering in towns was (occasionally) annoying.
(SPOILER)
The stuttering at the Talmberg-Camps (near end game) was utterly annoying for me. Strange thing was it didn’t stutter at all during the fight sequences in that location.

[GregMac32]

Speaking on my experience, patch 1.3 has destroyed the performance on my game. Every part of the game now has massive frame loss, stuttering & pop-in’s. Walking or riding through a town looks like Henry is moving through a strobe light. I bought the game about a week before patch 1.3 and it ran pretty smooth, but now I’m having a hard time playing. I’m playing on an Xbox One X which should be able to run this game smoothly. I’ve been searching online about this & I think it has something to do with Vsync-30 that was implemented with patch 1.3. But, I don’t know a lot about this stuff so I might be wrong. If anyone else has had this problem after the patch please let me know. I’m trying to find out if this is something I can fix myself, or if I have to wait for another patch.