GamingShogun

Personally, I had hoped it would originally be an EA-6B Intruder. Tandem multiplayer and SEAD/jamming simulation would be an interesting twist. But, after getting that from Wags I am hoping it is an Eagle or Strike Eagle. -GS

Hey guys, I am rather new to the forums but not to flight simming in general. I just wanted to report a bug and fix my friend and I discovered while attempting to do some multiplayer flying in LO:FC2. I would create a server and my friend would join it by I.P. After a few minutes he would be kicked from the server with an error that told him 'Ping Timeout'. His connection was fine otherwise, he checked his latency and all other manner of network metric but could not find the problem. After some forum searching, I discovered that the cause of this issue was the new Bigfoot Networks Killer XENO Pro card I had installed in my gaming rig. So, beware, fellow simmers! That card is not gamer-friendly yet apparently, at least in Lock-On. If you do not wish to remove the card completely, you can make sure it is set to Application Mode (compatibility) to temporarily fix the problem. Talk soon! GamingShogun - Saitek X65F? Nothing but awesome.

Thanks Chizh, I will try it without the keyboard and report back ASAP! Shoot, that did not work either. It is weird. The simulator loading screen gets about 75% of the way and then turns white for a few seconds. Still sounds like display to me but I have tried the 190, 186, and 185 drivers without luck. Just so odd.

Okay, so I tried both methods and it still does not work. I am uploading the new crash and error log files as well as my DxDiag in hopes that someone knows the answer. Thanks again for the responses thus far, all! DxDiag.txt DCS-20090722-091313.crash.txt Error.log.txt DCS-20090722-091345.crash.txt

Thanks Panzertard, I will try those drivers as well as the Chkdsk method and report back!

Funny thing is that before the sim executable shuts down, and launches the debrief screen, it turns white for about ten seconds.... Anyone experiencing similar issues with Nvidia drivers? I have heard of this issue with ATI but not Nvidia.

Sure thing! Here is a C&P of a .crash file. I definitely appreciate the insight. I can't make heads or tails of this info. # -------------- 20090718-222912 -------------- àñ� # C0000005 ACCESS_VIOLATION at 3E0661B0 00:00000000 # # EAX = 00000001 # EBX = 3E0661A0 # ECX = 3E0661B0 # EDX = 00000001 # ESI = 43569FF8 # EDI = 3E0661B0 # CS:EIP = 0023:3E0661B0 # SS:ESP = 002B:0017F648 EBP = 00000030 # DS = 002B ES = 002B FS = 0053 GS = 002B # Flags = 00010212 3E0661B0 00000030 0000:00000000 3E0661B0 00000030 0000:00000000

If you find a solution, would you mind letting this thread know? I received the same crash. MP or SP, single missions, or instant action - doesn't matter. Mission begins loading, it gets about 75% of the way through then the sim crashes and the 'after mission' debrief menu pops up. Intel i7 2.6 6GB DDR3 BFG GTX-280 VISTA 64-bit SB X-fi Fatal1ty Titanium All drivers up-to-date, running 'as admin', and anti-virus disabled. The issue also occurs no matter what game peripherals I have plugged in or not.

Would love to see a real F-14D sim. Microprose's was amazing but I know DCS could do it way better. Now that they are retired, getting access to museum pieces, after-action reports, and ex-Turkey drivers would be much easier.