Any fix for the hitching besides disconnecting BT controllers?

[Roland]

My first match, I might get 2 hitches, but the second match on it quickly becomes unplayable.
Those of us with disabilities can't necessarily sit at a desk and use keyboard and mouse, so some of us absolutely rely on wireless controllers for gaming. (Personally, I'm not even in the same room as my computer 80% of the time I'm using it)
I'm using the non-Steam version of the game, and Steam's Dualshock 4 controller support.

Oh also, my computer specs:
fx-8350 4.0GHz
16GB RAM
GTX 760
With most settings on like medium, my setup gets a minimum of 52fps and a max of like 103 or something like that. (figured I should include this, even though we know it isn't a performance thing)

Oh also I thought I should mention that every time there was a hitch there was a spike in Disk Reads in my performance monitor.
I find this extra odd, since the game is kept on it's own hard drive, separate from the OS, specifically to avoid things like this...

UPDATE:
So supposedly lowering the process priority and removing 1 core from the affinity fixes it.
I've set the priority to Low via the registry, but i'm at a loss for setting Affinity.

Using a bat file to set it only sets it momentarily; it changes back before the game fully launches.
Ideally I'd like to set the Affinity through the registry so it's a "set it and forget it" deal and I could combine it with the other entry for the priority, but I'll take what I can get right now...

[Roland]

updated first entry

[UbiBaron]

I believe with the Affinity, you may need to change that when the game is running. Have you tried that and did it stick when you did this? It may reset when the app is closed and Re-opened.

- Ubisoft Support

[Roland]

Originally posted by UbiBaron:

I believe with the Affinity, you may need to change that when the game is running. Have you tried that and did it stick when you did this? It may reset when the app is closed and Re-opened.

- Ubisoft Support

Hi thanks for your reply, I actually solved my hitching issue by not using Steam's big picture mode to launch the game, while also using a registry entry to set the game's process priority to low.
For some reason, even though I am using the non-Steam version of the game, Steam's big picture mode (which I use for controller support and to hit up my Steam friends to join me sometimes) caused hitching in both this and my Steam version of FFXV. The latter is what led me to the solution, and I may use as an excuse to contact Steam about this.
Both games run perfectly with Steam's normal overlay and I only get hitching with the Big Picture Overlay.

To answer your question (and I'm slightly surprised you don't know this) you can't change priority or affinity while it is running because of the anti-cheat protection. That's why I was looking for backdoor methods or ways to set it before launch.
But it turns out it wasn't necessary and Steam just needs to clean up their Big Picture code.

I might try changing the priority back to Normal to see if it was just BPM or if setting the process to low did help as well.
I think it might have just been BPM though since every hitch was a spike in disk reads

[UbiBaron]

Thanks for the information, unfortunately I've not had to do this myself and so I was unclear on how that worked. I probably should have taken a more in-depth look into it first, so apologies for that.

I'm glad to hear that you were able to work out the reason for this occurring.

- Ubisoft Support