cAshewTheAce

Oh gotcha, i just briefly went over the video, my bad!

So with the new RWR sounds coming soon, would there be a way to still have old ones through a sound mod? Or would that break IC or be entirely impossible? I know most of y'all like the change, but for me i've grown to love the vipers RWR sounds and i can't imagine using the newer sounds...

From what i can tell, the new aim54cmk60 is able to go active in PDSTT correct? It was added earlier this year. Is the documentation given by heatblur just a bit oudated then? The manual states :

As the title says, the VOIP is not picking up any audio, or outputting it. I've checked my audio devices and my audio configuration, it should work. I know voicemeeter is not the standard setup a user would have, but it shouldn't cause issues like this. I've used this software for years and haven't had such an issue before. I can see the right audio devices in the drop down lists for voice chat options, but changing them leads to no effect. I don't know what files to add to this post, so if i need to add anything, please tell, i would love to help to get this issue fixed.

That's telling jester to lock targets. What currently we are missing is a way to tell him which target to hook, which is incredibly useful. And also telling him to possibly prioritise targets with "mandatory attack" and "next launch" buttons you find in the backseat. Either way, thank you HB for continuing to make the f14 amazing in DCS. I can't wait for the future, especially the updates on aim54's.

Back in 2019 i saw people asking for the ability to tell jester which targets to hook... Because currently he is a bit clueless. Has there been any developments in that area? Or is that not a priority for HB?

Negative, don't have the kneeboard folder in my openbeta saved games folder

Indeed that did fix the issue, atleast temporarily. What are the fxo and metashader folders for?

Well since it decided to delete the whole long report... Here is the tldr Maverick crosshair is bugged, the image shows it untouched (only put as SOI). It is not in the break lock mode (tws down just makes it not soi again). Regardless of mode this behaviour is roughly the same. What "fixes" this is setting the MSAA to 2x, as i had it on 0x. I also experimented with putting cockpit displays to 1024 and changing AF to 2x, but to no effect. PC specs are as follows Ryzen 3 2200g GTX 1060 3GB 16 GB ddr4 2777mhz DCS is installed on a 230gb nvme m.2 ssd I will send the DCS settings in a separate screenshot.