I have gotten a strange problem in IL-2 that I have failed to fix. I’m not sure if it started when I installed TIR5 or if it came with installing ATI driver 9.12.
But for whatever reason, IL-2 no longer accept input from the keyboard while in flight (or playing a track). It works at the, eh, first screen.
I can still Alt-Tab etc, so kb is working, and is not totally disabled, but no of the in-game commands work, neither does Esc or Shift-Tab (opening console). Keys mapped on HOTAS doesn’t work either.
The analogue part of the joystick works like normal, so it’s possible to fly, but not properly of course.
What I have done so far: uninstalled 9.12 and gone back to 9.10 (got text corruptions in-flight at the beginning of a flight or showing of a track), all traces of 9.12 is removed, so that is not the reason now at least.
I haven’t touched TIR so far, perhaps I should?
Yes, USB keyboard, but it works in other games, and it did work in IL-2 at the beginning, and no problems in ARMA II. Joystick is also USB, and as I said, the analogue part of it works as it should.
Installing Java runtime sounds like a plan, will try that!
There is a setting in BIOS, that tells the system that it is a USB-keyboard. Is that on? If not, you cannot press del to get into the BIOS. Maybe you can try an old PS2 keyboard and see what happens?
On the same machine Catalyst SB driver 9.10 and 9.11
Connect the PS/2 keyboard to your motherboard
Start Vista or Seven (you should use start key, tab etc. to select options in this guide) in normal mode (SAFE MODE not required).
Launch Catalyst 9.11 SB setup and select uninstall.
From the list check USB Filter driver, choose next and uninstall the driver.
A restart maybe required.
Start Vista or Seven again in full mode.
Start Catalyst 9.10 SB Setup and install the whole package or just the USB Filter driver.
Shut down without restart to disconnet properly your PS2 keyboard.
Connect your usb mouse and keyboard.
Start your OS and enjoy!!! And hope that AMD will fix the SB package soon. I’m quite sure that this issue is not releated to a software bug; I think that something went wrong when coders made the final build for 9.11 SB package…probably the include some sort of test inf file or they missed to add a file that cause Windows to be unable to initialize USB hubs.
Interesting, this sounds like it could be related for sure!
I’m pretty sure it started with the installation of 9.12. Then again, it does sound like those who ran into this problem had it at desk as well?
And I have uninstalled 9.12 and used drive cleaner to get totally rid of it before installing 9.10.
Will look into it further…
Only had a USB-kb at home, didn’t make any difference.
I did notice one thing in TIR though, I’m unable to change a button for doing different things. Tried remapping the button that puts TIR in precision mode, and that simply doesn’t work. Hmm, related?
IL-2 no longer accept input from the keyboard while in flight (or playing a track). It works at the, eh, first screen.
It sounds as if your Il-2 (I forget, technical name for window) is losing focus Mikke
There are commands in conf.ini regarding focus, maybe play with them
But first try running Il-2 in a (big maybe) window. That will force Windows to see your input keys, mouse etc as commands intended for the Il-2-window-frame. In case Il-2 cannot find focus for input commands
I forget the- no wait - surface that’s the word
Il-2 full screen depends upon Windows knowing that the Il-2 screen is a D3D surface. When you said that Il-2 sees the first screen, this may be a clue: this is maybe where Il-2 switches from DirectDraw (2D surface/window) - intoa ‘genuine’ Direct3D surface/window - and this may be where your Il-2 surface loses focus (the window can ‘feel’ your mouse clicks/TIR input and stick input
tried running IL-2 on DirectX, no difference
Maybe go to the Microsoft site and download the latest DirectX runtimes and install them. Or install RoF which will update your DirectX (DirectInput) files, a DirectX file may be broken. Please do this even if you know you did it already, the MagicTwoTimes feature, where sometimes an install must be repeated or the installer messes up (and any computer responds to the old magic)
Thinking on it, delete all the files in all your Temporary folders each time before you install something new. Installs can go bad if they use your Temp(orary) folders when installing
Hmm, related?
Sounds like yes mate. Something fundamental and possibly elemental is at work. Did you go to church last week. We may need to exorcise your machine
A friend lent me his Terminator:The Sarah Connor Chronicles season this last week, I’ve been enjoying it. But now I suspect all machines
Ming
I am in need of a lube job human
And I will give you a magic lamp
Or possibly magic beans
If you will get me a can of WD-40
But first try running Il-2 in a (big maybe) window. That will force Windows to see your input keys, mouse etc as commands intended for the Il-2-window-frame. In case Il-2 cannot find focus for input commands
Tested, no difference.
When you said that Il-2 sees the first screen, this may be a clue: this is maybe where Il-2 switches from DirectDraw (2D surface/window) - intoa ‘genuine’ Direct3D surface/window - and this may be where your Il-2 surface loses focus (the window can ‘feel’ your mouse clicks/TIR input and stick input
Yes, it seems the problem comes when it goes from 2D to 3D in IL-2.
Maybe go to the Microsoft site and download the latest DirectX runtimes and install them.
Tested, no difference.
Thinking on it, delete all the files in all your Temporary folders each time before you install something new. Installs can go bad if they use your Temp(orary) folders when installing
Good suggestion, will clean them out before installing next time.
Ran dxdiag, both in 32-bit and 64-bit, no problems found.
ETA: Have (re)installed 4.09m patch, didn’t make any difference.
Just came home from work, booted PC, decided to try IL-2 before I started to prepare to reinstall Windows 7 from scratch, and what do you know, now it works!
I haven’t started TIR and Cougar CC yet, but I will try that and see if things still work (hope it does!).
Only thing I think I had done but not rebooted before I tried IL-2 was unplugging the USB-TV thingy, I hope that was it.
Everything working perfectly now, including with TIR ans CCC on!
Must have been the PCTV DVB-T stick. It have a built in IR reciever for the little remote, must be that one that disabled all other input when in 3D-mode.
As to drivers, I am now on Catalyst 9.12 Hotfix, with the atioglxx.dll from 9.10 installed in the IL-2 folder. Seems to work fine.
