Keyboard inputs
-
@alanfernandes It’s okay, I’m swedish, and english is also not my first language.
Basically, hit ‘enter’ and just type. But be quick. What you wrote before enter doesn’t matter.
I recorded a short clip with my phone in one hand and typed with the other.
Hopefully you see what happens.
@ploodovic said in Keyboard inputs:
@alanfernandes It’s okay, I’m swedish, and english is also not my first language.
Basically, hit ‘enter’ and just type. But be quick. What you wrote before enter doesn’t matter.
I recorded a short clip with my phone in one hand and typed with the other.
Hopefully you see what happens.
Thank you so much, my friend! I’ll test it as soon as possible, since it's already past 10 PM here in Brazil and I have to work tomorrow! Thanks for the assistance!
-
I just tested it, and there isn't actually a 'problem' on Xbox, but you have to be EXTREMELY fast for it to work. It goes like this:
• Click the mouse on the _ _ _ _ _ field.
• The 'KYBD' acronym appears.
• From that moment on, you have only a few seconds to type.I also noticed that as long as the 'KYBD' message (which I assume stands for Keyboard) is visible, no mouse clicks on the _ _ _ _ _ field are accepted.
To make it ideal, would it be possible to extend the duration of this keyboard function? For instance, if I have to type a custom waypoint (which is usually long), I have to type very fast. If you pause halfway through, it disables the function.
In short: I think that when clicking to enable the keyboard function, it should stay active for longer, and it could be disabled at any time just by clicking with the mouse again.It sounds a bit confusing, but tomorrow I'll try to record a video so you can better understand what I mean.
-
I just tested it, and there isn't actually a 'problem' on Xbox, but you have to be EXTREMELY fast for it to work. It goes like this:
• Click the mouse on the _ _ _ _ _ field.
• The 'KYBD' acronym appears.
• From that moment on, you have only a few seconds to type.I also noticed that as long as the 'KYBD' message (which I assume stands for Keyboard) is visible, no mouse clicks on the _ _ _ _ _ field are accepted.
To make it ideal, would it be possible to extend the duration of this keyboard function? For instance, if I have to type a custom waypoint (which is usually long), I have to type very fast. If you pause halfway through, it disables the function.
In short: I think that when clicking to enable the keyboard function, it should stay active for longer, and it could be disabled at any time just by clicking with the mouse again.It sounds a bit confusing, but tomorrow I'll try to record a video so you can better understand what I mean.
@alanfernandes Not confusing at all! I know exactly what you're talking about. The only thing I don't know is if the timeout is any shorter on Xbox than on PC, but I doubt that it is. Unfortunately, being locked out of other keyboard and mouse interactions while the keyboard entry is enabled just comes with the territory. That's why it has a timeout at all, since otherwise I would be getting complaints about how no mouse input works (including view panning), when all they had to do was click the screen again. If you want to check the timing, it should be five seconds from seeing KYBD to it disappearing.
-
@alanfernandes Not confusing at all! I know exactly what you're talking about. The only thing I don't know is if the timeout is any shorter on Xbox than on PC, but I doubt that it is. Unfortunately, being locked out of other keyboard and mouse interactions while the keyboard entry is enabled just comes with the territory. That's why it has a timeout at all, since otherwise I would be getting complaints about how no mouse input works (including view panning), when all they had to do was click the screen again. If you want to check the timing, it should be five seconds from seeing KYBD to it disappearing.
@Black-Square Thank you for your assistance. My apologies for the confusion regarding the system logic—I mistakenly thought it was a bug.
-
@Black-Square Thank you for your assistance. My apologies for the confusion regarding the system logic—I mistakenly thought it was a bug.
@alanfernandes No worries! I misidentify the behavior of my own software as bugs at least every few weeks. I just feel bad that I can't offer you a custom code solution, as I would for someone on PC. I have been criticized in the past for suggesting that my users edit the files on their own systems, but I believe that there is no reason anyone should be kept from a more enjoyable sim experience if I can offer an immediate solution that fits their needs.
