TBarina

Same problem in Huey here

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.

That's what I'm saying. ED should not disregard the efforts of the community and should have got in touch with good developers like Hollywood time ago. If they decide to change the protocols they should provide adequate information. What if TacView or other add-ons cease to work in the future. DCS is not a game. Is complex simulator that must be able to communicate with many add-ons, peripherals, cockpit panels, etc. As someone wrote here they don't provide any help or API to facilitate the community. BTW: The code has nothing to do but if you could examine the code (C# is a high level programming language that can be easily read) you could probably discover that 99% of the code only deals with it's own internal functionalities (i.e.: managing configuration and radios tuning) and only 1% relates to communication with DCS. I bet that with minimal support VAICOM could easily work again and serve the comminity until proper ATC is provided by ED.

Thanks for your response. VAICOM has been probably abandoned but is magnificient piece of software. Didn't die by himself. Simply ED have cut it out by changing something in the network interface (sockets). As soon as I have some time I'll write a small program to test sockets in 2.8 But I read in the forum that some people are complaining that other add-ons have ceased to work as well. ED is not supposed to take VAICOM under their wing it if they don't want to. But there is no need to shut the door and cut it out especially if they cannot prove themselves to be ready to provide good ATC solutions shortly. To tell the truth I'm not trusting ED so much now. I wouldn't be surprised if DCS was abandoned in the future if ED don't enlarge their visionI wouldn't be surprised if DCS would be abandoned in the future if ED doesn't enlarge their vision Like someone wrote we ara a niche and they have limited resources. Partnership is the main way for the future. Most big companies have already understood it by ages In any case: 2.8 is an openBETA. Hopefully ED is monitoring reactions and will amend if possibile.

Those are not nonsense to me. Imagine what could have happened to all the add-ons (take a tour in www.aerosoft.com) if Microsoft made modifications to FSX without guaranteeing compantibillity. We are a small community and since ED has limited resources it's crazy not to open to the community and create valid partnerships with those the have proved to be able to develop very useful an robust add-ons. Frankly, I say again, I'm fed up with rainbows, moving clouds, new similar aircrafts once a day that nobody will have time to learn and fly. I'd rather spend money on other things that add global immersion (Supercarrier is a real examples that demostrates how they can really respond to community requests. It's Early Access, I know and more has to come even if it will require monts or years. But was it not desolating to take off or land on empty deck? Same is with ATC. We have been getting away with VAICOM so far but it's crazy to cut it out. On my side, I can easily build VA profiles and, since I'm a C# developer I could even integrate VA with a plugin) but let VAICOM die is stupid. It can be a valid alternative until ATC is relaeased by ED, if they will. Surely VA is not the same as VAICOM but you can setup a bunch of voice command in VA like "Take 1", "Take 2" .... "Take 12" binding them to F1, F2, ... F12.

Better do that by using voice commands by means of VoiceAttack. Very easy to do in the same way as Vaicom did (Options, Take 1, Take 2, etc.).

The fact that there is plenty of third parties affected confirms what I was thinking: it's not an issue with VAICOM. The major part of the source code (VAICOM is written in C# .NetFramework 4.7.2) should hardly be offended by changes in DCS so far. There should be something wrong with changes in the network protocol by ED. They simply don't communicate any more at all. I think it should be up to ED developers to fix the issue by being backward compatible with the previous interface. I'm not pleased by 2.8 and have reverted back to 2.7. Frankly rainbows and moving clouds add less immersion than VAICOM does!

Cannot even image of flying such a great simulator and approach to the carrier while hitting F keys to send messages to marshal or LSO. It would completely spoil immersion.... I don't think it would be too difficult to fix VAICOM source code (it's a program written in C# .Net Framework). The problem is the UDP communication interface between VAICOM and DCS because they don't dialogate any more. The rest of the code is not probably affected by the chages in 2.8 like it was not affected at the time of 2.7 ED could byy the licence from Hollywood and amend the interface or could preserve 2.7 inferface within 2.8 for addon backward compatibility. In any case we must make a strong petition all togheter to ED for a quick ATC solution maybe in the form of an immediate Early Access release with a minimal bunch of functionalites with the intent to progress in the future months. Surely I'm not going to buy any other modules from them until they don'f fix this issue. To tell the truth, I'm fed up with countinuous relaeses of new aircrafts and scenarios. I'd rather have them pay more attention and effort to safaguard the flight and combat immersion. Let's hope so.