Jump to content

hornblower793

Members
  • Posts

    1715
  • Joined

  • Last visited

Everything posted by hornblower793

  1. Also actively being worked on Sent from my SM-T835 using Tapatalk
  2. These are currently being looked at by the team with a possible fix being tested
  3. I will pass your thanks on to the coding wizards who are making it happen[emoji3] Sent from my SM-T835 using Tapatalk
  4. All, With the transition of control of Vaicom from @Hollywood_315 to a user community team we have asked for this thread to be locked. At over 7700 posts 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 (/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 Sent from my SM-T835 using Tapatalk
  5. 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 (/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 Sent from my SM-T835 using Tapatalk
  6. Please use this thread to post any ideas for functionality you would like to see added or improved in Vaicom
  7. For all users running DCS Open Beta versions earlier than 2.8, please continue to use the last @Hollywood_315 release of Vaicom and its plugins, found at https://www.vaicompro.com/ With the release of DCS Open Beta 2.8 a community team has taken over ongoing development and support of Vaicom. The current release of Vaicom (also now versioned to 2.8 to align with the DCS major version and help avoid confusion moving forwards), along with instructions for installation, can be found at https://github.com/Penecruz/VAICOMPRO-Community for the installation instructions and https://github.com/Penecruz/VAICOMPRO-Community/releases/tag/v2.8.0.0 for the initial community release
  8. This thread will be used to provide details of the latest version of Vaicom for users running the Open Beta version of DCS (whether standalone or Steam). We would ask people to not post any questions, replies, comments in here so the only information relates to releases required for different DCS versions. Please start new threads to provide feedback / ask questions etc. The Discord server for the community supported Vaicom is at https://discord.gg/7c22BHNSCS. Many thanks Hornblower793
  9. This thread will be used to provide details of the latest version of Vaicom for users running the stable version of DCS (whether standalone or Steam). We would ask people to not post any questions, replies, comments in here so the only information relates to releases required for different DCS versions. Please start new threads to provide feedback / ask questions etc. The Discord server for the community supported Vaicom is at https://discord.gg/7c22BHNSCS. Many thanks Hornblower793 Users of the DCS stable version 2.7 should currently continue to use the last version of Vaicom and plugins released by @Hollywood_315 and pointed to from https://www.vaicompro.com/.
  10. 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
  11. 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)
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. hornblower793

    FAQ

    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.
  19. 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
  20. 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.
  21. We can always find a role for volunteers - testing across all airframes etc. Sent from my SM-T835 using Tapatalk
  22. 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
  23. 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
  24. 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
  25. Unfortunately no I haven't, and have had no time to fly myself either recently. Hopefully that will change soon though
×
×
  • Create New...