NEECH

This hurts my brain I've wondered if the AI enemy is subject to visibility issues as a human enemy would be. Night, cloud cover, etc; does it affect their ability to visually see an aircraft?

I know this pain all too well and I think it’s just the nature of the missile’s seeker. DCS – A-10C II TACTICS – Maverick Miss Lock

I added a new link to a high-res version in the original post. And 7 missile hits; the F-15 snuck in a last second one I missed in the original video.

I've shot down plenty of helicopters in DCS, and I've never seen one take six Sidewinders plus gun damage from multiple aircraft and still operate while on fire.

Yesterday, myself and a few others tried to shoot down this KA-27 which took damage (was on fire) but nothing beyond that despite many hits. Here's the Tacview; -edit: hi-res version I've seen this before with the KA-27, and I'm unsure if it was on the same MP server.

This function, to lase & store, is such a fundamental function for the gunner that I'm still surprised ED released the AH-64 without it, let alone take this long yet to add it. To add insult, George actually states he's lased & stored the target.

Yeah, per the article, the A-10 "can now employ up to 16 GBU-39/B Small Diameter Bombs (SDBs) on a single sortie, among other stores, with the help of a new software update." If they can mod it, why can't we? Seriously, this would help tremendously with SEAD work when there's little help on a server to do so.

Yes, please! I would love to add this as an option. A-10 Warthog To Soon Carry 16 Small Diameter Bombs In Combat

Thanks! It's been frustrating trying to nail down the driver at fault.

I was about to smack a SAM site when my Win11 PC BSOD'ed. OS is up to date. Crash report is included. Driver Verifier was/is disabled. I did not see a crash report from DCS; however, I had one today that I submitted, which did not cause a BSOD, just the application crash. Please let me know if there's any additional info or log files needed. Happy to help. Thanks Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\042323-8312-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (24 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff802`3e600000 PsLoadedModuleList = 0xfffff802`3f213420 Debug session time: Sun Apr 23 20:22:13.940 2023 (UTC - 4:00) System Uptime: 12 days 6:27:54.053 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................. Loading User Symbols Loading unloaded module list .................................................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`3ea293a0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff802`42e04ed0=00000000000000e6 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DMA_VIOLATION (e6) An illegal DMA operation was attempted by a driver being verified. Arguments: Arg1: 0000000000000026, IOMMU detected DMA violation. Arg2: 0000000000000000, Device Object of faulting device. Arg3: 0000000040388cc1, Faulting information (usually faulting physical address). Arg4: 0000000000000004, Fault type (hardware specific). Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 390 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2384 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 61 Key : Analysis.Init.Elapsed.mSec Value: 12422 Key : Analysis.Memory.CommitPeak.Mb Value: 98 Key : Bugcheck.Code.DumpHeader Value: 0xe6 Key : Bugcheck.Code.Register Value: 0xe6 Key : Dump.Attributes.AsUlong Value: 1008 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 FILE_IN_CAB: 042323-8312-01.dmp DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump BUGCHECK_CODE: e6 BUGCHECK_P1: 26 BUGCHECK_P2: 0 BUGCHECK_P3: 40388cc1 BUGCHECK_P4: 4 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: DCS.exe STACK_TEXT: fffff802`42e04ec8 fffff802`3eb1cd8d : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`40388cc1 : nt!KeBugCheckEx fffff802`42e04ed0 fffff802`3eb0633b : fffff802`3f261900 fffff802`3f261900 fffff802`3a171100 fffffc03`f8e30aa0 : nt!IvtHandleInterrupt+0x1bd fffff802`42e04f20 fffff802`3e94b46e : fffff802`3f30df90 fffff802`3f30e040 fffff802`3a171180 fffff802`3f30df90 : nt!HalpIommuInterruptRoutine+0x4b fffff802`42e04f50 fffff802`3ea2b3cc : fffffc03`f8e30aa0 fffff802`3f30df90 000001c5`3a48d520 00000000`00000001 : nt!KiCallInterruptServiceRoutine+0x19e fffff802`42e04f90 fffff802`3ea2b957 : 00000000`00000002 ffffb90f`c1ad6260 000001c4`14b2b1b8 00000000`00000000 : nt!KiInterruptSubDispatchNoLock+0x11c fffffc03`f8e30a20 00007ff8`f5831d10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x37 00000045`cc92dfe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`f5831d10 SYMBOL_NAME: nt!IvtHandleInterrupt+1bd MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.1555 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1bd FAILURE_BUCKET_ID: 0xE6_26_nt!IvtHandleInterrupt OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {11608481-d56e-58cc-4b64-17c92254d2f4} Followup: MachineOwner ---------

Thanks, I'll give this a try. Seeing his targets better definitely will help. My lack of trust in his aiming has made me a better pilot. MP for the most part. It's been a while since I played SP. SP I've only played the training runs; flying higher, faster which means a closer, easier to see target too. Thanks for the replies, guys. Unfortunately, my tracks are too long to share. It takes a while to sneak under the radar.

George is excellent at spotting targets. George is not good at hitting them. I know I'm going to get numerous questions about what I'm doing when he's missing. I can say, undoubtedly, there's no reason for him to miss the last shot that caused me to rage-quit! I was completely stable at 20 knots, nonobstructive view of the target, range was around 8K – long but considering the clear shot, completely doable. It's so frustrating to creep up on a SAM site for 25 minutes just to have him miss such an easy shot and waste a missile, sometimes repeatedly. Is it because he can't use the DTV camera that he often misses?

Figured it out. It was a resolution mismatch. The game was set much higher than what I am using in Windows. I dropped the game to the Windows resolution and it looks correct.

Hi all, Long story, short; I just finished moving and have missed a few updates. I also purchased a a new monitor. I'm not sure what's change but George's UI is at the 3 o'clock position between the center and edge of the screen instead of the corner. I also cannot see the target selection list. Has something changed with these two UIs? I haven't been able to find any game setting related to these this. TIA!

I asked for something similar last week. It would be a welcome option for sure. https://forum.dcs.world/topic/306874-george-ai-needs-a-search-range-limiter-option/?do=getNewComment