HOTAS analog inputs stop working if PC is busy (possible vJoy problem?)

Recently I've been having problems with my analag HOTAS inputs to Elite: Dangerous. I use a Thrustmaster Hotas 4 and recently got a brand new one. I use the Joystick Curves utility which allows response curves to be programmed. I believe Joystick Curves uses the vJoy driver to map its "curved" output responses to virtual joystick inputs which is what are then bound to ED controls.

What I'm finding is that sometimes, when I've just started things up (and certain background tasks are using quite a lot of CPU), in-game the analog controls (pitch, roll and yaw) are almost entirely unresponsive. However, if I Alt+Tab back to my desktop and look at either the Windows USB game controller properties window or the Joystick Curves interface itself, everything seems to be fine and responsive, but as soon as I Alt+Tab back into the game ... nothing.

Usually this sorts itself out after a while (10 mins maybe) ... I put that down mostly to startup background tasks settling down.

Last night when I was on the Frontier livestream it happened worse than ever. It had been fine earlier but, with video and livestream chat running in Discord and various websites open plus quite a lot of multiplayer in-game activity too, I was again back to my controls being almost entirely unresponsive, with them very occasionally working sporadically for the odd minute or two.

My hunch is a software problem, possibly vJoy failing to communicate the virtual inputs to Elite.

Anyone got any thoughts on this because it's potentially a game breaker and I'm not sure what to do about it.
 
Last edited:
It's an i5 4690k. So it's an older CPU for sure but it used to be fine, not quite sure what's changed.

Hmmm, I wonder if an AVG virus checker update has caused problems? (I can try disabling it just to rule that out)

Also, I seem to recall reading something about changing CPU process priorities - I wonder if I can give the vJoy driver a higher priority?
 
You can create a list of exceptions in your virus checker, and Windows defender (if that’s running) This will prevent them from periodically agitating those specific programs you wish to be left alone.
Also, in Windows settings check the start up list and disable programs that do not need to booting up immediately.
And finally, in Windows power settings. disable the ‘quick start/boot’ option as when this is enabled Windows can miss/not activate things when starting up.
ping me if you require further info. :)
i run the same vjoy utility and all is well. No need to mess with priorities in task master.

Flimley

oh yes, one last thing, in device manager check your USB ports and make sure they are powered continuously.
 
Last edited:
Follow-up to this issue.

I've continued with my suspicions that the problem is actually down to joystickcurves.exe missing out on CPU cycles when the CPU is heavily loaded.

Yesterday I decided to go and rescue some folks from the burning station (a notoriously CPU/GPU intensive area). Anyway, as soon as I'm through the mailslot I lose ALL my joystick axes - pitch, roll and yaw - absolute disaster (luckily I manage to wait out the 15 second timer and log out before I'm burned to a crisp).

On a hunch I then set CPU priority for joystickcurves.exe to Above Normal and try again.

That seems to fix it.

So what the hell? Elite Dangerous seems to be using so much CPU these days (I'm sure that didn't used to be the case) that other processes like joystickcurves.exe aren't getting a look in. Surely with 4 cores there's scope for EliteDangerous to hog two of them and still leave scope for a virtual joystick emulator to do its thing?
 
Back
Top Bottom