Jump to content

Jonathan Clayton 1408711

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. WE should be thanking YOU, Justin, for all of the time & effort that goes into creating, developing, and supporting this product, which we all use completely free of charge and ad-free. People need to remember that part of the implicit agreement when you use a software product in Beta Testing phase is that you report issues and bugs in a helpful manner, to [Mod - Happy Thoughts]ist the developer in improving their product before it goes into "official" release. Hopefully the users in this forum will keep that perspective. I echo Robert. I can't imagine the time you are spending on t
  2. Happy to help! Thanks to you and your team for this awesome product and software and the time you guys put into this.
  3. So I think I have it figured out (and it was completely user error on my part). I'll explain: I use VoiceMeeter Potato (to allow me to have multiple audio sources from two computers that are networked). It works well, but it is complicated to set up. When I set up xPilot, when I selected the audio input/output, I thought it best to select my USB headset as the mic source and the output source since that's what I use when I fly. In my mind, byp[Mod - Happy Thoughts]ing the complicated VoiceMeeter input/output settings made sense (even though this USB headset was also a input/output sour
  4. Still no joy. It's funny because xPilot is shown under the apps that accessed the microphone - but the last access date was the day that I installed it. It recognized the mic and the peak meter was working. Since then, I have been getting the same error message, and while the mic is recognized in the dropdown menu, it no longer registers on the peak meter and the application will not connect to the voice server. Out of curiosity, can you try the standalone AFV app and see if you have the same problem? You're on to something - I had the same result. I got a (JIT) dialog box with the same
  5. Still no joy. It's funny because xPilot is shown under the apps that accessed the microphone - but the last access date was the day that I installed it. It recognized the mic and the peak meter was working. Since then, I have been getting the same error message, and while the mic is recognized in the dropdown menu, it no longer registers on the peak meter and the application will not connect to the voice server.
  6. I have checked all that and I do have the Media pack. My error seems to be unrelated. It is still causing issues and I have not yet successfully connected to the voice network. I haven't seen a response from any developers, so I might move back to xSquawkBox or Swift - so that I can start flying again. Please remember that us developers are doing this on our free time. We don't get paid for doing this work. Bashing us developers for lack of response (especially when it hasn't even been a full 24 hours since your original post) is a bit absurd. Needless to say, we have our hands quite
  7. I have checked all that and I do have the Media pack. My error seems to be unrelated. It is still causing issues and I have not yet successfully connected to the voice network. I haven't seen a response from any developers, so I might move back to xSquawkBox or Swift - so that I can start flying again.
  8. Hi there - thanks so much for this software. I am having trouble connecting to the voice server. I am able to connect to VATSIM and read texts in xPilot, but I am getting the following error message: Error starting voice server connection: Exception from HRESULT: 0x8889000A I am wondering if that's an AFV issue or an issue with my client? Thank you EDIT: I am using version 1.1.0.1
×
×
  • Create New...