HeliHell

They only fixed Gazelle after player outcry that they had In fact abandoned it....

Should be refunds for this. They simply do not match up to the screenshots shown before release. Zero comms from the devs also. This is Falklands 2.0 but this time people are actually voicing opinions about receiving a bad product

Even turning off the collisions for the trees would be a very good temporary measure until they can create this. We already have ME capability to remove / destroy scenery. This should hopefully be an easy tick box for ED

Apache to Hornet seems to be the issue. # -------------- 20240301-194052 -------------- DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.22631) C:\Program Files\Eagle Dynamics\DCS World\bin-mt\dx11backend.dll # C0000005 ACCESS_VIOLATION at 00007ffbbea18c77 00:00000000 SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World\bin-mt;', symOptions: 532, UserName: 'adamc' OS-Version: 10.0.22631 () 0x100-0x1 0x0000000000018c77 (dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37 0x0000000000017788 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68 0x000000000000be2e (GraphicsCore): enlight::AtmosphereWrapper::precompute + 0x40E 0x00000000000a3a41 (GraphicsCore): render::ShadowMapModule::queryCasters + 0x921 0x00000000000542af (GraphicsCore): render::BaseRenderingPass::execute + 0x1F 0x0000000000054974 (GraphicsCore): render::BaseRenderingPass::execute + 0x6E4 0x0000000000058f7d (GraphicsCore): render::RenderGraph::render + 0xED 0x000000000001bb92 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42 0x000000000016299a (Visualizer): smSceneManager::regLua + 0x129A 0x000000000014deb4 (Visualizer): smCamera_Implement::getClipRegion + 0x19594 0x0000000000139cdc (Visualizer): smCamera_Implement::getClipRegion + 0x53BC 0x0000000000151192 (Visualizer): smSceneManager::DestroySceneManager + 0x1222 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D

Same issue as above. Seems to happen when switching from Apache to hornet. Hornet is hot on the boat. click A/G and instant crash hash dxdiag.txt dcs.20240301-194052.trk dcs.20240301-194052.log

Shame about Apache datalink not having the same functionality of the other modules with positional data constantly updated. Hopefully this is on a to-do list