Jump to content
The simFlight Network Forums

All Activity

This stream auto-updates     

  1. Past hour
  2. I've no idea. The developers would need to test this with FSUIPC7. If they are not on the MSFS third-party developer list (i.e. they have access to the MSFS SDK), then they can't test until they get access to the SDK, which will be included with an MSFS license. John
  3. Great news, but will the smartcars from TFDi work with FSUIPC7 ?
  4. Save the following in a text file named "FixMyJoys.reg". Windows Registry Editor Version 5.00 [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_294B&PID_1900] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_294B&PID_1900] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16D0&PID_0A38] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_16D0&PID_0A38] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_10C4&PID_82C0] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_10C4&PID_82C0] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_8807&PID_8807] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_8807&PID_8807] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_294B&PID_1900] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_294B&PID_1900] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16D0&PID_0A38] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_16D0&PID_0A38] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_10C4&PID_82C0] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_10C4&PID_82C0] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_8807&PID_8807] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_8807&PID_8807] Now this should in no way do harm to your system -- it is just deleting your joystick device entries from the Registry. however, before editing the registry at all i always play safe and do a Windows backup (the Window backup and restore facility in Windows Settings or Control Panel). Unplug your devices. Then run the .reg file you just created by right-click and selecting "run as administrator". Now power off. Plug your devices back in, and start the PC again. This should give you a clean registry with your devices properly registered. Pete
  5. 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
  6. Today
  7. It looks like it crashed whilst reading the complete ground and air traffic data in one go. Does one of your programs do that? It's a long time since I delved into the nitty-gritty of WideFS, so it might take me a while to work out what is happening. But there are two more steps you could do, please, to narrow it down more conclusively (after all this is only one crash and it might just be coincidental that it is doing this particular thing). First do the same sort of test but with Log=Yes instead of DebugAll. Second, see if the crash still happens if you don't run the program which is reading traffic. Pete
  8. Okay, yes. I see the registry details. I'll work out what you need to do ... Pete
  9. 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
  10. I adderd this to the INI file, as you said. Debug=Please LogExtras=x200000 What should I do next? Just run the Sim?
  11. Yesterday
  12. The likely issue is that your OS now has a fault and no longer has a working version of a standard component that is used to search a database (why the MCDU is 'saying' there are no airports, waypoints, etc). The MDAC components needs to be repaired. A general Internet search will lead to possible solutions.
  13. @ashman99 I use Tower!3D, it's just been altered a bit. So my log file has more detail than is normally available. Here is KJFK's gates Load airfield: airfields/kjfk ASM: find asset: airfields/kjfk ASM: find asset: Found assets/resources/airfields/kjfk.xml Add gate T1_2 MEDIUM to Terminal_1 Add gate T1_3 NOLIMIT to Terminal_1 Add gate T1_5 NOLIMIT to Terminal_1 Add gate T1_7 NOLIMIT to Terminal_1 Add gate T1_9 NOLIMIT to Terminal_1 Add gate T1_11 NOLIMIT to Terminal_1 Add gate T1_10 NOLIMIT to Terminal_1 Add gate T1_8 NOLIMIT to Terminal_1 Add gate T1_6 NOLIMIT to Terminal_1 Add gate T1_4 NOLIMIT to Terminal_1 Add gate T2_29 NOLIMIT to Terminal_2 Add gate T2_28 NOLIMIT to Terminal_2 Add gate T2_27 NOLIMIT to Terminal_2 Add gate T2_26 NOLIMIT to Terminal_2 Add gate T2_25 NOLIMIT to Terminal_2 Add gate T2_23 NOLIMIT to Terminal_2 Add gate T2_22 NOLIMIT to Terminal_2 Add gate T2_21 NOLIMIT to Terminal_2 Add gate T2_20 NOLIMIT to Terminal_2 Add gate T2_19 NOLIMIT to Terminal_2 Add gate T4_B20 NOLIMIT to Terminal_4 Add gate T4_B22 NOLIMIT to Terminal_4 Add gate T4_B24 NOLIMIT to Terminal_4 Add gate T4_B26 NOLIMIT to Terminal_4 Add gate T4_B28 NOLIMIT to Terminal_4 Add gate T4_B30 NOLIMIT to Terminal_4 Add gate T4_B31 NOLIMIT to Terminal_4 Add gate T4_B29 NOLIMIT to Terminal_4 Add gate T4_B27 NOLIMIT to Terminal_4 Add gate T4_B25 NOLIMIT to Terminal_4 Add gate T4_A2 NOLIMIT to Terminal_4 Add gate T4_A4 NOLIMIT to Terminal_4 Add gate T4_A6 NOLIMIT to Terminal_4 Add gate T4_A3 NOLIMIT to Terminal_4 Add gate T4_A5 NOLIMIT to Terminal_4 Add gate T4_A7 NOLIMIT to Terminal_4 Add gate T6_15 NOLIMIT to Terminal_6 Add gate T6_14 NOLIMIT to Terminal_6 Add gate T6_12 NOLIMIT to Terminal_6 Add gate T6_10 NOLIMIT to Terminal_6 Add gate T6_9 NOLIMIT to Terminal_6 Add gate T6_7 NOLIMIT to Terminal_6 Add gate T6_5 NOLIMIT to Terminal_6 Add gate T6_4 NOLIMIT to Terminal_6 Add gate T6_3 NOLIMIT to Terminal_6 Add gate T6_2 NOLIMIT to Terminal_6 Add gate T6_1 NOLIMIT to Terminal_6 Add gate T7_1 MEDIUM to Terminal_7 Add gate T7_2 NOLIMIT to Terminal_7 Add gate T7_3 NOLIMIT to Terminal_7 Add gate T7_4 NOLIMIT to Terminal_7 Add gate T7_5 NOLIMIT to Terminal_7 Add gate T7_6 NOLIMIT to Terminal_7 Add gate T7_7 NOLIMIT to Terminal_7 Add gate T7_8 NOLIMIT to Terminal_7 Add gate T7_9 NOLIMIT to Terminal_7 Add gate T7_10 NOLIMIT to Terminal_7 Add gate T7_11 NOLIMIT to Terminal_7 Add gate T7_12 NOLIMIT to Terminal_7 Add gate T8_32 NOLIMIT to Terminal_8 Add gate T8_34 NOLIMIT to Terminal_8 Add gate T8_36 NOLIMIT to Terminal_8 Add gate T8_38 NOLIMIT to Terminal_8 Add gate T8_40 NOLIMIT to Terminal_8 Add gate T8_42 NOLIMIT to Terminal_8 Add gate T8_44 NOLIMIT to Terminal_8 Add gate T8_46 NOLIMIT to Terminal_8 Add gate T8_33 NOLIMIT to Terminal_8 Add gate T8_35 NOLIMIT to Terminal_8 Add gate T8_37 NOLIMIT to Terminal_8 Add gate T8_39 NOLIMIT to Terminal_8 Add gate T8_41 NOLIMIT to Terminal_8 Add gate T8_43 NOLIMIT to Terminal_8 Add gate T8_12 NOLIMIT to Terminal_8 Add gate TCargo_1 NOLIMIT to Terminal_Cargo Add gate TCargo_2 NOLIMIT to Terminal_Cargo Add gate TCargo_3 NOLIMIT to Terminal_Cargo Add gate TCargo_4 NOLIMIT to Terminal_Cargo Add gate TCargo_5 NOLIMIT to Terminal_Cargo Add gate TCargo_6 NOLIMIT to Terminal_Cargo Add gate TCargo_7 NOLIMIT to Terminal_Cargo Add gate TCargo_8 NOLIMIT to Terminal_Cargo Add gate TCargo_9 NOLIMIT to Terminal_Cargo Add gate TCargo_10 NOLIMIT to Terminal_Cargo Add gate TCargo_11 NOLIMIT to Terminal_Cargo Add gate TCargo_12 NOLIMIT to Terminal_Cargo Add gate TCargo_13 NOLIMIT to Terminal_Cargo Add gate TCargo_14 NOLIMIT to Terminal_Cargo Add gate TCargo_15 NOLIMIT to Terminal_Cargo Add gate TCargo_16 NOLIMIT to Terminal_Cargo Add gate TCargo_17 NOLIMIT to Terminal_Cargo Add gate TCargo_18 NOLIMIT to Terminal_Cargo Add gate TCargo_19 NOLIMIT to Terminal_Cargo Add gate TCargo_20 NOLIMIT to Terminal_Cargo Add gate TCargo_21 NOLIMIT to Terminal_Cargo Add gate TCargo_22 NOLIMIT to Terminal_Cargo Add gate TCargo_23 NOLIMIT to Terminal_Cargo Add gate TCargo_24 NOLIMIT to Terminal_Cargo Add gate TCargo_25 NOLIMIT to Terminal_Cargo Add gate TCargo_27 NOLIMIT to Terminal_Cargo Add gate TCargo_28 NOLIMIT to Terminal_Cargo Add gate TCargo_29 NOLIMIT to Terminal_Cargo Add gate TCargo_30 NOLIMIT to Terminal_Cargo Add gate TCargo_31 NOLIMIT to Terminal_Cargo Add gate TCargo_32 NOLIMIT to Terminal_Cargo Add gate TCargo_33 NOLIMIT to Terminal_Cargo Add gate TCargo_34 NOLIMIT to Terminal_Cargo Add gate TCargo_35 NOLIMIT to Terminal_Cargo Add gate TCargo_36 NOLIMIT to Terminal_Cargo Add gate TCargo_37 NOLIMIT to Terminal_Cargo Add gate TCargo_38 NOLIMIT to Terminal_Cargo Add gate TCargo_39 NOLIMIT to Terminal_Cargo Add gate TCargo_40 NOLIMIT to Terminal_Cargo Add gate TCargo_41 NOLIMIT to Terminal_Cargo Add gate TCargo_42 NOLIMIT to Terminal_Cargo Add gate TCargo_43 NOLIMIT to Terminal_Cargo Add gate TCargo_44 NOLIMIT to Terminal_Cargo Add gate TCargo_45 MEDIUM to Terminal_Cargo Add gate TCargo_46 NOLIMIT to Terminal_Cargo Add gate TCargo_47 NOLIMIT to Terminal_Cargo Add gate TCargo_48 NOLIMIT to Terminal_Cargo Add gate TCargo_50 NOLIMIT to Terminal_Cargo Add gate TCargo_51 NOLIMIT to Terminal_Cargo Add gate TCargo_52 NOLIMIT to Terminal_Cargo Add gate TCargo_53 NOLIMIT to Terminal_Cargo Add gate TCargo_54 NOLIMIT to Terminal_Cargo Add gate T5_1 NOLIMIT to Terminal_5 Add gate T5_2 NOLIMIT to Terminal_5 Add gate T5_3 NOLIMIT to Terminal_5 Add gate T5_4 NOLIMIT to Terminal_5 Add gate T5_5 NOLIMIT to Terminal_5 Add gate T5_6 NOLIMIT to Terminal_5 Add gate T5_7 NOLIMIT to Terminal_5 Add gate T5_8 NOLIMIT to Terminal_5 Add gate T5_9 NOLIMIT to Terminal_5 Add gate T5_10 NOLIMIT to Terminal_5 Add gate T5_11 NOLIMIT to Terminal_5 Add gate T5_12 NOLIMIT to Terminal_5 Add gate T5_13 NOLIMIT to Terminal_5 Add gate T5_14 NOLIMIT to Terminal_5 Add gate T5_15 NOLIMIT to Terminal_5 Add gate T5_16 NOLIMIT to Terminal_5 Add gate T5_17 NOLIMIT to Terminal_5 Add gate T5_18 NOLIMIT to Terminal_5 Add gate T5_19 NOLIMIT to Terminal_5 Add gate T5_20 NOLIMIT to Terminal_5 Add gate T5_21 NOLIMIT to Terminal_5 Add gate T5_23 NOLIMIT to Terminal_5 Add gate T5_24 NOLIMIT to Terminal_5 Add gate T5_25 NOLIMIT to Terminal_5 Add gate T5_26 NOLIMIT to Terminal_5 Add gate T8_45 NOLIMIT to Terminal_8 Add gate T8_47 NOLIMIT to Terminal_8 Add gate T8_14 NOLIMIT to Terminal_8 Add gate T8_16 NOLIMIT to Terminal_8 Add gate T8_10 NOLIMIT to Terminal_8 Add gate T8_8 NOLIMIT to Terminal_8 Add gate T8_6 NOLIMIT to Terminal_8 Add gate T8_4 NOLIMIT to Terminal_8 Add gate T8_2 NOLIMIT to Terminal_8 Add gate T8_1 NOLIMIT to Terminal_8 Add gate T8_3 NOLIMIT to Terminal_8 Add gate T8_5 NOLIMIT to Terminal_8 Add gate T4_40 NOLIMIT to Terminal_4 Add gate T4_41 NOLIMIT to Terminal_4 Add gate T4_43 NOLIMIT to Terminal_4 Add gate T4_44 NOLIMIT to Terminal_4 Add gate T4_45 NOLIMIT to Terminal_4 Add gate T4_46 NOLIMIT to Terminal_4 Add gate T4_47 NOLIMIT to Terminal_4 Add gate T4_48 NOLIMIT to Terminal_4 Add gate GA1 LIGHT to Terminal_GA Add gate GA2 LIGHT to Terminal_GA Add gate GA3 LIGHT to Terminal_GA Add gate GA4 LIGHT to Terminal_GA Add gate GA5 LIGHT to Terminal_GA Daniel
  14. You tried "(L:klid) = 1703010" where, exactly? and what do you mean by "the fsuipc list"? I really don't know what you are talking about there. To set an L:var from a Lua plug in you need to use the ipc.writeLvar function. Please do refer to the Lua library documentation. Pete
  15. I searched about the MDAC, but I'm still not sure what to do. I use windows 7 and I remember that recently I installed something for the simulator not to give so much trouble such as crashes or to not stop working suddenly. what should I do?
  16. So the actual devices you have are: 1 x Alpha Flight Controls 2 x UnoJoy_Throttle 1 x B737 1 x MFG Crosswind V2 Right? And in the last set of files you submitted these were recognised and assigned: 2 x Alpha Flight Controls 2 x UnoJoy Throttle which means on that occasion you lost both the B737 and the Crosswind and gained a "ghost" Alpha Flight Control! All because of Windows apparently repetitively assigning new GUIDs which copy existing ones. I think there must be a load of entries in the Registry for each of those devices and which entry gets assigned is almost pot luck. Not sure what the "more details" were intended to be in the Log, but there's nothing useful there. For some reason you are running a plugin called "comtest.lua" and have Lua log/trace enabled. Next step would be to get the log with that extra logging i mentioned so I can give you instructions on cleaning this stuff in the Registry. Pete
  17. Well, it might be easier to eliminate each of them, one at a time -- or maybe by halves. after all, in the end i have to get the logging operating for those offsets to see which causes the crash (assuming it is due to one of the values being written). Another way of tackling it would be to log them all in any case and see if there's any consistency over the last thing written before the crash. It's just that the log could get very large. To make this happen please set Log=Yes (replacing Log=Errors+ probably) in the [User] section of WideClient.INI. There are much more detailed logging options which we'd use if that proves futile -- Log=All, and Log=DebugAll. One of these methods should show us what is causing the problem. Pete
  18. not for me that why I asked cheers.....
  19. Hi Pete, i was able to read the values and get the displays going. now i have another roadblock as i have jumped to Captain Sim 757, seems to be a better model and they have a published SDK. Using the same code i was able to display the MCP Altitude on the 7segment - using the L:var. values Now to use the knobs i checked the SDK and its says the following. - ---------------------------------- HOW TO RETURN DATA FOR MOMENTARY ACTION SWITCHES 1. Convert the element's name into an ID number. For example, for the G02_003_BUT. - remove all underscores and the ending to get G02003. - change the first letter to a number according to the table below: C=13 G=17 L=22 O=25 P=26 R=28 So an ID number for the G02_003_BUT is 1702003. 2. Set the ID number to the L:klid variable. This will simulate a user's click. FOR KNOBS ( _KNO) 1.Convert the element's name into an ID number. 2. Add the - (minus) for counterclockwise rotation. For example: (L:klid) = 1702003 - clockwise rotation. (L:klid) = -1702003 - counterclockwise rotation FOR ALL OTHER ELEMENTS Set the required value to a variable. E.g. to press the G02_003_BUT: (L:G02_003_BUT) = 1 ---------------------------------------------------------------- I Used the data and i was able to come up with the ID for the MCP Airspeed = 1703010 How would i set the ID number to the L:klid variable to simulate a user's click / knob rotation ???? 😞 i tried (L:klid) = 1703010 , but it does not show up in the fsuipc list. ☹️ CS757CAPTAINIII_MANUAL_PART6.pdf
  20. Ok, deinstalled them all again, and connected one by one, all devices are recognized by FSUIPC, didn't reboot yet. Here are the new ini, without reboot, and the new Log with more details. Greets Sergej FSUIPC6.rar
  21. It is a problem for me and numerous others. Check the forum.
  22. 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
  23. We didn't need the FSUIPC log. If anything the WideServer log would be the one relating to WideFS. You give only one client log. Please confirm that there are no lua files in the WideClient folder. I see there are quite a few applications being loaded: 5016 New Client Application: "FsATG" (Id=1720)5422 New Client Application: "FD_Sounds" (Id=10480)21922 New Client Application: "FlightDeck320" (Id=7212)282110 New Client Application: "FSATG" (Id=5492)287516 New Client Application: "FD_PUSHBACKEDITOR" (Id=1444) Is it possible for you to run with less of these? Or even one at a time? I'm trying to see which might be causing WideClient to crash. I know it shouldn't happen, but perhaps one of them is writing some values to an FSUIPC offset which Wideclient chokes on. Once we can narrow it down I can tell you how to enable logging so we can find out exactly which. To do this logging without first narrowing it down a bit would produce far to much to wade through i fear. Pete
  24. @WildCard Daniel, what software did you use in order to search to find the gate size limitations for each airport? Also when you did find it, where you able to edit gate size types? Mostly curious as I was playing for JFK gate sizes since most of the retros have flown in and out of there.
  25. Thanks John and Peter, a must have in this hobbie...
  26. Yes. I will release a beta version of FSUIPC7 for MSFS on the 18th. I'll post more details in the Announcements section before the 18th. John
  27. 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
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • 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.