Holding keys (specifically WASD)

Follow

Anthony W Lowery

February 06, 2019 21:27

When I use Jump to connect from my iPad Pro to my Windows desktop everything works quite well with one exception, I cannot hold keys down in a game. Which means of course you cant move. I've tried every setting, soft keyboard, BT keyboard, nothing works. The odd thing is that if I bring up my Windows On Screen keyboard it shows that button holds are being communicated, the keys highlight and stay that was as long as I'm holding the key (letter keys excluded). 

It'd clear that both keyboard methods communicate the key is held down, then why doesn't it register in the game? DirectInput maybe, games API?

Thanks!

0

• 

  Jump Desktop Support February 07, 2019 15:11

  Hi, 

  Can you tell me a little more about this: Which games are you having trouble with. Also, which protocol are you using to connect to the remote Windows machine?

   

  Thanks.

  0

  Comment actions Permalink
• 

  Anthony W Lowery February 07, 2019 16:53

  Sure thing, I dont know if this will help but I tried 2 games and had slightly different results. 

   

  Paladins: WASD was not registered at all, no visible movement

  Overwatch: I couldnt move with key holds but If I tapped as fast as I could I could see a visible nudge, as though the key was pressed for just the briefest moment. So rapid taps will barely move you.

  I am using the Fluid Desktop. 
  
  Thanks for the quick response!

  0

  Comment actions Permalink
• 

  Jump Desktop Support February 07, 2019 17:05 (Edited February 07, 2019 17:05)

  Hi:

  1. We know the on-screen iPad QWERTY keyboard does not correctly send button information to the remote (it only sends us text vs actual key presses). 

  2. Can you try the arrow keys on the bluetooth keyboard or in Jump's '123' keyboard. Do they work correctly? Let me know if it does - this will help us. We might need to end up showing a custom control for WASD keys I suspect.

  Thanks.

  0

  Comment actions Permalink
• 

  Anthony W Lowery February 07, 2019 17:21

  They do not work, I tried everything I could find, even RDP and VNC protocols. The 123 or BT arrows wont work. 

  The on screen WASD would be helpful, but given the way that the input is sent, does that mean movement via a bluetooth keyboard is not possible?

   

  Thanks again.

  0

  Comment actions Permalink
• 

  Jump Desktop Support February 07, 2019 17:37

  Anthony: Bluetooth over FLUID should have worked. We're going to investigate this and get back to you.

  0

  Comment actions Permalink
• 

  Anthony W Lowery February 07, 2019 17:47

  I didnt want to waste your time I double checked. I didnt have the arrows mapped as alternate controls, whoops. So I mapped them and it turns out it DOES work! It's not as useful as WASD but at least it does work. Is there any way to get the same function from WASD?

   

  Thanks again for all of your help!

  0

  Comment actions Permalink
• 

  Jump Desktop Support February 07, 2019 17:57

  Thanks for double checking. Let me look into why WASD isn't working.

  0

  Comment actions Permalink
• 

  Liz Vincent February 09, 2019 22:31

  Just as an fyi I also am having this problem. keyboard works fine using arrow keys (detects the hold of the button) but WASD key holds are not detected. Would also be interested in having this fixed. Thanks! 

  1

  Comment actions Permalink
• 

  Michael Filliater February 10, 2019 17:48 (Edited February 11, 2019 00:39)

  I am experiencing this issue as well but I believe this is an issue with ios. For instance ensure key repeat is on and just go into a note app and you will see that pressing and holding the '.' key will repeat and so will arrows. But any letter keys do not.

  So I think it would require apple support

  EdIt: I use a physical keyboard attached to the folio case. Also want to add WASD is sometimes needed over arrow keys based on location to other keys

  1

  Comment actions Permalink
• 

  Jump Desktop Support February 21, 2019 20:11

  Hi guys,

  We're beta testing a fix for this right now (on all platforms). If you're interested we'd love to have you test the fix. Shoot us an email: support@jumpdesktop.com and let us know which platform you're interested to test on.

  Quick Note: Fluid connections will also require the new Jump Desktop Connect beta to be installed on your remote machine (6.2.23+): To get the Jump Desktop Connect beta open up Jump Desktop Connect -> Settings -> Updates and make sure 'Beta updates' is checked. Then click 'Check for updates'. At the time of this writing the latest beta Jump Desktop Connect beta is 6.2.22 but we're going to be releasing 6.2.23 very shortly (ETA 24 hours from now). 

   

  1

  Comment actions Permalink

Please sign in to leave a comment.