Jump to content
The simFlight Network Forums

michel78320

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About michel78320

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Paris (France)

Recent Profile Visitors

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

  1. Great, you've found the solution ! 😀 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.
  2. For Loud Speaker : And for USB-Headset :
  3. 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. 🙂
  4. Hi again. Here are the statuses of Windows : And I put the log in five minutes.
  5. 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?
  6. 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 :
  7. 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.
  8. michel78320

    MCP (CPFLIGHT) and LUA

    Thank you for this quick response. I apologize, I would of course have to start by verifying that a new version was not released. I just installed the new version. Actually com.write works. All is OK ! I can now write a Lua script to drive my MCP. Your product is just great. Thank you very much.
  9. Hello, I am a registered user of FSUIPC and WIDEFS for 11 years, and I thank Pete very much for this extremely complete software. The operation of WideFS is still operational with P3D-V4. Bravo. I bought an FSUIPC5 key as soon as it was available, and everything works perfectly with P3D-V4. Now, here is my problem : I own an MCF + EFIS from CPFlight. It worked perfectly with the supplied driver, as well as the (Expensive) software from FS-Labs. Unfortunately , the FS-Labs software is a 32 bits version, and there is no planned version for compatibility with P3D-V4. So I looked for another solution, and by reading the important documentation provided with FSUIPC, I discovered that there was everything necessary to direct control for my hardware. So I started using LUA plug-ins, helped by the many examples provided. Great job, Pete ... Very well explained and very complete. Unfortunately, I am not able to make a simple com.write () ... I run P3D-V4 with the following LUA script, associated with a keyboard key ("A") : MCP-747.lua : ----------------------------------------------- -- Commande du MCP-747 de CP-Flight avec LUA ----------------------------------------------- speed = 38400 -- Vitesse du port USB handshake = 0 -- No handshake MCP = com.open("com6", speed, handshake) if MCP == 0 then ipc.log("Pas trouvĂ© de MCP-747 de CP-Flight") ipc.exit() end ipc.log("Port USB ouvert") n = com.write (MCP, "Q001") ipc.log(n) When I execute the script ("A" key from the keyboard), the LLUA log (MCP747.log) gives this: ********* LUA: "MCP-747" Log [from FSUIPC version 5.101] ********* 256825 System time = 21/06/2017 11:42:37, Simulator time = 14:44:36 (12:44Z) 256825 LUA: beginning "M:\P3D-V4-0\Modules\MCP-747.lua" 256825 LUA: M:\P3D-V4-0\Modules\MCP-747.lua:5 256825 LUA: Global: ipcPARAM = 0 256825 LUA: M:\P3D-V4-0\Modules\MCP-747.lua:6 256825 LUA: Global: speed = 38400 256825 LUA: M:\P3D-V4-0\Modules\MCP-747.lua:8 256825 LUA: Global: handshake = 0 256903 LUA: M:\P3D-V4-0\Modules\MCP-747.lua:10 256903 LUA: Global: MCP = 5029216692 256903 LUA: M:\P3D-V4-0\Modules\MCP-747.lua:15 256903 LUA: Port USB ouvert 256903 LUA: M:\P3D-V4-0\Modules\MCP-747.lua:17 256903 LUA: M:\P3D-V4-0\Modules\MCP-747.lua:19 256919 LUA: Global: n = 0 256919 LUA: 0 256919 >>> Thread forced exit (ipc.exit or os.exit) <<< 256919 System time = 21/06/2017 11:42:37, Simulator time = 14:44:36 (12:44Z) ********* LUA execution terminated: Log Closed ********* The trace of the serial port (COM6) by the "Advanced Serial Port Monitor" software gives this : <20170621114237.550 SYS> COM est ouvert <20170621114237.550 SYS> Taille de queue entrĂ©e/sortie 1024/1024 <20170621114237.550 SYS> Unable to add string #8 <20170621114237.553 SYS> DĂ©bit en bauds 38400 <20170621114237.556 SYS> RTS activĂ© <20170621114237.559 SYS> DTR activĂ© <20170621114237.562 SYS> Bits de donnĂ©es=8, Bits d'arrĂȘt=1, ParitĂ©=None <20170621114237.562 SYS> Configurer charactĂšres : Eof=0x00, Error=0x00, Break=0x00, Event=0x00, Xon=0x11, Xoff=0x13 <20170621114237.565 SYS> Handflow : ControlHandShake=(DTR_CONTROL), FlowReplace=(TRANSMIT_TOGGLE, RTS_CONTROL), XonLimit=896, XoffLimit=512 <20170621114237.565 SYS> Purger le port sĂ©rie : RXABORT, RXCLEAR <20170621114237.983 SYS> Purger le port sĂ©rie : RXABORT, RXCLEAR <20170621114238.101 SYS> COM est fermĂ© There is nothing writen on the Com6 ! Using the MCP test software, with the same "Advanced Serial Port Monitor" : <20170621114831.512 SYS> COM est ouvert <20170621114831.515 SYS> Taille de queue entrĂ©e/sortie 1024/512 <20170621114831.515 SYS> Purger le port sĂ©rie : RXABORT, RXCLEAR, TXABORT, TXCLEAR <20170621114831.515 SYS> Unable to add string #8 <20170621114831.518 SYS> DĂ©bit en bauds 38400 <20170621114831.524 SYS> RTS dĂ©sactivĂ© <20170621114831.530 SYS> DTR activĂ© <20170621114831.533 SYS> Bits de donnĂ©es=8, Bits d'arrĂȘt=1, ParitĂ©=None <20170621114831.533 SYS> Configurer charactĂšres : Eof=0x1A, Error=0x00, Break=0x00, Event=0x00, Xon=0x11, Xoff=0x13 <20170621114831.539 SYS> Handflow : ControlHandShake=(DTR_CONTROL), FlowReplace=(), XonLimit=256, XoffLimit=256 <20170621114831.540 TX> Q001<NUL>Q001<NUL> <20170621114831.612 RX> KCPF<NUL>CPMCP747_100<NUL>CHIAVE0310013<NUL>MOD485EFI1<NUL>K037<NUL>K041<NUL>K017<NUL>K019<NUL>V06 359<NUL>S003<NUL>M001<NUL>K072<NUL>K075<NUL>V0900<NUL> <20170621114844.218 RX> K025<NUL> <20170621114844.218 TX> L0125 <20170621114845.089 RX> K024<NUL> <20170621114845.089 TX> L0124 <20170621114846.026 RX> K026<NUL> <20170621114846.027 TX> L0126 I do not understand where I was wrong ! Can anyone help me ? PS : I am from Paris (France) so, please, excuse my bad English ...
×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.