hornblower793

All, With the transition of control of Vaicom from @Hollywood_315 to a user community team we have decided to lock this thread. At 308 pages long it has become unwieldy and we know that it is easy for us to miss issues. Please check the other threads in the Vaicom forum (https://forum.dcs.world/forum/329-vaicom/) or head to the Discord (https://discord.gg/7gbYqKEsX6) - we are trying to keep them topic specific (e.g. each issue will have its own thread) and also to provide pinned topics such as the latest release versions of the software for OB and stable versions so that forum users have known locations to look for update news. @MAXsenna and I (along with other members from the community) are also available to help answer any queries so feel free to DM us if you prefer to do this rather than creating a thread

It is on the github - we would ask people to first concentrate on basic issues with the new version, and will then gradually expand it out to wider issues (such as comms not working with some airframes once wow)

We totally agree, and would like to try and keep all users moving in a single group - it will be to the benefit of all

Github will have the releases and will also host the bug tracking - I will also add a new thread to this forum that will contain details for the releases from our community group moving forwards so that people can check here or on the Discord, as well as going directly to the hub

If not done by someone else in the meantime, I will do this evening when I return from work (UK time) Sent from my SM-T835 using Tapatalk

Yep - the team is working hard to get a more robust fix out, but it probably won't autoupdate for everyone in the way it used to Sent from my SM-T835 using Tapatalk

There is a fix nearing completion - it is now being looked after by the community and a team is currently resolving issues. If you are on Discord, head to the community server (https://discord.gg/7gbYqKEsX6) for the latest

Agreed - we are already looking at how to best identify and track issues, and will post both here and on the Discord (https://discord.gg/7gbYqKEsX6) once we have formulated some ideas and the coding wizards have had a chance to look at the code and understand in depth how it works

Starting from now, Vaicom is no longer supported by its original developer. For answers to questions please either head to the Vaicom Discord (https://discord.gg/7c22BHNSCS) or contact either @MAXsennaor me via these forums (either posted or as a DM) and we will do our best to help. A team of volunteers is already forming to take this product forward but it will take us a few weeks to get fully up to speed.

As noted above, the Vaicompro website is no longer supported. The Discord server (https://discord.gg/7c22BHNSCS) is a good place to seek support, but also feel free to continue raising issues in these forums or DM either @MAXsenna or me and we will help

It has been placed on Github as open source. A small (but growing) team of users from the Vaicom Discord is already working on the code to deliver a rounded fix for the 2.8 issues and starting to work out how we best support / enhance the product into the future for the benefit of all. Given @Hollywood_315has generously placed it in the public domain we intend to honour that approach to keep both current and new users supported. @MAXsenna and I will lead on support in these forums for users who are not on the Discord (https://discord.gg/7gbYqKEsX6). Please give us a bit of time to work out what we are all doing / how this great plugin works but the intention is to then deliver updates / fixes as required, including a formal bug / issue tracker that all will be able to contribute to. In the meantime, all offers of help / expertise will be warmly received and any issues please either post in the forums or DM either Max or myself and we will do our best to get the answer.

We can always find a role for volunteers - testing across all airframes etc. Sent from my SM-T835 using Tapatalk

We haven't got that far in thought processes yet - the guys who can code (used to be me but I moved on many years ago) are focussed on immediate patching and the rest of us are just lobbing ideas in[emoji16]. I think it will be an incremental thing, with initial focus on maintaining functionality and understanding what it does before we move on. Regular updates will be posted here as we move forwards. Sent from my SM-T835 using Tapatalk

If you haven't already, head to the Discord and offer your services. We are assembling a team to take it forwards and it would be great to have a single, coordinated effort rather than a series of splinter groups[emoji108] Sent from my SM-T835 using Tapatalk

All, For those who are not yet aware, @Hollywood_315 has placed the Vaicom source on github this morning and is therefore no longer supporting it. We are in the process of pulling together an ongoing development and community management team and will update as further details become available. Massive thanks to @Hollywood_315 for having produced such a great tool and supported it for so long. Sent from my SM-T835 using Tapatalk

Unfortunately no I haven't, and have had no time to fly myself either recently. Hopefully that will change soon though

It doesn't exist as a command - I had that for a while and it disappeared with an update. I just ignored it

There are 4 of them at the moment - I am sure others will follow

Which modules? Have you confirmed the settings sliders are correct for your DCS install (standalone / steam and stable / openbeta)? If these are right please could you turn on Vaicom debug, restart Vaicom and then post the resulting log here (found in the logs folder of your Vaicom install). Happy New Year [emoji5] Sent from my SM-T835 using Tapatalk

Yes - turn off auto browse in Vaicom config Sent from my SM-T835 using Tapatalk

Does it show the commands you are speaking and then say whether they are recognised or not? Sent from my SM-T835 using Tapatalk

What does the VA / Vaicom log show? Sent from my SM-T835 using Tapatalk

Also, do you have auto browse turned on or off in the Vaicom settings? Sent from my SM-T835 using Tapatalk

What settings do you have in Vaicom config? Does this happen for all aircraft, and does something similar happen if DCS isn't loaded. It might be worth turning Vaicom debug on, restart VA and then post the Vaicom log here - this will let us see if there are any config messages that might give a clue Sent from my SM-T835 using Tapatalk

You are right -@MAXsenna is good and these forums do work very well Sent from my SM-T835 using Tapatalk