Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tomhighway]

Howdy,

First, I'll explain my issue, and then I'll post some information that will hopefully help others to help me.
 
The game will load and function normally to start with. But sometimes, not always, when I load up a mission through either the "career" mode, or the "QMB" mode, once the mission loads and you are in the cockpit, my keyboard does not respond. The mouse and the joystick function normally. You can fly the plane and all axis and buttons on the joystick function normally, but it's as if the game doesn't recognize that the keyboard exists. None of the keys mapped to a game function will do anything, including the escape key. I can use the "windows" key to get out of the situation as talked about below.

This issue only happens on my 2 modded versions of the game, VP Modpack, and YPack. The 2 stock versions that I play, IL-2 1946 4.12.2, and IL-2 1946 4.13.4, don't have this issue.

Has anyone else experienced this same issue, and was there ever a real solution found for it?

I've done a search with multiple "subjects", and I came up with only one thread where someone else posted about a "similar" problem.

https://www.sas1946.com/main/index.php/topic,9071.0.html

Although that problem has been marked as "solved", there was no actual solution to the issue. There was just a work-around that would get you past the issue so you could play the game. That work-around also works for my issue, even though I sometimes have to cycle through it several times before it works.

Here is some technical information.

VP Modpack: Selector version 3.1.1   Modactivator 5.30  (game version 4.12.2)
YPack:           Selector version 3.1.4   Modactivator 6.40  (game version 4.13.4)
I have no other mods installed.

Computer info:
Dell Precision 490 workstation.
2 dual core Intel Xeon 5160 CPU's @ 3.00 GHz.
8 gigabytes of RAM.
Silent Cell GV-N98TSL-1GI  video card.
500 gigabyte SSD hard drive.
Linux Mint 19.2 Xfce 64 bit operating system.
Wine version 4.0 bionic.
Running at 1920 x 1080 resolution on the desktop, and in the game.

Here is a link to how I solved the issue of getting VP Modpack and YPack to work on my Linux OS, in case that's relevant.

https://www.sas1946.com/main/index.php/topic,67889.0.html

Any help would be greatly appreciated.

[Epervier]

This issue only happens on my 2 modded versions of the game, VP Modpack, and YPack. The 2 stock versions that I play, IL-2 1946 4.12.2, and IL-2 1946 4.13.4, don't have this issue.

Then everything is perfect! 
The YPack is not supported on this site!
The VP pack is present here but its author is no longer here!
The 4.13 version has no interest!
So everything is fine!

[SAS~Storebror]

Douple-tap the "Alt" key, then douple-tap the "Tab" key.
Fixed.


Mike

[tomhighway]

Douple-tap the "Alt" key, then douple-tap the "Tab" key.
Fixed.


Mike

Nope.

[ZtheE]

Alt + Tab

[tomhighway]

Douple-tap the "Alt" key, then douple-tap the "Tab" key.
Fixed.


Mike

Alt + Tab

These are not "solutions" to the problem. They are workarounds to get you through the present gaming session.  A solution is when you figure out what is causing the problem, and then make whatever changes are necessary to keep the problem from reoccurring.

The "workarounds" are better than nothing, and of course I use one, (neither one of these, by the way), to be able to play the game. However, the question I posed in the original post was whether or not anyone has ever found an actual "solution" to this known problem.

[ZtheE]

Provide a log or we can't help

[SAS~Storebror]

These are not "solutions" to the problem. They are workarounds to get you through the present gaming session. A solution is when you figure out what is causing the problem, and then make whatever changes are necessary to keep the problem from reoccurring.

So you don't want no help.

The "workarounds" are better than nothing, and of course I use one, (neither one of these, by the way)

And you don't want to help others.
Welcome to my personal ignore list.


Mike

[tomhighway]

These are not "solutions" to the problem. They are workarounds to get you through the present gaming session. A solution is when you figure out what is causing the problem, and then make whatever changes are necessary to keep the problem from reoccurring.

So you don't want no help.

The "workarounds" are better than nothing, and of course I use one, (neither one of these, by the way)

And you don't want to help others.
Welcome to my personal ignore list.


Mike

That's a little unfair, Mike. I have posted helpful information on these forums, which I provided a link to in my original post. And the only "workaround" that seems to get me past the keyboard lockup was given by someone else in one of the links I posted above. Left click on the mouse, hit the "windows" key, left click on the mouse again. Sometimes I have to repeat the process several times before it works, but it does end up working.

If it wasn't clear in my previous post, I do appreciate the "workarounds", but it wasn't what I asked for. I asked if anyone else has had this specific problem, and if there is a real "solution" to it. If not, that's ok, but I'd like to know.

[tomhighway]

Provide a log or we can't help

Thanks. I'll give that a try.

[agracier]

If it wasn't clear in my previous post, I do appreciate the "workarounds", but it wasn't what I asked for. I asked if anyone else has had this specific problem, and if there is a real "solution" to it. If not, that's ok, but I'd like to know.

Every now and then after starting up BAT, my keyboard doesn't seem to do anything, the game will simply not respond to keyboard input. Even when building FMB missions, I cannot place an aircraft or other object on the map. My mouse works fine but when keyboard input is needed (as in using ctr+mouseclick to place an object, the keyboard seems to have been rendered inoperable.

I have not found any solution to this, but a reboot of the game fixes the problem.

In any case, you are not the only one this happens to.

[tomhighway]

If it wasn't clear in my previous post, I do appreciate the "workarounds", but it wasn't what I asked for. I asked if anyone else has had this specific problem, and if there is a real "solution" to it. If not, that's ok, but I'd like to know.

Every now and then after starting up BAT, my keyboard doesn't seem to do anything, the game will simply not respond to keyboard input. Even when building FMB missions, I cannot place an aircraft or other object on the map. My mouse works fine but when keyboard input is needed (as in using ctr+mouseclick to place an object, the keyboard seems to have been rendered inoperable.

I have not found any solution to this, but a reboot of the game fixes the problem.

In any case, you are not the only one this happens to.

Thanks. At least I know I'm not the only one.  ;^)