TBarina

Is there any solution? I'm still facing this problem even after applying the latest upgrade.

Thanks a lot. I forgot it! Sorry indeed.

I've the same issue but at dusk and night only. During day light it works perfectly.

Here is the mission. A very simple one. Only 2 Hueys on the runway at Batumi ready to takeoff. The problem is not the mission. The same issue is present in any mission or campaign in all scenarios. When EasyComms OFF: weird behaviour of the comms menu (VAICOM PRO fully disabled and removed fror export.lua). First of all I take off and wait on channel two for wingman to take off as well. I can hear his radio message on channel 2 (UHF 251.00) saying he is rejoining. Then I can issue commands by opening Comms Menu in Private channel (no other way to do that) and, of course, wingman doesn't respond and doesn't obey. Thanks TB_HUEY_Test_NonEasyComm.miz I'm flying DCS openbeta latest release in MT. Same issue in ST.

. I've made this test: simple mission with 2 hueys on the same frequency UHF 251.00. EasyComms Off. The only way to open Communication Menu in the air is to switch Radio selector switch to Private. Then, after menu appears, I turn the switch with the mouse to channel 2 (for UHF 251.00). Then I presws F2 and F4 to order wingman to cover me. Message is sent. But, just after message is sent, the radio selector switch automatically switches to Intercom position and WIngman doesn't respond and doesn't obey. The same happens with all other messages and commands to wingman. Also ATC doen't respond. Everything runs smoothly with Easy Comms ON instead.

I had similar problem recently especially because I'm using AMD 5800X3D that doen't have integrated graphics. My main GPU is RTX4090. When I installed a second NVidia GPU I had FPS issues. Then I tried RXT4090 togheter with an AMD Graphic Card and now it works flawlessly

Thanks. Great solution.

Ciao, I'm using RTX 4090 as well, with AMD 5800X3D and 64GB DRAM 3200. I run with 5 monitors 1920x1080 x 5, phisically organized like this: 4 (Upper view, to check the sky over the HUD. Very useful in doghfight) 1 2 3 5 (for Helios with 2 Thrustmaster Cougar for Left and Right MFD export and IFEI, RWR, etc.) plus 6 (1020x760 WinWing MFCD) In Windows Display setting they are arranged in line and the resolution in game is set to 10368 x 1080. No issue so far. Same as 2.8. All maxed out (AA set at 4X) in MT at constant and stable 60 fps (with theretically 130-160 indicated in heavy missions). In Task Manager my 4090 is working at 65-85%. DLSS stuff doesn't provide me with any extra benefit. I prefer native.

Same problem at night with the exported Central MFCD in F18. It only occurs at night both in ST and MT. I didn't have this issue in 2.8. It's a new issue caused by 2.9 I've also tried to export the MFD to the same monitor as the sim and the problem appears as well. So it's not due to any multimonitor setting. Very annoying especially when the moving map is shown. Also the usual problem of the huge difference in gamma between cockpit MFD and the exported one is still present in 2.9 At the moment F18 is not yet certified for night mission

Same problem in Huey here

That's very kind of you. I appreciate it. Surely it's a minor issue. When I show DCS to friends of mine it's annoying though. They say DCS is buggy and they prefer IL2. Also, since it's minor, it should be easy to fix. BTW: I've not encountered problems with MT so far. No crashes, no issues. And MT it's damn necessary. I've been able to run complex SP missions with hundreds of objects that were impossible to run in ST (e.g.: F18's Battlefield instant action) that now,, with MT and ProcessLasso,runs with in a steady 180 fps in my rig (5800x3d + RTX4090 at 10624 x 1080 with all the whistles and bells offered by Helios, Andre's SimShaker, VaicomPro and Buddy-fox). Safe flight!

I wonder why ED doesn't fix this; should't be that difficult to cut it out before mission actually start.. Seems like MT is working well during missions and the more people use it the more we can help ED with bug reports. But I hate starting a mission with all that nasty flickering. I prefer to stick to non MT version until this is fixed :(

Anyone knows if this can be fixed? Many thanks in advance

Also this problem when loading mission:

Same issue with Huey. In Syria is even worse.

In the new glory of the community. Many thanks to all that have contributed and thanks to Hollywood for his decision. I've just upgraded to 2.8 and installed Vaicom 2.8. It's working even better now.

Hi, where is Vaicom on GitHub. I cannot find it. Ops, sorry. Found it at https://github.com/Hollywood315/VAICOMPRO-GPL Now it is open source. We can download and even fork it. I've opened it in Visual Studio and can be edited and recompiled.

Appreciate that we can still map and ball call again

I know, thanks. I was joking I have complex profiles in VA that complement VAICOM for managing Intercom in Huey. You can get a lot out of VA but not all you can do with the aid of VAICOM. Simply it's not the same otherwise it wasn't worth buying VAICOM

LSO: "Call the ball..." Pilot: "Options, Take 5, Take 1..." Great example of radio communication that complies with US Navy procedures! Cheers Clouds are moving though...

Thanks. It doesn't depend on the module though. It's probably a general newwork issue since it doen't initiate the communication.

DCS 2.8 + KA-50 + VAICOM working now? It would be great! I've reverted back to 2.7 and have no room to install 2.8 as well for testing. Hope someone has the chances to give a try and confirm. Many thanks for the info.

Probably we must be patient. I don't think ED can answer without talking with programmers in charge of VAICOM. Probably is something concerning the network protocols. In the stable changelog I can read: DCS 2.7.18.30765 Home > News > Changelog > Stable changelog > DCS 2.7.18.30765 DCS World Network protocol version changed Probably this has something to do. They need cohoperation to provide valid infos. Let's hope VAICOM support can respond. Ciao

Many thanks for your answer. Seems like Hoolywood is MIA. Let's hope he is ok. I've just sent an e-mail to support@vaicompro.com to forward your message. Let's hope he can answer.