michel78320 Posted October 29, 2018 Report Posted October 29, 2018 (edited) Hello,I'm trying to play sounds (some waves) with the library "sounds" to simulate ATC.My lua script works perfectly on the speakers . How can I play the sounds on the headset (palyback device communications)?Indeed it does not appear in the list of devices (file FSUIPC5.ini). My headset is a Senheiser-USB model and works very well with standard ATC. Thank you in advance. Edited October 29, 2018 by michel78320
Pete Dowson Posted October 30, 2018 Report Posted October 30, 2018 I moved your support question to the Support Forum. Please remember to always put support requests here, not into the Reference subforums. You put yours into the User Contributions subforum, where there title indicated that it was some osrt of tutorial on playing sounds. 13 hours ago, michel78320 said: How can I play the sounds on the headset (palyback device communications)? Indeed it does not appear in the list of devices (file FSUIPC5.ini). If it is not in that list then FSUIPC is not seeing it listed as a sound output device in Windows. What devices are listed in Windows sound app? Can you check there? compare that list with FSUIPC's. Pete
michel78320 Posted October 30, 2018 Author Report Posted October 30, 2018 Hello, Thank you, Pete, for that answer.Excuse me for the bad place in the forum. 😕 Here are the devices seen by FSUIPC : [Sounds] Path=M:\P3D-V4-0\Sound\ Device1=Périphérique audio principal Device2=Haut-parleurs (Realtek High Definition Audio) Device3=Realtek Digital Output (Realtek High Definition Audio) Device4=Realtek HDMI Output (Realtek High Definition Audio) Device5=Realtek HD Audio 2nd output (Realtek High Definition Audio) Device6=TripleHead2Go-8 (2- NVIDIA High Definition Audio) Device7=LG ULTRAWIDE-4 (2- NVIDIA High Definition Audio) Here are the devices seen by P3DV4.3 :
Pete Dowson Posted October 30, 2018 Report Posted October 30, 2018 Very strange that FSUIPC doesn't see it. I've not seen a list that long before, so I wonder if it is just some limit FSUIPC is hitting. Checking now ... ... No, it isn't tht ... it allows up to 16. It is using a Windows facility to ennumerate sound devices. I've no idea what is odd about that one that it isn't being seen. Are any others missing? There is some logging which might help me. Please add these two lines to the [General] section of FSUIPC5.INI: Debug=Please LogExtras=32 Do that before running P3D, then after it loads up, terminate it. It won't log a lot of detail, but just the actual ennumeration calls. I might need to add more logging if that doesn't help. Pete
michel78320 Posted October 30, 2018 Author Report Posted October 30, 2018 The concern may be that I have output sound on the motherboard, and another output on the USB port for the headphones.It seems that FSUIPC is satisfied with the motherboard, and does not search on the USB ports. Do you want the log?
Pete Dowson Posted October 30, 2018 Report Posted October 30, 2018 50 minutes ago, michel78320 said: The concern may be that I have output sound on the motherboard, and another output on the USB port for the headphones.It seems that FSUIPC is satisfied with the motherboard, and does not search on the USB ports. It doesn't search at all. It simply lists all the DirectSound devices returned by Windows. That list should always be the same as that provided in the Sound applet in the control panel. Most of my sound devices are on USB sockets and those are listed. 52 minutes ago, michel78320 said: Do you want the log? That was the point of adding those lines. Please, just paste the contents into a message here. It might be tomorrow now before I get to it though. Pete
michel78320 Posted October 30, 2018 Author Report Posted October 30, 2018 Hi again. Here are the statuses of Windows : And I put the log in five minutes.
michel78320 Posted October 30, 2018 Author Report Posted October 30, 2018 By the way, I have windows 7 (64 bits) and P3DV4.3. Logfile = ********* FSUIPC5, Version 5.14 (3rd August 2018) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FED1E00000 Windows 7 Professional 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1) Prepar3D.exe version = 4.3.29.25520 Reading options from "M:\P3D-V4-0\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="Michel SORDOILLET" User Addr="michou78@hotmail.com" FSUIPC5 Key is provided WideFS7 Key is provided 0 System time = 30/10/2018 18:48:14 0 FLT UNC path = "\\GARGAMEL\Users\Michel\Documents\Prepar3D v4 Files\" 0 Using DialogMode 0 FS UNC path = "\\GARGAMEL\P3D-V4-0\" 218 ---------------------- Joystick Device Scan ----------------------- 234 Product= Saitek Pro Flight Rudder Pedals 234 Manufacturer= Saitek 249 Vendor=06A3, Product=0763 (Version 1.0) 249 GUIDs returned for product: VID_06A3&PID_0763: 249 GUID= {921FBE70-A7B4-11DF-8001-444553540000} 249 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 249 Product= Saitek Pro Flight X-55 Rhino Stick 249 Manufacturer= Madcatz 265 Serial Number= G0000041 265 Vendor=0738, Product=2215 (Version 0.87) 265 GUIDs returned for product: VID_0738&PID_2215: 265 GUID= {A9CCC370-8869-11E4-8001-444553540000} 265 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U0,V0,X65535,Y65535,Z0 265 Product= Saitek Pro Flight X-55 Rhino Throttle 265 Manufacturer= Madcatz 265 Serial Number= G0015253 265 Vendor=0738, Product=A215 (Version 0.119) 265 GUIDs returned for product: VID_0738&PID_A215: 265 GUID= {A9CCC370-8869-11E4-8003-444553540000} 265 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255 265 ------------------------------------------------------------------- 265 Device acquired for use: 265 Joystick ID = 2 (Registry okay) 265 2=Saitek Pro Flight Rudder Pedals 265 2.GUID={921FBE70-A7B4-11DF-8001-444553540000} 281 Device acquired for use: 281 Joystick ID = 1 (Registry okay) 281 1=Saitek Pro Flight X-55 Rhino Stick 281 1.GUID={A9CCC370-8869-11E4-8001-444553540000} 281 Device acquired for use: 281 Joystick ID = 0 (Registry okay) 281 0=Saitek Pro Flight X-55 Rhino Throttle 281 0.GUID={A9CCC370-8869-11E4-8003-444553540000} 281 ------------------------------------------------------------------- 296 LogOptions=00000000 00000211 296 Sound: Path=M:\P3D-V4-0\Sound\ 296 ------------------------------------------------------------------- 296 SimConnect_Open succeeded: waiting to check version okay 296 Opened separate AI Traffic client okay 129605 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 132897 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.3.29.25520 (SimConnect: 4.3.0.0) 132897 Initialising SimConnect data requests now 132897 FSUIPC Menu entry added 132897 ... Using Prepar3D with Academic License 132913 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 132913 \\GARGAMEL\Users\Michel\Documents\Prepar3D v4 Files\lfmr.fxml 132913 M:\P3D-V4-Michel\SimObjects\Helicos\nd_ec135\ec135.air 133069 Deactivated for PID=6376, "explorer.exe" 164503 Weather Mode now = Global 165735 \\GARGAMEL\Users\Michel\Documents\Prepar3D v4 Files\LFOL.fxml 170914 Deactivated for PID=6376, "explorer.exe" 170914 Lost focus to PID=6376, "explorer.exe" 286527 Loading Complete ... 287276 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 287276 Aircraft loaded: running normally now ... 287322 User Aircraft ID 2 supplied, now being used 287541 System time = 30/10/2018 18:53:01, Simulator time = 17:03:02 (15:03Z) 287541 Aircraft="EC135 F-GMIC2" 287556 ***** Nearest Airports ***** 287556 Airport1=LFOL, Lat=48.759722, Lon=0.659167, Alt=786.998103, Dist=0.022964 287556 Airport2=2856, Lat=48.614030, Lon=0.840835, Alt=801.699556, Dist=11.334442 287556 Airport3=LFAX, Lat=48.540278, Lon=0.533889, Alt=885.997410, Dist=14.061033 287556 Airport4=LFPD, Lat=49.102778, Lon=0.566667, Alt=553.999390, Dist=20.903002 287556 Airport5=LFFD, Lat=48.897435, Lon=1.250722, Alt=491.000714, Dist=24.806232 287556 Airport6=LFAJ, Lat=48.710556, Lon=0.003889, Alt=580.997436, Dist=26.075323 288274 ***DISP*** Text/menu type 1 broadcast 292283 ***DISP*** Text/menu type 1 clear broadcast 294202 -------------------- Starting everything now ---------------------- 294202 Starting WideServer now ... 294218 Using "M:\P3D-V4-0\Modules\GFDEV64.DLL", version 2.2.8.0 294218 GoFlight GFP8 detected: 1 device 294218 GoFlight GF166 detected: 1 device 294218 GoFlight GFMCP detected: 1 device 294218 GoFlight GFRP48 detected: 1 device 294218 GoFlight GFLGT2 detected: 1 device 294264 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 294264 LUA.0: beginning "M:\P3D-V4-0\Modules\ipcReady.lua" 294327 ***DISP*** Text/menu type 4 broadcast 294374 Advanced Weather Interface Enabled 299428 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 300707 === Closing session: waiting for DLLStop to be called ... 304654 Deactivated for PID=6376, "explorer.exe" 304654 Lost focus to PID=6376, "explorer.exe" 305029 === DLLStop called ... 305029 === Closing external processes we started ... 306027 === About to kill any Lua plug-ins still running ... 306183 === Closing global Lua thread 306183 ***DISP*** Text/menu type 4 clear broadcast 306183 ***DISP*** Text/menu general clear broadcast 307197 === About to kill my timers ... 307400 === Restoring window procs ... 307400 === Unloading libraries ... 307400 === stopping other threads ... 307400 === ... Button scanning ... 307493 === ... Axis scanning ... 307587 === Releasing joystick devices ... 307587 === Freeing macro memory 307587 === Removing any offset overrides 307587 === Closing all WideFS threads 308944 === Clearing any displays left 308944 === NOTE: not calling SimConnect_Close ... 308944 === AI slots deleted! 308944 === Freeing button memory ... 308944 === Deleting wxstationlist.bin file ... 308944 === Closing my Windows ... 308944 === Freeing FS libraries ... 309943 === Closing devices ... 309943 === Closing the Log ... Bye Bye! ... 309943 System time = 30/10/2018 18:53:24, Simulator time = 17:03:14 (15:03Z) 309943 *** FSUIPC log file being closed Minimum frame rate was 19.5 fps, Maximum was 52.1 fps Average frame rate for running time of 12 secs = 38.1 fps Maximum AI traffic for session was 0 aircraft Memory managed: 12 Allocs, 11 Freed ********* FSUIPC Log file closed *********** Thanks for your help.Good night, see you tomorrow. 🙂
michel78320 Posted October 30, 2018 Author Report Posted October 30, 2018 For Loud Speaker : And for USB-Headset :
Pete Dowson Posted October 30, 2018 Report Posted October 30, 2018 57 minutes ago, michel78320 said: Logfile = Strange. There are no entries suggesting it is scanning the sound devices! I''ll do some checking here, tomorrow morning. Meanwhile, could you try deleting the complete sound list from the INI file and see if it is re-generated -- because at present it looks like that is not happening. BTW, not sure what you last pix were about? Pete
michel78320 Posted October 30, 2018 Author Report Posted October 30, 2018 Great, you've found the solution ! 😀 1 hour ago, Pete Dowson said: I''ll do some checking here, tomorrow morning. Meanwhile, could you try deleting the complete sound list from the INI file and see if it is re-generated -- because at present it looks like that is not happening. As suggested, I deleted the sound section. After launch of P3D, I have a new sound section : [Sounds] Path=M:\P3D-V4-0\Sound\ Device1=Périphérique audio principal Device2=Haut-parleurs (Realtek High Definition Audio) Device3=LG ULTRAWIDE-4 (NVIDIA High Definition Audio) Device4=TripleHead2Go-0 (NVIDIA High Definition Audio) Device5=Haut-parleurs (3- Sennheiser USB headset) Here is the corresponding log : 281 ------------------------------------------------------------------- 297 LogOptions=00000000 00000211 297 Sound: Path=M:\P3D-V4-0\Sound\ 297 Sound: EnumDevice=Périphérique audio principal 297 Sound: EnumDevice=Haut-parleurs (Realtek High Definition Audio) 297 Sound: EnumDevice=LG ULTRAWIDE-4 (NVIDIA High Definition Audio) 297 Sound: EnumDevice=TripleHead2Go-0 (NVIDIA High Definition Audio) 297 Sound: EnumDevice=Haut-parleurs (3- Sennheiser USB headset) 297 ------------------------------------------------------------------- Now I can send the sounds to the headset. 🙂 Many thanks, Pete.
Pete Dowson Posted October 31, 2018 Report Posted October 31, 2018 14 hours ago, michel78320 said: Now I can send the sounds to the headset. Good. So it looks like FSUIPC is not scanning for sound devices if it has a list already. I'll fix that in for the next release. Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now