Game goes straight to fly again screen

[naubusan]

When starting a mission or campaign normal loading screens occurs, but then loading bar doesn't come and game goes straight to the fly again screen. Sometimes everything working just fine, but 9/10 times this is happening.

I have reinstalled game and Gpu drivers several times..

When I First installed game it worked well but then suddenly it started to do this. I don't know what have happened.

 

I have Intel E8200 cpu, 2048RAM, Ati 1950XT512

 

Right now have ati 8.12 drivers, but I have tried all 9.xx drivers too. Disabling or enabling Catalyst AI doesn't change a thing.

 

Crash file:

# -------------- 20090603-171651 --------------

C:\WINDOWS\system32\DINPUT8.dll

# C0000005 ACCESS_VIOLATION at 6CE25738 01:00014738

#

# EAX = 00050202

# EBX = 00199AE8

# ECX = 00000502

# EDX = 001A8DD0

# ESI = 001947E0

# EDI = 0019E040

# CS:EIP = 001B:6CE25738

# SS:ESP = 0023:0012F0C0 EBP = 0012F11C

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

6CE25738 0012F11C 0001:00014738 C:\WINDOWS\system32\DINPUT8.dll DirectInput8Create()+7E12

6CE25738 0012F11C 0001:00014738 C:\WINDOWS\system32\DINPUT8.dll DirectInput8Create()+7E12

6CE26AB0 0012F134 0001:00015AB0 C:\WINDOWS\system32\DINPUT8.dll DirectInput8Create()+918A

6CE26C59 0012F178 0001:00015C59 C:\WINDOWS\system32\DINPUT8.dll DirectInput8Create()+9333

6CE2428F 0012F190 0001:0001328F C:\WINDOWS\system32\DINPUT8.dll DirectInput8Create()+6969

6CE1533E 0012F1B8 0001:0000433E C:\WINDOWS\system32\DINPUT8.dll

6CE1DBDA 0012F1D8 0001:0000CBDA C:\WINDOWS\system32\DINPUT8.dll DirectInput8Create()+2B4

6CE1DC57 0012F1F8 0001:0000CC57 C:\WINDOWS\system32\DINPUT8.dll DirectInput8Create()+331

02567480 7C3AC1D1 0001:00006480 C:\Program Files\Eagle Dynamics\Ka-50\bin\stable\NewInput.dll ??4ForceFeedback@@QAEAAV0@ABV0@@Z()+3240

56ADE87C 3CDC9CB8 0000:00000000

 

 

 

Error.log:

 

Error running Config/autoexec.cfg: cannot open Config/autoexec.cfg: No such file or directory

3.6.2009 20:16 V808201900

[Panzertard]

It seems to indicate issues with DirectInput - your input devices.

What input devices (mouse, keyboard, gear, software for it) do you have?

[naubusan]

Logitech g15 keyboard, microsoft sidewinder mouse and precision2 joystick.

Software: Logitech keyboard profiler.

 

Ok I try to troubleshoot these...

[EtherealN]

Microsoft Sidewinder mouse has a problem (it is incompatible with DirectInput). If you have another mouse, try that one.

 

There have also been some issues with the g15, but not quite as severe. My bet is that it will work once you switch out the Sidewinder mouse.

[Panzertard]

Sidewinder is the problem. It's having DirectX compatability issues that affects DCS:BS. Try using another mouse. :)

EDIT: Ethereal beat me to it ;)

[EtherealN]

Hah! I sniped you! :D

[Panzertard]

:chair:

[naubusan]

Thanks guys!

Actually it wasn't the mouse but the joystick. Funny that couple of weeks ago all worked well, but now suddenly it's not working..

Tried uninstall drivers, and another usb port, something more to test?

Ok now I have good reason to buy new proper one ;D

 

Any suggestions for all in one model?? I have a small desk :(

 

Edit: what that force feedback does in crash report I don't have one??

[naubusan]

Ok I found that if I plug off either mouse or joystick game works. So maybe the mouse is biggest problem. Probably game thinks I have two joystics?

 

But still wondering what have happened because I played many weeks with no problems and used same stick and mouse.

[EtherealN]

The problem in the case of the mouse is that there's an incompatibility with it and DirectInput, which is part of the standard DirectX suite. So nothing in DCS has changed, and there's nothing DCS can do about it - but any kind of stuff in windows might have aggravated the problem to the point where it causes those unrecoverable errors that kill the DCS.exe for you.

 

ED has on earlier reports gotten themselves those mice for testing, and have been in contact with Microsoft about it, and from that they have established that it's the mouse vs DirectInput that is the issue. For that reason it is pretty much entirely out of EDs hands - up to Microsoft to fix it, if they care.