Weird kneeboard bug, forced to hard-reboot

[Flappie]

Hi, it's the second time that I experience such a bug with the Huey. Both times happened while flying in the Argo campaign, and trying to hide the kneeboard. Second time was during mission 10 (I can't recall the first time).

 

How to reproduce :

1. I load Argo campaign mission 10.

2. Once in the cockpit, I hit "RShift + K" to display the kneeboard.

3. I then press and hold RShift, and click some random buttons (e.g. Weapon Realease button). Once I hear a beep, I'm completely unable to interact with my keyboard.

 

 

Whenever I hit a key, I get a beep. "Pause", "Ctrl+Alt+Del", "Escape", nothing works. I'm unable to disable/enable the ShiftLock and NumLock lights of my keyboard. Still, my HOTAS, TrackIR, mouse, screen and sound keep working, thus allowing me to accomplish the mission. Once the mission is over, I have no other choice than to hard-reboot my PC. Hopefully, greg added a "Skip mission" option ! Kudos for that, greg. :thumbup:

 

I've just tested a Huey free flight mission, and I just can't reproduce the bug there. Has someone else already bumped on this bug?

 

 

EDIT: I was unable to reproduce this bug in mission 11.

Edited November 14, 2019 by Flappie
fixed

[petritis]

Hi, it's the second time that I experience such a bug with the Huey. Both times happened while flying in the Argo campaign, and trying to hide the kneeboard. Second time was during mission 10 (I can't recall the first time).

 

How to reproduce :

1. I load Argo campaign mission 10.

2. Once in the cockpit, I hit "RShift + K" to display the kneeboard.

3. I then press and hold RShift, and click some random buttons (e.g. Weapon Realease button). Once I hear a beep, I'm completely unable to interact with my keyboard.

 

 

Whenever I hit a key, I get a beep. "Pause", "Ctrl+Alt+Del", "Escape", nothing works. I'm unable to disable/enable the ShiftLock and NumLock lights of my keyboard. Still, my HOTAS, TrackIR, mouse, screen and sound keep working, thus allowing me to accomplish the mission. Once the mission is over, I have no other choice than to hard-reboot my PC. Hopefully, greg added a "Skip mission" option ! Kudos for that, greg. :thumbup:

 

I've just tested a Huey free flight mission, and I just can't reproduce the bug there. Has someone else already bumped on this bug?

 

 

EDIT: I was unable to reproduce this bug in mission 11.

 

This is indeed a really strange issue. As you describe it, it really looks like to me that you accidentally activate the "sticky keys". In order to check if this is the case, please disable sticky keys from windows settings and try if it happens again.

 

Also this doesn't seem to be a campaign or mission bug, since all missions where designed and implemented in the same way and didn't occur during testing to none of the testers or my self.

 

Thanks for sharing this issue, later in the day i will try to reproduce it and post the results.

[Flappie]

This is indeed a really strange issue. As you describe it, it really looks like to me that you accidentally activate the "sticky keys". In order to check if this is the case, please disable sticky keys from windows settings and try if it happens again.

That's what I thought at first. Then I tried to activate the "sticky keys" by hitting RShift multiple times from my Windows 10 desktop, but the "sticky keys" message didn't show up. Anyway, I'll come back here to confirm that this function is effectively disabled in the Windows parameters.

 

 

By the way, the "beeps" that I hear whenever I bump on the bug are not issued by the motherboard speaker, they are real sounds coming from my headphones.

 

 

Thank you for considering this issue.

[petritis]

That's what I thought at first. Then I tried to activate the "sticky keys" by hitting RShift multiple times from my Windows 10 desktop, but the "sticky keys" message didn't show up. Anyway, I'll come back here to confirm that this function is effectively disabled in the Windows parameters.

 

 

By the way, the "beeps" that I hear whenever I bump on the bug are not issued by the motherboard speaker, they are real sounds coming from my headphones.

 

 

Thank you for considering this issue.

 

So i tried to recreate the problem you describe, in the exact same way based on your description but had no luck.

[Flappie]

Thank you for your time.

 

I've just looked at my "sticky keys" parameters. They were already disabled, but two "shortcuts" were still active: one tied to NumLock/ShiftLock and this other one, tied to RShift.

 

 

 

I'll let you know if I still get the issue.

[Flappie]

It seems it did the trick: I've just finished the campaign and I haven't had this issue anymore.