Jump to content
The simFlight Network Forums

StefanGA

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About StefanGA

  • Rank
    Member

Profile Information

  • Gender
    Not Telling
  • Location
    GER

Recent Profile Visitors

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

  1. Pete, John & all interested, after some time of headache, testing and further development I can report that the root cause of the occasional quits is not an FSUIPC issue. It turned out that I had another thread running in parallel to the main thread doing FSUIPC Writes and Process(), and the calls have not been properly mutexed. After fixing I have now appx. 8+ hours without a quit anymore. Thanks for your support ! Best regards Stefan
  2. >> The last part, the entries timed 300422, show a lot of separate transactions ("Process Message") all within one millisecond or so. Certainly a lot lot more than in the earlier times. What >> might be happening there? Not sure. I run a 2-PC setup. The second runs a "A320 Cockpit suite" with several apps, some self-developped among them using FSUIPC. These are configured to access FSUIPC in cycles not faster appx 50ms, but they of course run independantly towards WideClient. The main app uses the AI table access to just trigger some sound effects outside of P3D. Not a big deal to reduce the access cycle time if that causes interference in WC, but is this the problem .. ? Thank you, Stefan
  3. Hi Pete, after some days of absence I had a chance to experience the original issue again tonight. (I saw another thread in the meantime experiencing a similar issue). I also got the feeling that I could "provoke" the termination of WC by changing views in P3D, eg from VC to Spot view and vice versa. (stripped Log /final lines / is attached) As you already mentioned, the issue might correlate with reading the AI tables: My app reads the full ground AI and airborne AI tables in one FSUIPC_Process() call each 250ms. When I deactivate this part of code and the related functions, I can not reproduce the termination of WC. Hope this helps - BR Stefan WideClient_Quit.log
  4. Pete, yes, when on ground the AI table is read by one of my apps within a 250ms cycle. I'll do as proposed, first with Log=Yes, then disabling the AI table read. Thank you, Stefan
  5. Pete, I ran a session with Log=DebugAll, and had the quit after appx. 20min. The log file is about 4GB - the last entries show : 2172703 Exiting ProcessRequestData <M13:L1:C1:H311> 2172703 FreeSlot releases pView <M13:L1:C1:H311> 2172703 FreeSlot releases hMap <M13:L1:C1:H310> 2172703 ProcessRequest: Exit <M13:L1:C1:H310> 2172703 FS6IPC message Exit2 <M13:L1:C1:H310> 2172703 FS6IPC message Entry <M13:L1:C1:H310> 2172703 Processing request now ... <M13:L1:C1:H310> 2172703 ProcessRequest: Getting Atom Name <M13:L1:C1:H310> 2172703 ProcessRequest: Opening File Mapping <M13:L1:C1:H310> 2172703 ProcessRequest: Getting a View <M13:L1:C1:H311> 2172703 ProcessRequest: processing the request <M13:L1:C1:H311> 2172703 Exiting ProcessRequestData <M13:L1:C1:H311> 2172703 ProcessRequest: dealing with response <M13:L1:C1:H311> 2172703 MakeSmaller: Orig Size = 7758 <M13:L1:C1:H311> 2172703 FS6IPC Data Processed <M13:L1:C1:H311> PREQ ulSize=7747, ulTime=2172703, uSum=2035, fUsed=1 01 00 00 00 80 E0 00 00 00 0F 00 00 C8 D7 B0 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ (330 lines of Zero following to the end). Does this help or do you need other outputs / infos ? Stefan
  6. Pete, I see. All of these apps on the wideclient side are self-developped Win32 apps, so I have full control. What I could prepare is a list of all Offsets / Offset ranges that these apps read and write to, will take a bit of time. Thanks for your effort ! Stefan
  7. Hi Pete, I don't use Lua specifically. You see the Joysticks used in the log, but they are all connected to the main P3D machine. Here are the logs: ********* FSUIPC6, Version 6.0.10 (19th July 2020) by Pete & John Dowson ********* Prepar3d.exe version = 5.0.31.35253 Running inside Prepar3D v5 Module base=7FFE90120000 Windows 10 Pro 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0) Reading options from "E:\P3D Add-ons\FSUIPC6\FSUIPC6.ini" Checking the Registrations now ... User Name= ; User Addr= ; FSUIPC6 Key is provided WideFS7 Key is provided 0 System time = 11/08/2020 11:40:04 0 FLT UNC path = "\\STUDIO-PC\Windows10\Users\Verwaltung\Documents\Prepar3D v5 Files\" 0 Using DialogMode 32 FS UNC path = "\\STUDIO-PC\FlightSim\Prepar3D V5\" 94 ---------------------- Joystick Device Scan ----------------------- 94 Product= Saitek Pro Flight Rudder Pedals 94 Manufacturer= Saitek 94 Vendor=06A3, Product=0763 (Version 1.0) 94 GUIDs returned for product: VID_06A3&PID_0763: 94 GUID= {502E2420-5143-11E8-8001-444553540000} 94 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 94 Product= T.16000M 94 Manufacturer= Thrustmaster 94 Vendor=044F, Product=B10A (Version 5.0) 94 GUIDs returned for product: VID_044F&PID_B10A: 94 GUID= {604D54F0-1828-11E9-8001-444553540000} 94 Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255 110 Product= Saitek Pro Flight Quadrant 110 Manufacturer= Saitek 110 Vendor=06A3, Product=0C2D (Version 2.0) 110 GUIDs returned for product: VID_06A3&PID_0C2D: 110 GUID= {502E2420-5143-11E8-8002-444553540000} 110 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 110 Product= Saitek Pro Flight Yoke 110 Manufacturer= Saitek 110 Vendor=06A3, Product=0BAC (Version 3.0) 110 GUIDs returned for product: VID_06A3&PID_0BAC: 110 GUID= {502E2420-5143-11E8-8003-444553540000} 110 Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U128,V-268435327,X1023,Y1023,Z128 110 ------------------------------------------------------------------- 110 Device acquired for use: 110 Joystick ID = 2 (Registry okay) 110 2=Saitek Pro Flight Rudder Pedals 110 2.GUID={502E2420-5143-11E8-8001-444553540000} 110 Device acquired for use: 110 Joystick ID = 0 (Registry okay) 110 0=T.16000M 110 0.GUID={604D54F0-1828-11E9-8001-444553540000} 110 Device acquired for use: 110 Joystick ID = 1 (Registry okay) 110 1=Saitek Pro Flight Quadrant 110 1.GUID={502E2420-5143-11E8-8002-444553540000} 110 Device acquired for use: 110 Joystick ID = 3 (Registry okay) 110 3=Saitek Pro Flight Yoke 110 3.GUID={502E2420-5143-11E8-8003-444553540000} 110 ------------------------------------------------------------------- 141 Controllers are set to ON, using RawInput within P3D 141 LogOptions=00000000 00000001 141 ------------------------------------------------------------------- 141 SimConnect_Open succeeded: waiting to check version okay 141 Opened separate AI Traffic client okay 1454 Running in "Lockheed Martin® Prepar3D® v5", Version: 5.0.31.35253 (SimConnect: 5.0.0.0) 1454 Initialising SimConnect data requests now 1454 FSUIPC Menu entry added 1454 ... Using Prepar3D with Academic License 1454 \\Studio-PC\Windows10\Users\Verwaltung\Documents\Prepar3D v5 Files\FsFlightDeck.fxml 1454 \\STUDIO-PC\FlightSim\P3D Add-ons\01 My A320\SimObjects\Airplanes\Airbus A320-214\A320.air 1469 ### The user object is 'A320 SAS' 1469 ### Mode is NORMAL 1797 ### Mode: PAUSE on 6407 -------------------------------------------------------------------- 6407 ***** HID USB device reconnected: re-initialising FSUIPC connections 6407 HID: Vendor=046D, Product=C534 (Version 41.1) 6407 Manufacturer= Logitech 6407 Product= USB Receiver 6407 Serial Number= USB Receiver 6407 ---------------------- Joystick Device Scan ----------------------- 6407 Product= Saitek Pro Flight Rudder Pedals 6407 Manufacturer= Saitek 6407 Vendor=06A3, Product=0763 (Version 1.0) 6407 GUIDs returned for product: VID_06A3&PID_0763: 6407 GUID= {502E2420-5143-11E8-8001-444553540000} 6407 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 6407 Product= T.16000M 6407 Manufacturer= Thrustmaster 6407 Vendor=044F, Product=B10A (Version 5.0) 6407 GUIDs returned for product: VID_044F&PID_B10A: 6407 GUID= {604D54F0-1828-11E9-8001-444553540000} 6407 Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255 6407 Product= Saitek Pro Flight Quadrant 6407 Manufacturer= Saitek 6407 Vendor=06A3, Product=0C2D (Version 2.0) 6407 GUIDs returned for product: VID_06A3&PID_0C2D: 6407 GUID= {502E2420-5143-11E8-8002-444553540000} 6407 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 6407 Product= Saitek Pro Flight Yoke 6407 Manufacturer= Saitek 6407 Vendor=06A3, Product=0BAC (Version 3.0) 6407 GUIDs returned for product: VID_06A3&PID_0BAC: 6407 GUID= {502E2420-5143-11E8-8003-444553540000} 6407 Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U128,V-268435327,X1023,Y1023,Z128 6407 ------------------------------------------------------------------- 6422 Device acquired for use: 6422 Joystick ID = 2 (Registry okay) 6422 2=Saitek Pro Flight Rudder Pedals 6422 2.GUID={502E2420-5143-11E8-8001-444553540000} 6422 Device acquired for use: 6422 Joystick ID = 0 (Registry okay) 6422 0=T.16000M 6422 0.GUID={604D54F0-1828-11E9-8001-444553540000} 6422 Device acquired for use: 6422 Joystick ID = 1 (Registry okay) 6422 1=Saitek Pro Flight Quadrant 6422 1.GUID={502E2420-5143-11E8-8002-444553540000} 6422 Device acquired for use: 6422 Joystick ID = 3 (Registry okay) 6422 3=Saitek Pro Flight Yoke 6422 3.GUID={502E2420-5143-11E8-8003-444553540000} 6422 ------------------------------------------------------------------- 19610 Loading Complete ... 19625 ### Mode is NORMAL 19860 Aircraft loaded: running normally now ... 19875 User Aircraft ID 1 supplied, now being used 20532 System time = 11/08/2020 11:40:24, Simulator time = 11:40:06 (09:40Z) 20547 Aircraft="A320 SAS" 26532 -------------------- Starting everything now ---------------------- 26532 Starting WideServer now ... 26547 ASN active function link set 26547 Ready for ActiveSky WX radar with additional data 26547 Note: 200 bytes memory used WXradar bitmap 27641 Advanced Weather Interface Enabled 29672 Weather Mode now = Theme 65563 Note: 80000 bytes memory used WXradar bitmap 1052719 -------------------------------------------------------------------- 1052719 ***** HID USB device reconnected: re-initialising FSUIPC connections 1052719 HID: Vendor=046D, Product=C534 (Version 41.1) 1052719 Manufacturer= Logitech 1052719 Product= USB Receiver 1052719 Serial Number= USB Receiver 1052719 ---------------------- Joystick Device Scan ----------------------- 1052719 Product= Saitek Pro Flight Rudder Pedals 1052719 Manufacturer= Saitek 1052719 Vendor=06A3, Product=0763 (Version 1.0) 1052719 GUIDs returned for product: VID_06A3&PID_0763: 1052719 GUID= {502E2420-5143-11E8-8001-444553540000} 1052719 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 1052719 Product= T.16000M 1052719 Manufacturer= Thrustmaster 1052719 Vendor=044F, Product=B10A (Version 5.0) 1052719 GUIDs returned for product: VID_044F&PID_B10A: 1052719 GUID= {604D54F0-1828-11E9-8001-444553540000} 1052719 Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255 1052719 Product= Saitek Pro Flight Quadrant 1052719 Manufacturer= Saitek 1052719 Vendor=06A3, Product=0C2D (Version 2.0) 1052719 GUIDs returned for product: VID_06A3&PID_0C2D: 1052719 GUID= {502E2420-5143-11E8-8002-444553540000} 1052719 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 1052735 Product= Saitek Pro Flight Yoke 1052735 Manufacturer= Saitek 1052735 Vendor=06A3, Product=0BAC (Version 3.0) 1052735 GUIDs returned for product: VID_06A3&PID_0BAC: 1052735 GUID= {502E2420-5143-11E8-8003-444553540000} 1052735 Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U128,V-268435327,X1023,Y1023,Z128 1052735 ------------------------------------------------------------------- 1052735 Device acquired for use: 1052735 Joystick ID = 2 (Registry okay) 1052735 2=Saitek Pro Flight Rudder Pedals 1052735 2.GUID={502E2420-5143-11E8-8001-444553540000} 1052735 Device acquired for use: 1052735 Joystick ID = 0 (Registry okay) 1052735 0=T.16000M 1052735 0.GUID={604D54F0-1828-11E9-8001-444553540000} 1052735 Device acquired for use: 1052735 Joystick ID = 1 (Registry okay) 1052735 1=Saitek Pro Flight Quadrant 1052735 1.GUID={502E2420-5143-11E8-8002-444553540000} 1052735 Device acquired for use: 1052735 Joystick ID = 3 (Registry okay) 1052735 3=Saitek Pro Flight Yoke 1052735 3.GUID={502E2420-5143-11E8-8003-444553540000} 1052735 ------------------------------------------------------------------- 5777813 === Closing session: waiting for DLLStop to be called ... 5778688 Sim stopped: average frame rate for last 5758 secs = 60.2 fps 5778688 Max AI traffic was 61 aircraft 5778688 ------------------------------------------------------------------- ********* WideClient Log [version 7.156] Class=FS98MAIN ********* Date (dmy): 11/08/20, Time 11:39:45.349: Client name is FLIGHTDECK 3532 Attempting to connect now 3532 Trying TCP/IP addr 192.168.1.10, port 8002 ... 3563 LUA: "E:\WideClient\Initial.LUA": not found 5016 New Client Application: "FsATG" (Id=1720) 5422 New Client Application: "FD_Sounds" (Id=10480) 5610 Error on client pre-Connection Select() [Error=10061] Connection refused 5610 Ready to try connection again 6641 Attempting to connect now 21922 New Client Application: "FlightDeck320" (Id=7212) 60969 Connection made okay! 282110 New Client Application: "FSATG" (Id=5492) 287516 New Client Application: "FD_PUSHBACKEDITOR" (Id=1444) BR Stefan
  8. John, indeed event entries of Wideclient : WideClient.exe 7.1.5.6 5c52c65a ntdll.dll 10.0.19041.207 1bdbc4b8 c0000005 00048976 e54 01d66fc3586b7422 E:\WideClient\WideClient.exe C:\Windows\SYSTEM32\ntdll.dll cff7ce4e-9d83-4f9d-82fe-b8aeca3f55e3
  9. John, thanks for the fast reponse ! I already run 6.0.10. It started with 6.0.8. I'll check for the event log. BR Stefan
  10. Hey FSUIPC team & users, I use FSUIPC since the 3.x times with FSX. Today I have a nice, smoothly running home cockpit setup with 2 x i7 PCs with Win10 x64, one runs P3D V5, the other runs cockpit stuff with Wideclient. Since using FSUICP 6.0.8 , I have a strange phenomena: Wideclient occasionally quits without any notice, error message or other usefull info. The FSUIPC server log as well as the wideclient log have no special entry other than the normal logs. I see no relation to any specific action or situation that might force this. Also the software modules I run on the cockpit machine have not been changed specifically for months. Network connection is stable and inconspicuous. It occurs sometimes after 15 min, sometimes after 1hour flying and rolling to the gate - the FSUIPC data transfer stops, and in task manager wideclient.exe simply has gone .. Anybody some hints were to look at ? Thanks all, and to Pete and John : a wonderful great product , hope it continuous its life !
×
×
  • Create New...

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.