Jump to content

hornblower793

Members
  • Posts

    1785
  • Joined

  • Last visited

Everything posted by hornblower793

  1. Yes you should just be able to move the folders. I would definitely place on a different SSD to your operating system. I now used a 1TB SSD (trying to slightly future-proof)
  2. This is an issue in 2.7 that others have been experiencing and we have been busy chasing. It will need an update to resolve
  3. When training, make sure you set the Windows speech engine to recognise non native accents - this may also help you Sent from my SM-T835 using Tapatalk
  4. Indeed - we are just more advanced newbies
  5. A known issue with 2.7 at the moment - @Hollywood_315will be release a new version once 2.7 has settled down
  6. The best way to do what you want is to train them using Microsoft speech and adding to its recognition dictionary. To start this just type speech into the Windows search bar, open the Windows Speech Recognition app and then right click on the microphone that appears to access the speech dictionary
  7. Mine was 2D yesterday - i was trying to trigger crashes while watching what was happening. As with most people here it didn't happen every time Sent from my SM-T835 using Tapatalk
  8. I also had this yesterday Sent from my SM-T835 using Tapatalk
  9. Is easy comms being forced on by the server? What happens if you fly a SP mission in the F18 - does it work as expected? Sent from my SM-T835 using Tapatalk
  10. Select [AM; FM;] [0..3] [0..9] [0..9] decimal [0..9] [0; 2 5; 5 0; 7 5;] is the command that should be in the VA Vaicom profile list In use this would be something like Select FM 2 5 1 . 5 5 0 to tune to 251.550 MHz FM (I would say this as Select FM 2 5 1 dot 5 5 oh) I don't really use this command so can't say how easy it is to get it to work. Will try and remember to test next time I fly
  11. https://discord.gg/aWqRWfzZ It is largely the same helpers on the Discord as here Sent from my SM-T835 using Tapatalk
  12. Someone on Discord had that - I think it is using 1. 2. etc - rename them to D1, D2 and you should be good to go
  13. Sounds like Easy Comms might be on The Kneeboard is a bookmarked page on the in-game kneeboard and not a separate app What exactly are you seeing and in which plane(s)
  14. Try semding an email to support@vaicompro.com @Hollywood_315 might be able to solve the issue but that is also the formal channel for requests like this Sent from my SM-T835 using Tapatalk
  15. I have experienced using both my Oculus Rift S and pancake with the VR disabled
  16. Might be worth dropping @IronMike or @fat creason a PM Sent from my SM-T835 using Tapatalk
  17. I also thought that, but then had it happen yesterday when I just used the F-18. I then quit, went back in and it worked happily Sent from my SM-T835 using Tapatalk
  18. We have a wide range of GPUs both AMD and NVidia - mine is a ROG 2060 Super so should be fine
  19. Alternatively open the miz file in the Mission Editor and change your plane from the A10c to the A10c II and save it
  20. Don't worry - we are all noobs, it is just that some of us are more advanced noobs[emoji16] Sent from my SM-T835 using Tapatalk
  21. It does - that is how I tend to get my crashes - I think the .bin file is more an indication to the developers of when in the process the issue is happening
  22. Aren't we all, but short of getting a dev build or full debug build on a problem machine I don't what else we can do - takes me back to my time leading development teams building mission critical systems for police and airport clients where some of the 'features' took months to track down Sent from my SM-T835 using Tapatalk
  23. @Devastator - i think from our earlier conversations you said that you didn't use the SRS integration inside Vaicom. How do you have your system set up to do this? Does Vaicom work as expected in Single Player mode? If not, if you comment out the SRS line in your Export.lua does it then work? Sent from my SM-T835 using Tapatalk
  24. @MAXsenna I think from the earlier conversation on this that the issue is not with the TX buttons - the VA / Vaicom log shows the correct TX being used to issue the command, but the comms are only happening on one channel (so TX1 even if Vaicom is showing TX2 being used). I think there is some SRS conflict going on since Devastator has a screenshot of a message appearing top right which is to do with the channel players are tuned to, and then the problems start - other people have stated they think this is an SRS message (it could also be VoiceChat but I think Devastator said he had this disabled). This definitely sounds like some kind of conflict, but working out what is causing it is fun (especially as I have never used SRS so not looked into how to setup and use it)
×
×
  • Create New...