TBarina

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.