Plugin Not Working Correctly

Casimir
Posts: 26
Joined: Sat May 19, 2018 9:14 pm
Location: KOLV

Re: Plugin Not Working Correctly

Post by Casimir »

RogerW wrote:I'm not the expert on this but I believe the headset is set as default communication device not default output device.
Good luck!
Right - in the Oculus Rift though it has a built-in microphone as well as the headphones, so the settings for both point at the same device.

Speaking of that though, I did try to move the sound in PE into my other headphones while trying to troubleshoot this, just to see if it was an issue with the Oculus. Same issue - no ATC out of those other headphones either.
Cessna N5351E (A2A C172 / REP XPlane 11 C172)
Piper N5351A (Carenado Seneca V)
wrs2
Posts: 5
Joined: Fri May 22, 2020 3:02 pm

Re: Plugin Not Working Correctly

Post by wrs2 »

I am suddenly getting a "voice disable" when I connect to PE plugin. I can hear the ATIS from Xplanwe and microphone works for other plugins namely "planecommand". I will note that Windows 10 performed an update last night. I checked the PE preferences and had to change the audio to my Logitech 540 headset. I see comments about having the headset connected before starting Xplane and or the PE plugin. I checked the Windows setting for sound and all is working. I am including my PE_out.txt below. Could not include it as an attachment. Appreciate guidance to resolve this. WRS2

Starting up: PilotEdge client, V1.6.3
initVoice: playback device: {0.0.0.00000000}.{d0e7bbe7-487d-4cb4-bb5f-303991d1c79f}, capture device: {0.0.1.00000000}.{dcef1b35-4ff3-4c69-965b-39f88929b42e}
initVoice returned 2321
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:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_voltage.txt
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_groundspeed.txt
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_com_selector.txt
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_com1_frequency.txt
Connecting N15WS with ICAO type: C172
Connected to PilotEdge Server
Checking for traffic relay file...
COM1 is now considered to be off
Prefs: error getting current capture device, error #1
Prefs: error getting current playback device, error #1
VSProClient: disconnect() entered
MessageController::sendMsg entered: msg = QUIT
status = 37
VSProClient: sent bye
VSProClient: signalled controller entered
VSProClient: connection closed
MessageController exiting
VSProClient: disconnect() complete
Setting up connection details...
Checking for slaves...
Checking for server file...
Checking for voice service file...
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_voltage.txt
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_groundspeed.txt
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_com_selector.txt
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_com1_frequency.txt
Connecting N15WS with ICAO type: C172
Connected to PilotEdge Server
Checking for traffic relay file...
COM1 is now considered to be off
VSProClient: disconnect() entered
MessageController::sendMsg entered: msg = QUIT
status = 37
VSProClient: sent bye
VSProClient: signalled controller entered
VSProClient: connection closed
track count: 20, prevTrack->time 348.991655, PI->time 349.229799, proposed time 349.203081, delta = 0.026717
MessageController: done
MessageController exiting
VSProClient: disconnect() complete
Setting up connection details...
Checking for slaves...
Checking for server file...
Checking for voice service file...
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_voltage.txt
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_groundspeed.txt
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_com_selector.txt
looking for C:\X-Plane 11\Aircraft\Laminar Research\Cessna 172SP\PE_com1_frequency.txt
Connecting N15WS with ICAO type: C172
Connected to PilotEdge Server
Checking for traffic relay file...
COM1 is now considered to be off
VSProClient: disconnect() entered
MessageController::sendMsg entered: msg = QUIT
status = 37
VSProClient: sent bye
VSProClient: signalled controller entered
VSProClient: connection closed
MessageController exiting
VSProClient: disconnect() complete
Keith Smith
Posts: 9939
Joined: Sat Oct 09, 2010 8:38 pm
Location: Pompton Plains, NJ
Contact:

Re: Plugin Not Working Correctly

Post by Keith Smith »

Delete your VSProSound.ini from the PilotEdge\VSPro Resources folder. The windows update likely altered the signature of your audio drivers (this never used to be a thing...now suddenly it's a thing in windows 10), rendering the plugin slightly lost with regards to the previous devices that it swore were there.

I'm going to update the plugin when I can to better handle this case.
wrs2
Posts: 5
Joined: Fri May 22, 2020 3:02 pm

Re: Plugin Not Working Correctly

Post by wrs2 »

Thanks for the assistance. I deleted the INI sound file and now the PE sound is back online for me. That resolved the issue. Will keep that in mind following future Windows10 updates. WRS2
Post Reply