Connected to Pilot Edge voice disabled

Connected to Pilot Edge voice disabled

Postby RiverFlow » Sun Sep 22, 2019 4:49 pm

I have searched the forums, but the solutions don't work for me. New user. When I activate the Plugin, I get 'connected to Pilot Edge, voice disabled'.

I can hear the plane and myself speak in the headset. I have aircraft sounds (stock C172).

My microphone / headset is plugged into the back of my computer - is this an issue?

Any other checks?
RiverFlow
 
Posts: 3
Joined: Sun Sep 22, 2019 4:29 pm

Re: Connected to Pilot Edge voice disabled

Postby Keith Smith » Mon Sep 23, 2019 1:57 pm

This occurs if the plugin isn't able to open the input or playback device at the time the sim is loaded up (PRIOR to connecting to xplane). So, step 1....make sure everything is plugged in and then fire up the sim and connect to PE.

If that's failing, then post the contents of your PilotEdge_out.txt file and we'll try to work through it.
Keith Smith
 
Posts: 9865
Joined: Sat Oct 09, 2010 8:38 pm
Location: Pompton Plains, NJ

Re: Connected to Pilot Edge voice disabled

Postby RHD » Tue Mar 31, 2020 3:27 pm

Keith Smith wrote:This occurs if the plugin isn't able to open the input or playback device at the time the sim is loaded up (PRIOR to connecting to x plane). So, step 1....make sure everything is plugged in and then fire up the sim and connect to PE.

If that's failing, then post the contents of your PilotEdge_out.txt file and we'll try to work through it.


Keith,
I am having a no-go with the Oculus Rift-S. Before I send you logs out of nowhere I wanted to learn if anything here has changed with regard to methods to try to get this working?
I have tried various iterations of making the Oculus:
-Default device
-Default Communication device Mic, use with and without playback enabled
-Use of Oculus virtual device
Of course Windows allows for separate definitions of both the "Playback" and "Recording" devices, headphones and Mic respectively.

I have also searched the boards and there appears to be no concrete way to get this working.

All said, how can I help? I seem to have some extra time lately to help out should PE need it?
Regards,
Ross
RHD
 
Posts: 6
Joined: Thu Mar 26, 2020 9:05 am

Re: Connected to Pilot Edge voice disabled

Postby uncertifiedpilot » Wed Apr 01, 2020 2:06 pm

Oculus Rift S is working fine on me end, for some time now.

Tried to help my father today setting up PE and using the Rift S too but ran into similar issues like described above. Seems unrelated to PE though (so please share the log for Keith to take a look at). Also, do not use the oculus virtual device but the 'Headset Rift S' one (I disabled all audio devices, including the virtual one, except this one).

We'll retry tomorrow and report our fix.
I use flight simulator to get Instrument Rated: www.uncertifiedpilot.com
Join my live streams on Twitch
Watch my previous flights on YouTube
uncertifiedpilot
 
Posts: 88
Joined: Sun Jan 18, 2015 4:50 am
Location: Netherlands

Re: Connected to Pilot Edge voice disabled

Postby RHD » Wed Apr 01, 2020 2:13 pm

uncertifiedpilot wrote:Oculus Rift S is working fine on me end, for some time now.

Tried to help my father today setting up PE and using the Rift S too but ran into similar issues like described above. Seems unrelated to PE though (so please share the log for Keith to take a look at). Also, do not use the oculus virtual device but the 'Headset Rift S' one (I disabled all audio devices, including the virtual one, except this one).

We'll retry tomorrow and report our fix.


What did you do with the ORift mic settings?
What have you set to default devices?
Did you check or Uncheck “allow application to use exclusively on the two devices (headset and mic)?

Before bugging Keith let’s see if we can’t troubleshoot this along and come up with some similar settings that work and don’t work?
Ross
RHD
 
Posts: 6
Joined: Thu Mar 26, 2020 9:05 am

Re: Connected to Pilot Edge voice disabled

Postby RHD » Wed Apr 01, 2020 5:38 pm

Keith Smith wrote:This occurs if the plugin isn't able to open the input or playback device at the time the sim is loaded up (PRIOR to connecting to xplane). So, step 1....make sure everything is plugged in and then fire up the sim and connect to PE.

If that's failing, then post the contents of your PilotEdge_out.txt file and we'll try to work through it.


Hi Keith,
I am not the OP of this thread however we both appear to be having the same issue now so I can stay here or start a new thread?
I have attached the requested file.

As a starting point to troubleshoot I have done the following:

-I have uninstalled the Rift
-Clean reboot
-I have disabled ALL sound devices on the computer other than the Rift
-I reinstalled the Rift software

I then restarted Xplane and PE and verified that te PE software device is set to the Rift-S
I can hear PE traffic
The mic is not "hearable" by anyone and there appears to be no output from the Rift mic on the test levels of Windows.

Let me know how you wish for me to proceed.

1..JPG
1..JPG (61.14 KiB) Viewed 2072 times


3.JPG
3.JPG (79.24 KiB) Viewed 2072 times


PilotEdge_out.txt text below...
(many lines of "falling behind" deprecated due to charter count restriction

Ross

Starting up: PilotEdge client, V1.5.3
initVoice with device {0.0.0.00000000}.{0a069b4b-1bd8-429c-ba51-f8ef433113bb}, returned 0
PilotEdge initialized
Entered deferred startup
completed deferred startup
Setting up connection details...
Checking for slaves...
Checking for server file...
Checking for voice service file...
looking for C:\Users\Ross\Desktop\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP Skyhawk REP\PE_voltage.txt
looking for C:\Users\Ross\Desktop\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP Skyhawk REP\PE_groundspeed.txt
looking for C:\Users\Ross\Desktop\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP Skyhawk REP\PE_com_selector.txt
looking for C:\Users\Ross\Desktop\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP Skyhawk REP\PE_com1_frequency.txt
Connecting N5218F with ICAO type: C172
Connected to PilotEdge Server
Connected to PilotEdge Voice
Sent voice ids to server: 160,161
Checking for traffic relay file...
COM2 is now considered to be off
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.354790, PI->time 127.386017, proposed time 133.568169, delta = -6.182153
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.326591, PI->time 127.386017, proposed time 133.555229, delta = -6.169213
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.421716, PI->time 127.386017, proposed time 133.621667, delta = -6.235651
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.429046, PI->time 127.386017, proposed time 133.649505, delta = -6.263489
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.403270, PI->time 127.386017, proposed time 133.610790, delta = -6.224773
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.398611, PI->time 127.502017, proposed time 133.605276, delta = -6.103260
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.472953, PI->time 127.502017, proposed time 133.674857, delta = -6.172841
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.414544, PI->time 127.502017, proposed time 133.622796, delta = -6.120780
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.410453, PI->time 127.502017, proposed time 133.625785, delta = -6.123769
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.504443, PI->time 127.503017, proposed time 133.732714, delta = -6.229698
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.483936, PI->time 127.503017, proposed time 133.717823, delta = -6.214807
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.510343, PI->time 127.504017, proposed time 133.710294, delta = -6.206278
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.432183, PI->time 127.504017, proposed time 133.651421, delta = -6.147405
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.465284, PI->time 127.504017, proposed time 133.679151, delta = -6.175134
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.568169, PI->time 127.716017, proposed time 133.780083, delta = -6.064067
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.555229, PI->time 127.716017, proposed time 133.785209, delta = -6.069193
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.621667, PI->time 127.716017, proposed time 133.863610, delta = -6.147594
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.649505, PI->time 127.716017, proposed time 133.870941, delta = -6.154925
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.610790, PI->time 127.716017, proposed time 133.824169, delta = -6.108152
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.605276, PI->time 127.716017, proposed time 133.818655, delta = -6.102639
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.674857, PI->time 127.716017, proposed time 133.880912, delta = -6.164896
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.622796, PI->time 127.716017, proposed time 133.828484, delta = -6.112468
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.625785, PI->time 127.717017, proposed time 133.843558, delta = -6.126542
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.710294, PI->time 127.717017, proposed time 133.937101, delta = -6.220085
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.732714, PI->time 127.717017, proposed time 133.962694, delta = -6.245678
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.717823, PI->time 127.717017, proposed time 133.952686, delta = -6.235670
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.651421, PI->time 127.717017, proposed time 133.868218, delta = -6.151202
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.679151, PI->time 127.717017, proposed time 133.891065, delta = -6.174048
falling behind, solidering on with ptime: track count 20, prevTrack->time 133.780083, PI->time 127.717017, proposed time 133.994927, delta = -6.277911
falling behind, solidering on with ptime: track count 8, prevTrack->time 139.175406, PI->time 137.222280, proposed time 139.455679, delta = -2.233399
falling behind, solidering on with ptime: track count 9, prevTrack->time 139.455679, PI->time 137.222280, proposed time 139.746695, delta = -2.524415
falling behind, solidering on with ptime: track count 10, prevTrack->time 139.746695, PI->time 137.222280, proposed time 140.023062, delta = -2.800782
falling behind, solidering on with ptime: track count 11, prevTrack->time 140.023062, PI->time 137.222280, proposed time 140.298453, delta = -3.076173
falling behind, solidering on with ptime: track count 12, prevTrack->time 140.298453, PI->time 137.222280, proposed time 140.576773, delta = -3.354493
falling behind, solidering on with ptime: track count 13, prevTrack->time 140.576773, PI->time 137.222280, proposed time 140.864859, delta = -3.642579
falling behind, solidering on with ptime: track count 14, prevTrack->time 140.864859, PI->time 137.222280, proposed time 141.143179, delta = -3.920899
falling behind, solidering on with ptime: track count 15, prevTrack->time 141.143179, PI->time 137.222280, proposed time 141.419546, delta = -4.197266
falling behind, solidering on with ptime: track count 16, prevTrack->time 141.419546, PI->time 137.222280, proposed time 141.704702, delta = -4.482422
falling behind, solidering on with ptime: track count 17, prevTrack->time 141.704702, PI->time 137.222280, proposed time 141.991811, delta = -4.769531
falling behind, solidering on with ptime: track count 18, prevTrack->time 141.991811, PI->time 137.222280, proposed time 142.267202, delta = -5.044922
falling behind, solidering on with ptime: track count 19, prevTrack->time 142.267202, PI->time 137.223280, proposed time 142.543569, delta = -5.320289
falling behind, solidering on with ptime: track count 20, prevTrack->time 142.543569, PI->time 137.223280, proposed time 142.840444, delta = -5.617164
falling behind, solidering on with ptime: track count 20, prevTrack->time 142.840444, PI->time 137.223280, proposed time 143.108999, delta = -5.885719
falling behind, solidering on with ptime: track count 20, prevTrack->time 143.108999, PI->time 137.223280, proposed time 143.391226, delta = -6.167946
RHD
 
Posts: 6
Joined: Thu Mar 26, 2020 9:05 am

Re: Connected to Pilot Edge voice disabled

Postby uncertifiedpilot » Thu Apr 02, 2020 1:23 am

Update: Resolved – Updated my father’s motherboard (and audio) drivers solved the issue.
I use flight simulator to get Instrument Rated: www.uncertifiedpilot.com
Join my live streams on Twitch
Watch my previous flights on YouTube
uncertifiedpilot
 
Posts: 88
Joined: Sun Jan 18, 2015 4:50 am
Location: Netherlands

Re: Connected to Pilot Edge voice disabled

Postby Keith Smith » Thu Apr 02, 2020 3:40 am

RHD,

Make sure the mic isn't muted. The fact that the levels aren't moving when you're speaking indicates that no signal is coming in. Additionally, make sure your PTT is configured correctly (ie. mapped to Contact ATC). You can test the PTT by holding it down briefly while listening to the PE ATIS on the same radio that you're transmitting from (typically COM1). If the ATIS cuts out while you're holding PTT, then the PTT itself is functional.
Keith Smith
 
Posts: 9865
Joined: Sat Oct 09, 2010 8:38 pm
Location: Pompton Plains, NJ

Re: Connected to Pilot Edge voice disabled

Postby RHD » Thu Apr 02, 2020 10:07 am

Hi All-
In the event someone should have the same issues as me, the following got everything working:
1. As above reinstall motherboard audio drivers for a clean start.
2. Uninstall/Reinstall Oculus
3. Plug a headset or Mic and Speaker into the computers built in audio ports to activate your audio driver. If you do not do this, your basic audio services will not install/enable with ONLY an Oculus, as the only audio device the computer has ever had...
4. I disabled the Virtual Audio Mic

Finally,
I suspect this is actually what the issue was but given the order I troubleshot I am not sure and don't care to work it backward...

5. ***Correction*** Unplug the Oculus, reinstall drivers, plug back and and reconfigure Oculus.

That should do it.

Hope it helps in the future...
Regards,
Ross
RHD
 
Posts: 6
Joined: Thu Mar 26, 2020 9:05 am

Re: Connected to Pilot Edge voice disabled

Postby Keith Smith » Thu Apr 02, 2020 7:52 pm

That.....is terrifying.
Keith Smith
 
Posts: 9865
Joined: Sat Oct 09, 2010 8:38 pm
Location: Pompton Plains, NJ

Next

Return to X-Plane

Who is online

Users browsing this forum: No registered users and 4 guests