lost song issau controller problem

[∆∆°BlueΠExtreme°∆∆]

Sorry for my bad english but i have a problem, i have lost song and ps4 controller go well,but i prefere xbox one controller for this game,now it work but when i fly fast kirito fly slowly left, it happen only with one controller? Can anyone confirm that or give me a fix, i alredy try with 2 controller is a problem to the game,help please?

[NormireX]

Not sure on your issue, but I am using an Xbox One controller but the game keeps switching to mouse/keyboard and back to controller. LIke it stutters between mbk and Controller and I had both my keyboard and mouse turned off (they are wireless).

[Raedeon Alexsis]

Im using an Xbox One controller and having the same issue.

[Quixadhal]

Yep, same issue in 2020... like clockwork, if you hold down the RB when facing something interactable, you'll see the prompt switch to the keyboard "E" for an instant before registering the controller input and going back to "B" again... like clockwork, every second on the second.

I'm going to guess it's another example of bad console port code, where something is polling the DirectX input streams rather than waiting for events to fire.

[EDIT] What's really odd is that this game worked smoothly and flawlessly (for me) before the latest Windows Update patch. At that point, after rebooting for it, it started doing this. It makes it impossible to hold a block in combat, and also makes running or flying quickly annoying. I have tried reverting the update and reapplying it, as well as swapping to a wired controller with no effect.

To me, it almost feels like the order of the devices got changed and it now has to poll past the keyboard briefly....

[EDIT 2] So, I solved the problem. Windows Update didn't break this game directly, but rather it broke another program (Process Explorer from sysinternals) which in turn broke this game while running. Apparently something in the latest update must have changed the way privilege escalation is handled, as PE acquires exclusive locks on all threads to get their info, and this apparently prevents the game from polling the controller for an instant.

From the game's point of view, the controller disappeared, so it flips to keyboard/mouse just long enough to break input... and then it's back on the next frame again.

[Scrumbles]

Originally posted by Quixadhal:

Yep, same issue in 2020... like clockwork, if you hold down the RB when facing something interactable, you'll see the prompt switch to the keyboard "E" for an instant before registering the controller input and going back to "B" again... like clockwork, every second on the second.

I'm going to guess it's another example of bad console port code, where something is polling the DirectX input streams rather than waiting for events to fire.

[EDIT] What's really odd is that this game worked smoothly and flawlessly (for me) before the latest Windows Update patch. At that point, after rebooting for it, it started doing this. It makes it impossible to hold a block in combat, and also makes running or flying quickly annoying. I have tried reverting the update and reapplying it, as well as swapping to a wired controller with no effect.

To me, it almost feels like the order of the devices got changed and it now has to poll past the keyboard briefly....

[EDIT 2] So, I solved the problem. Windows Update didn't break this game directly, but rather it broke another program (Process Explorer from sysinternals) which in turn broke this game while running. Apparently something in the latest update must have changed the way privilege escalation is handled, as PE acquires exclusive locks on all threads to get their info, and this apparently prevents the game from polling the controller for an instant.

From the game's point of view, the controller disappeared, so it flips to keyboard/mouse just long enough to break input... and then it's back on the next frame again.

What did you adjust for Process Explorer? The same behavior is happening for me too.

[Quixadhal]

I stopped using it.

It's a thing with live display refresh and how it locks the processes to scan them. You could adjust the refresh rate so instead of updating every second, it updates every 30 seconds, but all that does is change the stuttering.

The "fix" would be to get the folks at System Internals to change how their tool handles scanning the process list, so it doesn't get exclusive locks, or releases them much faster...

[FluffyXai]

Originally posted by Quixadhal:

I stopped using it.

It's a thing with live display refresh and how it locks the processes to scan them. You could adjust the refresh rate so instead of updating every second, it updates every 30 seconds, but all that does is change the stuttering.

The "fix" would be to get the folks at System Internals to change how their tool handles scanning the process list, so it doesn't get exclusive locks, or releases them much faster...

I'm sorry to bring up an old thread, I just got this game and I'm having this issue. What do you mean by stopped using it?
What exactly is process explorer and how do you stop using it? I tried looking around in my processes and services but couldn't see anything by that name.
I can't really sit up to use mouse and keyboard while playing games so I need to use a controller.

[Quixadhal]

process explorer is a third party tool that gives you a bit more in depth info about processes on your system, and what resources they're using. Unlike the built-in task manager, it keeps a short graph of process information active, so you can see what spiked the CPU a minute ago without having to catch it in the act.

In theory, any other tool that does the same kind of thing (gets exclusive locks on processes to interrogate them) might have a similar behavior. Anti-virus stuff comes to mind.

[FluffyXai]

Originally posted by Quixadhal:

process explorer is a third party tool that gives you a bit more in depth info about processes on your system, and what resources they're using. Unlike the built-in task manager, it keeps a short graph of process information active, so you can see what spiked the CPU a minute ago without having to catch it in the act.

In theory, any other tool that does the same kind of thing (gets exclusive locks on processes to interrogate them) might have a similar behavior. Anti-virus stuff comes to mind.

Oh that's informative
but I'm not sure what I might have that might be doing that? I don't think I have any programs that could be doing anything like that?
And upon looking into it I don't think I have process explorer either.