Jump to content

hornblower793

Members
  • Posts

    1715
  • Joined

  • Last visited

Everything posted by hornblower793

  1. It is because REF is for refuelling etc.
  2. Chief....page works for me
  3. Having done a lot of watching it, 2.5.24 does show the same weird behaviour under the hood if you sit and watch it (if you don't touch any keys or buttons you get mission reset messages in the VA log every 2 minutes when Vaicom polls DCS). The difference between the 24 and 25 is that listening is suspended before these and reenabled afterwards in 24, when in 25 it suspends after these messages and so never reenables. I have spent soooo long watching these damn things today . With DiCE installed, both of them also bring up the mission restart messages on every other press of the TX button.
  4. I don't think it is a fundamental issue with the server - I typically get 25 MB/s
  5. All, @Hollywood_315 and I have spent quite some time in conversation today regarding the DiCE issues. I can now confirm (thanks to Hollywood's debugging) that it is definitely an issue with the way that DiCE manipulates DCS information to insert its CMS files. It does something with the lua file system that corrupts the real time state information read from DCS by Vaicom. This can only be addressed through changes to the DiCE mod.
  6. Do you have the community Hercules mod? To install the old version download the .24 version from the Downloads page on Vaicompro.com and then replace the dll in the Vaicom install folder Sent from my SM-T835 using Tapatalk
  7. I am still trying to investigate with @Hollywood_315 (making no promises about fixes but trying to understand the root cause).
  8. All, It is confirmed there is a conflict, but DiCE is not on the list of mods guaranteed to be compatible with Vaicom (https://forums.eagle.ru/topic/232373-faq/?do=findComment&comment=4256673) Cheers
  9. I have now replicated the DiCE issues (hopefully in a methodical way), and sent the information to @Hollywood_315. I have noticed on my install at least, that the issues only occur on every alternate press of the TX button. I have also found that it still happens even if DiCE.exe is closed down once DCS is running
  10. I am going to try installing DiCE and see what happens on my install
  11. This is a known issue and is already reported
  12. You should just be able to copy the vaicom folder from apps in the old location. I went the other way and did an in-place upgrade of VA 32-bit to 64-bit Sent from my SM-T835 using Tapatalk
  13. What plane are you flying and please could you turn on Vaicom debug, get the problem and then post your Vaicom log file here
  14. It might also be worth asking Bailey if he knows why DiCE might be interfering with Vaicom as well
  15. To the best of my knowledge, the Mi-24 is not officially supported yet in Vaicom. I have found that the module name is picked up if I make a ground start, but not if I make an air start
  16. I don't have SRS installed, but I have just gone in the M2000 and managed to get a response on TX2 (once I had sorted the issue of VA deciding to change the mic device) for approaching to refuel. I have Easy Comms off and tried both with Select...Texaco as the first command and just asking for Approaching for Refuel. I wonder if it is therefore something to do with the way you have the new VOIP control settings set. This is a different issue - you get a response from the nearest tanker (assuming they all have the same base callsign such as Texaco)
  17. There is only one radio in the F-86 so Vaicom will default to using TX1. If you want to use TX2 instead use the up and down arrows next to the LCD display to select TX2.
  18. Try re-adding the TX nodes one by one and see what happens - if the issue happens again we can have a look and see what is happening
  19. OK - could you post your Vaicom config settings and your Vaicom log from the last run (this can be found in <VoiceAttack install directory>\apps\VAICOMPRO\logs)
  20. Do you have DiCE installed? Sent from my SM-T835 using Tapatalk
  21. I cannot help much more apart from to check that your joystick calibration is good in the VKB software - I am sure the early access sight will be further tuned during early access. It would also help if you could post a video showing the degree of drift you are experiencing Sent from my SM-T835 using Tapatalk
  22. I use a VKB as well on the extension - adding some curves should help Sent from my SM-T835 using Tapatalk
  23. Why not use the whole stick as the controller? This is why the Aiming Station is a separate set of control bindings so you can use the joystick to do this and it will have more control than a POV Sent from my SM-T835 using Tapatalk
  24. I have updated fine so it is not a universal issue - if you go to the folder can you delete that file from file explorer?
×
×
  • Create New...