Jump to content

Hollywood_315

Members
  • Posts

    1095
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Hollywood_315

  1. @Zetrocker In SRS Client there's a setting Allow VAICOM TX Inhibit, make sure it's set to ON.
  2. Clearly a MS Windows issue. You could try resetting your desktop theme.
  3. Check your Hide On-Screen Text setting.
  4. Well that's interesting. Not reproducible and not reported elsewhere else either. Assuming there's nothing special about the path of your install and your Windows account has folder R/W access. Suggest to try add an antivirus exception.
  5. Well there are no known stability issues at this time. Confirm you are using VoiceAttack stable (not beta) and for testing make sure no third party apps are interfering e.g. in export.lua Suggest to check dcs.log and test with different modules and different missions, you could be dealing with a corrupted mission file.
  6. The 109 is supported by the plugin. As Lt_Jaeger says, there is a known issue with this module where it does not respond correctly to the ED API commands, specifically LoSetCommand(1591 and 1592). This compatibility error cannot be addressed by the plugin and needs to be solved by the module dev. Probably best to try with Easy Comms ON atm.
  7. No worries. For those that are interested in TARGET stuff let me take this opportunity to recommend the stellar work by @Homefries, make sure to check out this thread here https://forums.eagle.ru/showthread.php?t=116454
  8. There's many ways to go about this. You can e.g. change your TX mapping dynamically to different physical keys in a single profile using the plugins Exposed Variables. Alternatively, you can use different TARGET profiles for different aircraft etc.
  9. First of all do a hard reset of your database by deleting the Config and Database subfolders (you seem to have somehow imported an ATC called '0' which won't help here). Then try using the correct syntax as in the manual i.e. ' Two Five Zero Decimal Zero' and not e.g. 'Zero Zero Zero' as seen in the log. Hope that helps grtz
  10. [sOLVED] https://forums.eagle.ru/showthread.php?t=276120&page=5
  11. Probably something got corrupted in your database somehow, suggest to delete both the Database and Config subfolders and restart VA.
  12. These log entries are benign and unrelated, ED forgot to uncomment a line somewhere. I see this entry too on occasion but everything still works 100% here on the testbench. Just to be clear did you already clear your database with the Reset tab and perform the FINISH steps.
  13. Confirmed, appears to be a recently introduced undocumented change in the module. We'll have a look.
  14. Suggest to keep your voice command simple for basic testing. Run a DCS Repair first: manual lua tweaking is almost guaranteed to cause problems. Then enable Select Tunes Radio and instead of 'Kutaisi 411 request takeoff' try 'Kutaisi..Select' (beeps, tunes radio) followed by a simple 'Ready for Departure' and work from there. This assumes export.lua is cleared form third party entries and VA is running as admin with no antivirus/firewall interfering. If needed inspect DCS.log for further clues.
  15. The log suggests you release TX too soon. Confirm your hotkey is configured as press-and-hold (use keyboard keys 1-6 to test) and hold PTT until command is executed (beeps). Also confirm you have a fresh profile (use Config/export and import .vap in VA) and are not using VSPX.
  16. As hornblower says, you are tuned to a support vessel on the same freq. , not the Supercarrier unit itself. Use e.g. 'Washington, .. Select' to set your dialog to the actual supercarrier.
  17. What hornblower says, if needed get a fresh .vap profile using Config/export and import in VA. Then apply FINISH steps.
  18. It gets created automatically in the same folder as VAICOMPRO.dll. Make sure VA runs as admin.
  19. Suggest to try with what hornblower says, also check with the force language sliders. We'll have a look.
  20. Good one. I wouldn't qualify it as an issue but it's added to the list for next update.
  21. Salute for the F14 was added in 2.5.20 update. Grtz
  22. +++ plugin update 2.5.20 +++ Plugin version 2.5.20 includes compatibility update for DCS 2.5.6 Stable. If needed, run a DCS Repair first. The update includes some minor tweaks and fixes. Also included as a new addition the VAICOMPRO.exe app (see manual page 38 ). Grtz
  23. +++ 2.5.6 to Stable +++ As you will have noticed, DCS World Release moved to 2.5.6 yesterday. A compatibility update for the plugin will become available in the next few days. Thanks
  24. Thanks for the update, good to hear you got it sorted :thumbup:
  25. Can't reproduce: works fine with both easy comms on and off. Grtz
×
×
  • Create New...