operatorone Posted November 14, 2019 Share Posted November 14, 2019 DCS crashes if I try to slew the AGM62 in the TV mode without Datalink pod. If I press TDC depress for some time, the screen freezes and DCS will crash. I added my dcs.log file for some more info. Any ideas on this? :joystick: Cheers, operatoronedcs.txt Link to comment Share on other sites More sharing options...
Flagrum Posted November 17, 2019 Share Posted November 17, 2019 (edited) I had this as well. I suspect, it has to do with "unlimited ammo=on" that I was using. Loaded with 2 AGM62 (+ DL pod, which I did not use), the first AGM62 did work as expected. Bomb released, stores page STEPped to the other pylon. Did not do anything with the 2nd bomb, but waited for the automatic rearming to happen. Then tried to use the 2nd, still boxed bomb, but no video was shown. Then pressed STEP to get back to the first pylon. There was video feed available, but from the original target area of the first bomb drop (already miles behind me at that moment). After uncaging, I could slew the seeker for, maybe half a screen, then CTD happened. No track available due hard CTD and the DCS.log also ends way before the issue showed up. My guess: something goes wrong with the initialization of the autmatic rearmed weapons (maybe in conjunction with the fact, that the priority station has changed to the 2nd pylon?). edit: I found a Win MiniDump file of the crash in C:\Users\...\AppData\Local\CrashDumps and attached it here - hope that helps. WinDbg analyze report: Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\...\AppData\Local\CrashDumps\DCS.exe.6472.dmp] User Mini Dump File: Only registers, stack and portions of memory are available Symbol search path is: srv* Executable search path is: Windows 10 Version 18363 MP (8 procs) Free x64 Product: WinNt, suite: SingleUserTS 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Debug session time: Sun Nov 17 08:17:32.000 2019 (UTC + 1:00) System Uptime: not available Process Uptime: 0 days 0:22:45.000 ................................................................ ................................................................ ................................................................ ............................................................... Loading unloaded module list .......... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (1948.129c): Access violation - code c0000005 (first/second chance not available) For analysis of this file, run !analyze -v *** WARNING: Unable to verify checksum for CockpitBase.dll CockpitBase!cockpit::avTVSensor::search_handler+0x43: 00007ffa`4b86fbc3 418b18 mov ebx,dword ptr [r8] ds:00000000`0000001c=???????? 0:000> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** WARNING: Unable to verify checksum for ed_sound.dll KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullClassPtr Key : AV.Fault Value: Read Key : Analysis.CPU.Sec Value: 4 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-GIB8LP0 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 102 Key : Analysis.Memory.CommitPeak.Mb Value: 201 Key : Analysis.System Value: CreateObject Key : Timeline.Process.Start.DeltaSec Value: 1365 NTGLOBALFLAG: 0 PROCESS_BAM_CURRENT_THROTTLED: 0 PROCESS_BAM_PREVIOUS_THROTTLED: 0 APPLICATION_VERIFIER_FLAGS: 0 CONTEXT: (.ecxr) rax=00007ffa5ba2ca70 rbx=00000000007ce640 rcx=00000000007cc238 rdx=00000000007cc238 rsi=000000066421de20 rdi=00000000007cc238 rip=00007ffa4b86fbc3 rsp=00000000007cc160 rbp=00000000007cc390 r8=000000000000001c r9=0000000000000165 r10=0000000000a6f860 r11=0000000091de7be0 r12=00000000007ce620 r13=000000000000000c r14=00000000007cc470 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010244 CockpitBase!cockpit::avTVSensor::search_handler+0x43: 00007ffa`4b86fbc3 418b18 mov ebx,dword ptr [r8] ds:00000000`0000001c=???????? Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffa4b86fbc3 (CockpitBase!cockpit::avTVSensor::search_handler+0x0000000000000043) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 000000000000001c Attempt to read from address 000000000000001c PROCESS_NAME: DCS.exe READ_ADDRESS: 000000000000001c ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 000000000000001c STACK_TEXT: 00000000`007cc160 00007ffa`4b8742c1 : 00000000`007ce640 00000000`00000165 00000000`00000000 00000000`00000000 : CockpitBase!cockpit::avTVSensor::search_handler+0x43 00000000`007cc1e0 00007ffa`5ba1c8b1 : 3fe00000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CockpitBase!cockpit::avTVSensor::get_camera_position+0x851 00000000`007cc210 00007ffa`3bc84061 : 3fd85894`c0000000 00000000`00000000 00000000`00002756 00000000`007ce640 : edObjects!LandObjectStorage4::GetStatistics+0x191 00000000`007cc260 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : edterrain4!landscape4::CreateITerrainStub+0x45e1 SYMBOL_NAME: CockpitBase!cockpit::avTVSensor::search_handler+43 MODULE_NAME: CockpitBase IMAGE_NAME: CockpitBase.dll STACK_COMMAND: ~0s ; .ecxr ; kb FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_CockpitBase.dll!cockpit::avTVSensor::search_handler OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {6fd25ccd-9b44-03b8-d2c1-69110b0ec72b} Followup: MachineOwner --------- MiniDump.zip Edited November 17, 2019 by Flagrum Link to comment Share on other sites More sharing options...
operatorone Posted November 20, 2019 Author Share Posted November 20, 2019 Hi, I tested it withou "unlimited ammo" and it seemed to work out fine. Link to comment Share on other sites More sharing options...
ED Team NineLine Posted November 20, 2019 ED Team Share Posted November 20, 2019 While I didn't get the crash, I do see the sensor getting stuck on the already released weapon, and I could see where that might possibly crash the game, I have reported the issue, thanks! Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
Recommended Posts