Jump to content

hornblower793

ED Closed Beta Testers Team
  • Posts

    1628
  • Joined

  • Last visited

Everything posted by hornblower793

  1. I am going to try installing DiCE and see what happens on my install
  2. This is a known issue and is already reported
  3. 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
  4. What plane are you flying and please could you turn on Vaicom debug, get the problem and then post your Vaicom log file here
  5. It might also be worth asking Bailey if he knows why DiCE might be interfering with Vaicom as well
  6. 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
  7. 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)
  8. 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.
  9. 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
  10. 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)
  11. Do you have DiCE installed? Sent from my SM-T835 using Tapatalk
  12. 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
  13. I use a VKB as well on the extension - adding some curves should help Sent from my SM-T835 using Tapatalk
  14. 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
  15. 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?
  16. Interesting - I will try mine again later with the new patch but had the sight rock steady last time I tried UPDATE - I have now tried and can get it steady if I use my joystick without any curves or deadzone (it takes very gentle movements when moving slowly to do this). However, adding curves to it made it easier to get it steady. The same goes for both the mouse and the mini-stick I have (it is the Deltasim mod on my Warthog Throttle). For these I set the curves on each axis to 100 for the mini-stick and 25 for the mouse. The mouse is definitely the trickiest to use for me but then I haven't spent a lot of time tuning it because I will never use this method of control
  17. You will either have to write your own commands or download a profile - Bailey produces some very good ones (search the forums for Bailey profiles). You can then either daisychain this profile to Vaicom or vice versa. To do this pick the profile you want to be top in VA, click on the pencil icon and then on the edit profile button (next to the profile name) on the next screen. On the window that appears there should be an 'include commands from these profiles' option - use this to add the other profile(s) you want loaded at the same time Sent from my SM-T835 using Tapatalk
  18. Please could you post your Vaicom log file from a session where you have an issue. That will allow us to see if there are any clues Sent from my SM-T835 using Tapatalk
  19. Sounds more like a VA issue to me - I had a few funnies from the last VA update Sent from my SM-T835 using Tapatalk
  20. I will have a look at Baileys profile later and see what I can find - is Vaicom the top profile or the daisy-chained one? Sent from my SM-T835 using Tapatalk
  21. 2.5.6 was the exception because of the major performance issues it introduced. I would say the gap this time was far more normal Sent from my SM-T835 using Tapatalk
  22. Which profile(s) do you have daisy-chained and I will see if I can replicate. I have my own profile daisy-chained and have not had any issues with that. The message looks like one of the commands has the option to allow other commands to take place while it is processing turned off Sent from my SM-T835 using Tapatalk
  23. I don't think so. The .3 update was to resolve the listening suspended issue some users were encountering Sent from my SM-T835 using Tapatalk
  24. @MAXsenna is right - the aiming station is a separate set of controls (like most modules have game and sim profiles). If drift is an issue I think you can solve it by adding a deadzone to the axis mappings for the Aiming Station Sent from my SM-T835 using Tapatalk
  25. I didn't go for a flight last night, but sitting on the runway was a perfect (and instant) response from the tower Sent from my SM-T835 using Tapatalk
×
×
  • Create New...