LockOn2 Crash

[Mirtma]

Windows 7 64 bit. Install went OK. Activation OK. Options Ok. Start quick mission. Loading objects, ground objects... line goes to the end, than started at beginning, wait.. at app. 1/3rd of the line, program crashes. And return me to Debrifing data, where I can select fly again or close.

 

Here is log from Event veiwer:

 

Faulting application name: simulator.exe, version: 1.0.2.0, time stamp: 0x4bab85cd

Faulting module name: NPClient.dll, version: 0.0.0.0, time stamp: 0x2a425e19

Exception code: 0xc0000005

Fault offset: 0x0005cf32

Faulting process id: 0xf90

Faulting application start time: 0x01cacd86a746fc8e

Faulting application path: D:\Igre\LockOn Flaming Cliffs 2\bin\x86\stable\simulator.exe

Faulting module path: D:\Igre\il21946-UI\NewView_37m\NPClient.dll

Report Id: 0634cd8e-397a-11df-b57b-001d7dc7d6bd

 

HELP!!! http://forums.eagle.ru/images/smilies/cry.gif

[Mirtma]

I found in view settings that Track IR commands are defined. Since I don't have TrackIR I've cleared those settings. Now, when start lock on quick mission, I get new error (at about same place than before: simoulator.exe - NO Disk. There is no disk in the drive. Please insert a disk into drive \device\harddisk3\DR3. Then Flaming Cliffs 2 has stopped working.

Black Shark is working without problem, also LOFC1.1.

[Mirtma]

Oh, no! Black Shark has now same problem!

[Mirtma]

LockOn 1.1 still working. What's wrong?

[Mirtma]

Talking to myself sometimes works. It was NewView problem. Software that imitates TrackIr. I've deleted it and now it works. http://forums.eagle.ru/images/smilies/smartass.gif

[EvilBivol-1]

Good work.

[trigen]

Please insert disk into... fun msg

 

 

I've been having the same problem for some time now and frankly its getting quite annoying.

 

 

I've tried installing the game on different hard drives with the same problem.

 

sometimes it crashes on game start and sometimes i start a mission and it crashes, i press fly again and it works.

 

i do not think its a hardware issue as its only FC 2.

 

I hope you can get some of this sorted as soon as possible. some days 7 out of 10 starts the game crashes, and some days there's no issues at all, it seems to have a life of its own.

 

Perhaps some memory leak ?

 

Here's some error logs

 

Faulting application name: simulator.exe, version: 1.0.2.0, time stamp: 0x4bab85cd

Faulting module name: ZweiBlau.dll, version: 0.0.0.0, time stamp: 0x4bab80f9

Exception code: 0xc0000005

Fault offset: 0x00023220

Faulting process id: 0x1e3c

Faulting application start time: 0x01caddbb33fb38e3

Faulting application path: E:\games\Eagle Dynamics\LockOn Flaming Cliffs 2 VRA\bin\x86\stable\simulator.exe

Faulting module path: E:\games\Eagle Dynamics\LockOn Flaming Cliffs 2 VRA\bin\x86\stable\ZweiBlau.dll

Report Id: 7d403634-49ae-11df-8063-00248c485fab

 

Faulting application name: simulator.exe, version: 1.0.2.0, time stamp: 0x4bab85cd

Faulting module name: DINPUT8.dll, version: 6.1.7600.16385, time stamp: 0x4a5bd9c1

Exception code: 0xc0000005

Fault offset: 0x0001479b

Faulting process id: 0x1528

Faulting application start time: 0x01cade1529d185d2

Faulting application path: D:\games\Flight Simulator's\Eagle Dynamics\FC 2 - VRA\bin\x86\stable\simulator.exe

Faulting module path: C:\Windows\system32\DINPUT8.dll

Report Id: 098a69bb-4a16-11df-8063-00248c485fab

 

 

 

Faulting application name: Launcher.exe_unknown, version: 0.0.0.0, time stamp: 0x4ba9d487

Faulting module name: DINPUT8.dll, version: 6.1.7600.16385, time stamp: 0x4a5bd9c1

Exception code: 0xc0000005

Fault offset: 0x0001479b

Faulting process id: 0x110c

Faulting application start time: 0x01cade1515d850b3

Faulting application path: D:\games\Flight Simulator's\Eagle Dynamics\FC 2 - VRA\bin\x86\stable\Launcher.exe

Faulting module path: C:\Windows\system32\DINPUT8.dll

Report Id: 567fbfd8-4a08-11df-8063-00248c485fab

[EtherealN]

Hm, access violations (exception 0xc0000005) related to Dinput8...

 

     Device Name: SideWinder™ Mouse
        Attached: 1
   Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0724
       FF Driver: n/a

 

It's hardware. That mouse has a problem with DirectInput that microsoft doesn't feel like fixing. Try without it. :/

[trigen]

i'l give that a try

 

 

Thanks a bunch

[EtherealN]

My pleasure.

It's a bit tragic that a microsoft mouse should have such issues with DirectInput, another microsoft product, and not get fixed. (ED has been in contact with Microsoft about this issue.)

 

It is also possible that something wonky is happening with the G15 - that's another problem child, but not nearly as bad as the sidewinder mouse - the only "fix" I've ever seen for that mouse in DCS:BS (and therefore likely FC2 as well) is not to use it. Bit of a shame. :(