stormrider2

Electronic warfare module? Official supported Voice command? Combined arms 2? DCS ATC? VULKAN ?

I partly agree. I would love, as much as you, to have VAICOM working again. But not half working as a temporary solution. In this case, I would prefer that ED uses its development time to create something official, be it an in-house solution or to officially support or license a VAICOM-like third party product. A temp solution will eventually break again and again. Perhaps the reason why Hollywood disappeared is because he's been hired or licensed by ED. We can always dream.

I'm not sure that VAICOM's not working is ED's responsibility. It was never officially supported by ED in any way. It's a mod and therefore, the only one responsible for sustaining it is @Hollywood_315. The shame is that it was a paid mod.

TBH, competitive is not the word I would expect in DCS. Make it realistic please.

Google. Sorry, I can't be of more help there, depends of where you live as well.

Its actually a 2 extra buttons mod, one of up and the other for down. It will be handy as the radar elevation knob for when the F-15E comes out. You can find it cheaper tho.

Don't forget to provide tracks.

CPU: I9-9900K - GPU: RTX 3060 Ti 8gb - 32gb RAM - 2TB SSD Better single core performance and better GPU despite having less VRAM.

You can activate / deactivate the AI at will using triggers and actions. The problems are that static objects don't heat up or cool down the same way as "living" AI objects do, so they appear quite different on FLIR. Also, we should be asking the question of why the AI consumes so much computing while doing nothing, just sitting still.

I'll take two then.

I don't care about any datalink.

B-1B or F-117A for me.

The travel length is only one of the variables and you shouldn't focus on it alone. There's also the mechanism precision and the board's resolution. I also have a CH pro throttle, upgraded to 10bit resolution. The problem there is that the physical mechanism of the throttle is not all accurate. I currently have a TM Warthog throttle that, although not the best, it is years ahead in performance. I can now reliably AAR, simply because of the new throttle.

Thank you @Bailey for your effot to put this one up. If anything, my only suggestion would be to, instead of using VA default keyboard presses output, which can cause conflicts with different keyboard layouts, to assign the functions to vJoy buttons using VA plugin: https://forum.voiceattack.com/smf/index.php?topic=463.0

You can program it in TM Target software or as suggested in Joystick Gremlin. I prefer the later for my profiles because in my peripherals ecosystem, I use different brands of gears and Joystick Gremlin allows me to bind them to virtual interfaces (vjoy). I also do a lot of programming in terms of "Modes", to increase the combinations of buttons. To give an example, when I lower the landing gear, its two way permanent switch is programmed to also change to a "Landing Mode", which assigns different functions to, say, the weapons buttons that are obviously not necessary during landing. These new functions range from "Comms" shortcuts, Jester shortcuts, to toggling the Hook and so on. It gets complex quite quickly, but the range of possibilities that it opens up is infinite.

What version of the Oculus software are you using? Some people reported stuttering with latest v43 or something.

The HAGS in Win10 you will find in: Start > Type in: Graphics settings > Switch Hardware-accelerated GPU scheduling to off.

Have you tried repairing your DCS installation? I used to play with a 1070ti that worked great, even in VR. I upgraded to a 3080 and soon after, during my first attempt, it stuttered a lot and I saw a lot of pixelization around the MSAA mask. I shut DCS off and did a full repair and yeah, it found some old files from some old mods that I didn't even remember having and immediately it was a completely different experience, worthy of a 3080.

Thank you both!

Try full-repairing your DCS installation.

Reduce your preload by half and try again.

Have you tried inspecting the packet with Wireshark?

I'm pretty sure George, in its current state, wont engage helicopters; at least not with Hellfires.