Jump to content

Greyman

Members
  • Posts

    1255
  • Joined

  • Last visited

Everything posted by Greyman

  1. Maybe check your anti-virus software, to make sure that the missing file has not been quarantined
  2. According to Chuck's Guide, it's in the centre of the Pilot's HSD and is the bottom number.
  3. https://forums.eagle.ru/showpost.php?p=4311067&postcount=5 Read what the linked FAQ says about "blinking menus", as that appears to be the issue you are experiencing. The fix will probably also fix your apparently reversed disable menus option.
  4. That option had to be provided, mainly for TM WH HOTAS users. The TDC control on the Warthog throttle didn't like to be pushed and moved around at the same time, so this option makes it behave like the one in the A10C module.
  5. also, as per the FAQ, for general unexpected behaviour, make sure you are still running VA as admin and that you don't have any Garmin mods activated in DCS.
  6. If that doesn't help you, if you Google "Windows 10 speech recognition won't work", there appear to be a fair few people that have had what look like similar issues and there are quite a few suggested and apparently successful fixes.
  7. What if you type "speech recognition" into the Windows 10 search box and then select the app that results in? Hmmm, https://answers.microsoft.com/en-us/windows/forum/all/windows-10-speech-recognition-wont-start/ec6c690c-8486-4179-b6f2-929070231d9c might be worth a look.
  8. I'm fairly sure that VP doesn't send anything to DCS until it detects the PTT being released.
  9. Yes, i now understand, but whether and when it can be done is a question, that I guess only Hollywood_315 will be able to answer.
  10. For Case 1, there is a fair amount of text that describes the communications and when they should take place. For Case 2 and Case 3, the respective diagrams include indications of when to make the various calls over ATC. Maybe take another look
  11. Will it possibly provide at least a starting heading for a Harpoon, as ships might be easier to spot on the radar?
  12. Thanks and it looks like it was worth me checking. :)
  13. Sorry if this one has already been asked and answered, but looking at the diagram for a Case II recovery, from the SC manual, which is apparently a mixture of a Case III holding pattern and a Case I approach, it isn't clear what the speed should be at the start of the Case I phase. In a normal Case I, the speed requirement leading up to the break is 350kts, yet the descent from the holding stack, in a Case II recovery, is at 250kts. Should the break be started at 250kts, or should the aircraft be accelerated to 350kts before the break? My guess is the former, but I thought I'd check.
  14. Unless the launching aircraft identifier is added, as a prefix/suffix to the station number, unseen to the pilot.
  15. Vaicom Pro already automatically selects the most appropriate PTT buttons for each aircraft. For example, the Hornet just uses 2 of the PTT buttons (forward and down for radio 1 and radio 2 respectively on a WH HOTAS). The other PTT buttons are disabled. For the example above, are you suggesting that this might be changed so that you would be able to press different buttons for the two radios, than you might for any other aircraft with the same 2 PTT mappings or would you be happy with the aircraft specific defaults that VP already selects?
  16. maybe check out nvidia's AI noise reduction software. it should be available to your RTX GPU. Apparently, it's really effective for cancelling out the background noise for mics
  17. \o/\o/ Nice one \o/\o/ Now get to something relatively easy. AAR and Case 1, 2 and 3 recoveries in the Navy jet of your choice should be a breeze now. :) Good job gurus
  18. Unless you fly in a very quiet room and don't "grunt" like i do when in the heat of battle, a hot mic might throw up some unwanted and apparently random commands. The Nvidia noise cancelling utility, on the RTX cards might offer some help on this, or at least i hope it does.
  19. when you tried VSPX, did you reset all of the necessary settings, to make sure that you are not stuck somewhere between the two modes? From the manual:- Switching Between Modes To change between Default and VSPX modes, follow these steps: • In Preferences, (de)select VSPX option: you will see a pop-up. Press OK. • Follow the FINISH steps in the keywords editor to update your VA profile, • In VoiceAttack options put these settings as follows: Unrecognized Speech Delay VSPX OFF: 0ms. VSPX ON: 600-1000ms: 700ms recommended. Done. The green light on the editor page shows whether VSPX is activated.
  20. If you load something like notepad, alongside speech recognition, and say the Chinese version of "Batumi", does it appear as text in notepad?
  21. and maybe block "GTECH" in speech recognition, as that might be a word that you never want to use anyway.
  22. If it's the request for aerial refueling that you want to add an alias to, then you need to add the alias to "approaching for refuel", but if you use a word that is already used for another command, then VA is very likely to choose that command before using your alias.
  23. That's probably because "request refuel", as sthompson says, has already been allocated for asking the ground crew to refuel you, with Weight on Wheels, making this unworkable when at say 20,000ft. Maybe try "fill her up", "do you give stamps?" or probably something a little more sensible. :)
  24. Here's another one. Do you have the 2 sliders at the bottom right of the CONFIG tab set to match your standalone and stable environment?
  25. Sorry for clutching at straws a little, but better than not checking it and then finding out way later. :)
×
×
  • Create New...