Problem Starting BS v1.01 multiplayer

[sleepycanuck]

Hello All,

 

after installing 1.01 patch I can start and run single player without issue or problem ... like the new trimmer! :)

 

Unfortunately I am having lots of problems running the multiplayer module??? When ever I try and start multiplayer I usually get an error right away: "DCS has stopped working ... etc. "

I am running Vista 64. Below is my system info and the contents of the crash log. Thanks to all for any help.

 

System info:

 

OS Name Microsoft® Windows Vista™ Home Premium

Version 6.0.6002 Service Pack 2 Build 6002

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name SLEEPYCANUCK-PC

System Manufacturer MSI

System Model MS-7369

System Type x64-based PC

Processor AMD Athlon 64 X2 Dual Core Processor 6000+, 3013 Mhz, 2 Core(s), 2 Logical Processor(s)

BIOS Version/Date American Megatrends Inc. V2.1, 02/Aug/2007

SMBIOS Version 2.5

Windows Directory C:\Windows

System Directory C:\Windows\system32

Boot Device \Device\HarddiskVolume2

Locale United States

Hardware Abstraction Layer Version = "6.0.6002.18005"

User Name SleepyCanuck-PC\Sleepy Canuck

Time Zone Eastern Daylight Time

Installed Physical Memory (RAM) 4.00 GB

Total Physical Memory 4.00 GB

Available Physical Memory 2.70 GB

Total Virtual Memory 8.23 GB

Available Virtual Memory 6.67 GB

Page File Space 4.29 GB

Page File C:\pagefile.sys

 

crash file contents:

 

# -------------- 20090812-022917 --------------

C:\Windows\system32\DINPUT8.dll

# C0000005 ACCESS_VIOLATION at 75025B7B 01:00014B7B

#

# EAX = 00050202

# EBX = 00ACA3F0

# ECX = 00000502

# EDX = 00AD9BF8

# ESI = 00AA4F08

# EDI = 00003C18

# CS:EIP = 0023:75025B7B

# SS:ESP = 002B:0017EE64 EBP = 0017EEC4

# DS = 002B ES = 002B FS = 0053 GS = 002B

# Flags = 00010202

75025B7B 0017EEC4 0001:00014B7B C:\Windows\system32\DINPUT8.dll DirectInput8Create()+798F

75025B7B 0017EEC4 0001:00014B7B C:\Windows\system32\DINPUT8.dll DirectInput8Create()+798F

75027486 0017EEDC 0001:00016486 C:\Windows\system32\DINPUT8.dll DirectInput8Create()+929A

75027793 0017F158 0001:00016793 C:\Windows\system32\DINPUT8.dll DirectInput8Create()+95A7

750238BE 0017F170 0001:000128BE C:\Windows\system32\DINPUT8.dll DirectInput8Create()+56D2

75015BA9 0017F198 0001:00004BA9 C:\Windows\system32\DINPUT8.dll

7501E41C 0017F1B8 0001:0000D41C C:\Windows\system32\DINPUT8.dll DirectInput8Create()+230

7501E499 0017F1D8 0001:0000D499 C:\Windows\system32\DINPUT8.dll DirectInput8Create()+2AD

02387310 7C3AC1D1 0001:00006310 E:\DCS Black Shark\bin\stable\NewInput.dll ??4ForceFeedback@@QAEAAV0@ABV0@@Z()+3290

56ADE87C 7C3AC1D5 0000:00000000

EC83FFFF 7C3AC1D9 0000:00000000

57565314 7C3AC1DD 0000:00000000

FFF06589 7C3AC1E1 0000:00000000

DB330C75 7C3AC1E5 0000:00000000

E8EC5D89 7C3AC1E9 0000:00000000

00021507 7C3AC1ED 0001:00000507 E:\DCS Black Shark\bin\stable\lua.dll lua_rawequal()+7

8B08758B 7C3AC1F1 0000:00000000

8B068BF8 7C3AC1F5 0000:00000000

448B0440 7C3AC1F9 0000:00000000

C33B1830 7C3AC1FD 0000:00000000

3B087E59 7C3AC201 0000:00000000

2B047EC7 7C3AC205 0000:00000000

56D88BC7 7C3AC209 0000:00000000

E8E04D8D 7C3AC20D 0000:00000000

FFFF5DB8 7C3AC211 0000:00000000

00FC6583 7C3AC215 0001:000F5583 E:\DCS Black Shark\bin\stable\protect.dll

00E47D80 7C3AC219 0000:00000000

45C70C75 7C3AC21D 0000:00000000

[sleepycanuck]

MS Sidewinder Mouse: might be the problem

 

Hello All again,

 

After doing some more reading in the forums I found posts stating that users were having problems when a MS Sidewinder Mouse was attached.

 

I tested this theory by swapping the Sidewinder out with a Logitech G5 mouse and sure enough the game would launch in multi player without issue.

 

Once I went back to the MS Sidewinder the problems started again ... damb! ... I really like the sidewinder but I guess I will have to unplug it when flying the Black shark ... a small price to pay for such an awesome sim!

 

Cheers all.

[=SCoRPioN=]

I'm using an old MS Sidewinder Precision Pro gameport joystick connected to an old SB Audigy card on my super fast Phenom II system.

 

http://www.andovercg.com/ebay/images/tdo-1786.jpg

 

Havent had any problems in any games.

 

I stocked up on a few of these old schools joysticks, coz they do tend to break after 1-2 years of heavy usage.

 

Good sticks, responsive, precise, light, ergonomically perfect. Too bad they stopped making these and the newer ones are over complicated and just make things more difficult..

 

The best mouse outthere is a 3-button MS Wheel Mouse Optical

http://www.dclstore.co.uk/images/products/microsoft-wheel-mouse-optical-usb-ps2-blk-ret-d66-00073-l.jpg

 

Same pro's: light, easy on hand, especially when you need to lift it up, and no annoying extra buttons.

Edited August 12, 2009 by [SCoRPioN]

[Panzertard]

mouse, not joystick, scorp.

[=SCoRPioN=]

mouse, not joystick, scorp.

Yeah, I was just expressing my opinion on the Sidewinder branded stuff, and that it's good stuff :)

[Panzertard]

Ah, okai - I thought you might have misunderstood there ;)

[sleepycanuck]

;730918']I'm using an old MS Sidewinder Precision Pro gameport joystick connected to an old SB Audigy card on my super fast Phenom II system.

 

http://www.andovercg.com/ebay/images/tdo-1786.jpg

 

Havent had any problems in any games.

 

I stocked up on a few of these old schools joysticks, coz they do tend to break after 1-2 years of heavy usage.

 

Good sticks, responsive, precise, light, ergonomically perfect. Too bad they stopped making these and the newer ones are over complicated and just make things more difficult..

 

The best mouse outthere is a 3-button MS Wheel Mouse Optical

http://www.dclstore.co.uk/images/products/microsoft-wheel-mouse-optical-usb-ps2-blk-ret-d66-00073-l.jpg

 

Same pro's: light, easy on hand, especially when you need to lift it up, and no annoying extra buttons.

I have an old Sidewinder joystick and wheel/pedals combo kicking around aswell. ;-)

 

Cheers and beers

Edited August 12, 2009 by sleepycanuck

[=SCoRPioN=]

I think most tend to over complicate their controls and lose the basic usability.

At the end of the day, this is still a game, and I like to be able to react quickly and easily control the chopper.

 

Both with LockOn and DCS, I use default controls.

The only thing I change are the dead zones and curves for the joystick axis.

 

I've seen in many instances people with X-52s and other tricked out sticks having ease of use issues, and have to spend some time to adjust the stick to their preference. What happens is you end up over doing the controls.

 

I'm sure the developer's defaults are thoroughly tested and are found to be the most logical and easy to operate with.

 

My stick is an old gameport sidewinder, and it rocks!

 

[Vel0th]

I had a similar crash log file and first believed the problem was caused by StarForce protect.dll but now solved the problem by unplugging my Xbox 360 controller. So if anyone else have problems with game crashes they also might try removing any unnecessary peripherals. Thanks for the tip!

[Anarkee]

Anyone heard anymore info about a fix for the MS Sidewinder Mouse and Blackshark? (I read it was an Issue with DirectX but there was supposed to be a fix for it in the works.) Since I get the DINPUT8.DLL error in a couple of other games with the MS Sidewinder Mouse too, I tend to believe it is a DX issue. it does not happen as much in other games but they dont have quite as complex control input systems as DCS.

 

I found that unplugging the mouse and plugging it back in (while DCS is not running ofcourse) will get you past the error.

[EtherealN]

There is no fix for the Sidewinder mouse at this time as far as I know. It's in microsoft's court since they need to make it work properly with DirectInput.

[flanker0ne]

I have a Microsoft Sidewinder Mouse (the one with little LCD and Weight bay),

and obviously I suffer the same issue than other, I try to unistall the Software Intellipoint and plug the mouse, losing the programming Macros on-the-fly but it work, I think the problem is with the added button for handle the macros.

Waiting for some fix from DCS anyway.....:helpsmilie:

 

Hope I don't have discovered the hot water!!!!!!!!!!!!

Edited October 14, 2009 by flanker0ne

[Panzertard]

AFAIK there wont be any fix for the issue unless Microsoft themselves goes to work on the issue. Sorry. :)

[Paulowanclift]

I've found running it once and unplugging the mouse beforehand, then plugging it back in once the game starts cures the problem for me.

[EtherealN]

That's interesting. Bit of an annoying workaround but very interesting.

 

Someone else that own the Sidewinder feel like testing that? Might offer a clue as to what exactly the problem is, even if we still have to hope Microsoft bothers to fix the issue.