BoxxMann Posted October 10, 2015 Report Share Posted October 10, 2015 Hello, I updated to 4.947 from 4.946 and now all three sims listed above will not run. I rolled back to 4.946 and all seems to be good. :/ Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 10, 2015 Report Share Posted October 10, 2015 I updated to 4.947 from 4.946 and now all three sims listed above will not run. I rolled back to 4.946 and all seems to be good. :/ It runs fine here on all those plus FSX. I need more information, please. Specifically what actually happens -- "will not run" is rather less than informative. And a view of the FSUIPC4.LOG file (in the Modulers folder) from the unsuccessful attempts would be handy. There's really no point in reporting things like this with no accompanying information, don't you see? Pete Link to comment Share on other sites More sharing options...
BoxxMann Posted October 11, 2015 Author Report Share Posted October 11, 2015 It runs fine here on all those plus FSX. I need more information, please. Specifically what actually happens -- "will not run" is rather less than informative. And a view of the FSUIPC4.LOG file (in the Modulers folder) from the unsuccessful attempts would be handy. There's really no point in reporting things like this with no accompanying information, don't you see? Pete Yes, you're right. I rolled back to 4.946 and it goes fine. If there was an option here to remove the thread, I'd have opted for it. Here's the symptom: Start up each of the programs and none run, none of which go past the splash screens. There's really nothing more to report. While I'm sure all run fine on your end, but don't you see that perhaps others may not have the same results? Congratulations on having such a successful program. I am sure I am not your only paying customer who enjoys it so much. Since 4.946 runs without trouble and 4.947 does not produce more symptoms than what's stated, I'm happy to stay there and leave it at that. Link to comment Share on other sites More sharing options...
Luke Kolin Posted October 11, 2015 Report Share Posted October 11, 2015 There's really nothing more to report. While I'm sure all run fine on your end, but don't you see that perhaps others may not have the same results? Pete asked you for the log. I'm sure he understands that others may not have the same results, but unless you give him more information how is he ever going to find out what isn't working?? Cheers! Luke Link to comment Share on other sites More sharing options...
Walter Aeschbach Posted October 11, 2015 Report Share Posted October 11, 2015 I've got the same problem. Here the full log: ********* FSUIPC4, Version 4.947 by Pete Dowson *********Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"Running inside Prepar3D v3 on Windows 8.0Module base=52780000FSUIPC4 Key is providedWIDEFS7 not user registered, or expired 1312 System time = 10/10/2015 16:33:24 1312 FLT path = "C:\Users\Walti\Documents\Prepar3D v3 Files\" 1312 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 1328 Found it: trying to connect 1359 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\" 1547 ---------------------- Joystick Device Scan ----------------------- If I run fsuipc as an unregistered user then Prepar3d V3 starts without a problem. If I run fsuipc as an registered user then Prepar3d V3 crashes. Thanks Walter Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 11, 2015 Report Share Posted October 11, 2015 Yes, you're right. I rolled back to 4.946 and it goes fine. If there was an option here to remove the thread, I'd have opted for it. Why? How will I ever fix problems is everyone did that? I have to find and fix problems! Here's the symptom: Start up each of the programs and none run, none of which go past the splash screens. There's really nothing more to report. Okay, that is more helpful. So it HANGS at the start-up screen, not CRASHES? i.e. Windows doesn't report a crash? While I'm sure all run fine on your end, but don't you see that perhaps others may not have the same results? Oh dear. It is precisely BECAUSE it doesn't fail here thgat I need your help in finding out why it doesn't work there! There are so many variations on folks systems that I cannot possibly test here. I do my best, but then I'm reliant on nice friendly users giving me feedback, information, with which to continue to improve the program whilst trying to avoid or at least fix any problems! Since 4.946 runs without trouble and 4.947 does not produce more symptoms than what's stated, I'm happy to stay there and leave it at that. That's really unhelpful! All I asked for was for more information so I could fix it. I'm sorry you don't have the time nor patience to do this. Hopefully the next person to get a similar problem won't take the same attitude, otherwise I'll not be able to fix it at all, and such users will never be able to update their P3D or FSX-SE either, because each such update requires a new update for FSUIPC. :sad: [LATER] Ah, I see the next person has been more helpful, so I won't bother you any more. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 11, 2015 Report Share Posted October 11, 2015 I've got the same problem. Here the full log: Ah, THANK YOU very much. That's much more helpful. So it's hanging in the device scan, even before logging the first device. Hmm. Could you please download this test version,FSUIPC4947a_TEST with additional logging added. Before running P3D, add these lines to the [General] section of the FSUIPC4.INI file: Debug=Please LogExtras=x200000 Please just run it to get, hopefully, a more detailed log. You should then remove the LogExtras line before going back, temporarily (hopefully) to 4.946. Another way to help please, if you don't mind, would be to runHidScanner and show me the log resulting from that, please. The new scanning code in FSUIPC uses the same methods as HidScanner. If this doesn't hang as well it will give me a log more info. If I run fsuipc as an unregistered user then Prepar3d V3 starts without a problem. If I run fsuipc as an registered user then Prepar3d V3 crashes. You really mean crashes rather than hangs? If so, can you locate the windows crash data from me, please? In Windows' event viewer? That'll be most useful too. Thanks Pete Link to comment Share on other sites More sharing options...
Walter Aeschbach Posted October 11, 2015 Report Share Posted October 11, 2015 Helle Pete, thank you very much. 4947a works! Here the log ********* FSUIPC4, Version 4.947a by Pete Dowson *********Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"Running inside Prepar3D v3 on Windows 8.0Module base=15540000 FSUIPC4 Key is providedWIDEFS7 not user registered, or expired 422 System time = 11/10/2015 11:26:47 422 FLT path = "C:\Users\Walti\Documents\Prepar3D v3 Files\" 422 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 438 Found it: trying to connect 485 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\" 657 #### Initialising Dlrectinput Axis Scanning ... 672 Found correct joystick Id 0 672 ... and a "GUID" value 688 ... okay, Acquired device as #0! 782 ---------------------- Joystick Device Scan ----------------------- 782 Checking: \\?\hid#vid_044f&pid_b10a#6&1255c004&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Product= T.16000M 782 Manufacturer= Thrustmaster 782 Vendor=044F, Product=B10A (Version 5.0) 782 Serial Number= Thrustmaster 782 Checking: \\?\hid#vid_056a&pid_0027&col02#7&792ed82&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_046d&pid_c31c&mi_01&col01#8&3031901a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_056a&pid_0027&col03#7&792ed82&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_046d&pid_c31c&mi_01&col02#8&3031901a&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_046d&pid_c31c&mi_01&col03#8&3031901a&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_056d&pid_0002#8&260220fe&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_056a&pid_0027&col04#7&792ed82&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_056a&pid_0027&col05#7&792ed82&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_046d&pid_c069#6&1488b66d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_046d&pid_c31c&mi_00#8&186e03d5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 Checking: \\?\hid#vid_056a&pid_0027&col01#7&792ed82&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 782 ------------------------------------------------------------------- 782 #### Completed Dlrectinput Axis Scanning 860 LogOptions=00000000 02000011 891 ------------------------------------------------------------------- 891 ------ Setting the hooks and direct calls into the simulator ------ 891 --- CONTROLS timer memory location obtained ok 891 --- SIM1 Frictions access gained 907 --- FS Controls Table located ok 907 --- Installed Mouse Macro hooks ok. 907 --- Wind smoothing fix is installed 907 --- All links checked okay 907 ------------------------------------------------------------------- 907 SimConnect_Open succeeded: waiting to check version okay 907 Trying to use SimConnect Prepar3D 2469 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 2469 Initialising SimConnect data requests now 2469 FSUIPC Menu entry added 2485 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 2485 C:\Users\Walti\Documents\Prepar3D v3 Files\ZRH Beech King.fxml 2485 C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\Beech_King_Air_350\Beech_King_Air_350.air 2594 Memory in use: 742Mb, Avail=3354Mb 14766 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 15703 System time = 11/10/2015 11:27:02, Simulator time = 08:00:01 (07:00Z) 15719 Aircraft="Beech King Air 350 Paint1" 16719 Starting everything now ... 16735 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 17297 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 24875 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 27032 Advanced Weather Interface Enabled 29344 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 34282 Deactivated for PID=9748, "notepad++.exe" 34282 Lost focus to PID=9748, "notepad++.exe" 34797 === NOTE: not calling SimConnect_Close ... 35797 System time = 11/10/2015 11:27:22, Simulator time = 08:00:07 (07:00Z) 35797 *** FSUIPC log file being closedMinimum frame rate was 78.2 fps, Maximum was 86.4 fpsMinimum available memory recorded was 32768MbAverage frame rate for running time of 7 secs = 83.7 fpsMemory managed: 5 Allocs, 5 Freed********* FSUIPC Log file closed *********** You really mean crashes rather than hangs? If so, can you locate the windows crash data from me, please? In Windows' event viewer? That'll be most useful too. No, windows is not crashing. If I run fsuipc as an registered user then Prepar3d V3 is hidden and I can't "play" with it :-) Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 11, 2015 Report Share Posted October 11, 2015 thank you very much. 4947a works! Ah, but does it still work if you remove those extra logging lines? If not then I have a difficult timing bug to locate. If it does still work then I think I know what it must have been ... Thanks for the log. It is very useful to help me improve some things in any case. ;-) I'll have another Test version later today. Would you mind trying that for me too, before I "unleash" any more trouble? Pete Link to comment Share on other sites More sharing options...
Walter Aeschbach Posted October 11, 2015 Report Share Posted October 11, 2015 Hi Pete, I removed those extra logging lines and it still works :razz: In my case, the problem ist solved. The next test version I will be able to test not before tomorrow evening, sorry! Thanks a lot Walter Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 11, 2015 Report Share Posted October 11, 2015 I removed those extra logging lines and it still works :razz: Good. In my case, the problem ist solved. The next test version I will be able to test not before tomorrow evening, sorry! Okay. I'll post another link anyway later today and be patient! ;-) Pete Link to comment Share on other sites More sharing options...
Walter Aeschbach Posted October 11, 2015 Report Share Posted October 11, 2015 Sorry Pete, it's crazy, but at the moment fsuipc 4.947a is not working anymore even with extra logging files! Good luck Walter Here are the logs ********* HidScanner, Version 2.00 by Pete Dowson ********* Device at "\\?\hid#vid_044f&pid_b10a#6&1255c004&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=044F, Product=B10A (Version 5.0) Manufacturer= Thrustmaster Product= T.16000M Serial Number= T.16000M Usage Page: 1 Input Report Byte Length: 10 Output Report Byte Length: 0 Feature Report Byte Length: 5 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 5 Number of InputData Indices: 21 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 16 at indices 0 -> 15 Value POV at index 16, range 0 -> 7, using 4 bits Value X at index 17, range 0 -> 16383, using 14 bits Value Y at index 18, range 0 -> 16383, using 14 bits Value Sldr at index 19, range 0 -> 255, using 8 bits Value R/RZ at index 20, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_056a&pid_0027&col02#7&792ed82&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=056A, Product=0027 (Version 1.7) Manufacturer= Wacom Co.,Ltd. Product= Intuos5 touch M Serial Number= Usage Page: FF00 Input Report Byte Length: 11 Output Report Byte Length: 86 Feature Report Byte Length: 1024 Number of Link Collection Nodes: 3 Number of Input Button Caps: 0 Number of InputValue Caps: 5 Number of InputData Indices: 5 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 1 Number of Feature Button Caps: 1 Number of Feature Value Caps: 1 Number of Feature Data Indices: 2 Value X at index 0, range 0 -> 44704, using 16 bits Value Y at index 1, range 0 -> 27940, using 16 bits Value X at index 2, range 0 -> 2047, using 16 bits Value 0x01 at index 3, range 0 -> 255, using 8 bits Value 0x01 at index 4, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_046d&pid_c31c&mi_01&col01#8&3031901a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=046D, Product=C31C (Version 100.0) Manufacturer= Logitech Product= USB Keyboard Serial Number= USB Keyboard Usage Page: C Input Report Byte Length: 2 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 1 Number of InputData Indices: 2 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0xE0 at index 0, range -24 -> 24, using 7 bits ************************************************************************** Device at "\\?\hid#vid_056a&pid_0027&col03#7&792ed82&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=056A, Product=0027 (Version 1.7) Manufacturer= Wacom Co.,Ltd. Product= Intuos5 touch M Serial Number= Usage Page: FF00 Input Report Byte Length: 64 Output Report Byte Length: 86 Feature Report Byte Length: 1024 Number of Link Collection Nodes: 3 Number of Input Button Caps: 0 Number of InputValue Caps: 4 Number of InputData Indices: 4 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 1 Number of Feature Button Caps: 1 Number of Feature Value Caps: 1 Number of Feature Data Indices: 2 Value X at index 0, range 0 -> 4096, using 16 bits Value Y at index 1, range 0 -> 4096, using 16 bits Value 0x01 at index 2, range 0 -> 255, using 8 bits Value 0x01 at index 3, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_046d&pid_c31c&mi_01&col02#8&3031901a&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=046D, Product=C31C (Version 100.0) Manufacturer= Logitech Product= USB Keyboard Serial Number= USB Keyboard Usage Page: 1 Input Report Byte Length: 2 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 3 Number of InputValue Caps: 0 Number of InputData Indices: 3 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_046d&pid_c31c&mi_01&col03#8&3031901a&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=046D, Product=C31C (Version 100.0) Manufacturer= Logitech Product= USB Keyboard Serial Number= USB Keyboard Usage Page: C Input Report Byte Length: 4 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 21 Number of InputValue Caps: 0 Number of InputData Indices: 21 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_056d&pid_0002#8&260220fe&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=056D, Product=0002 (Version 128.0) Manufacturer= EIZO Product= EIZO USB HID Monitor Serial Number= EIZO USB HID Monitor Usage Page: 80 Input Report Byte Length: 519 Output Report Byte Length: 0 Feature Report Byte Length: 519 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 2 Number of InputData Indices: 2 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 9 Number of Feature Data Indices: 9 Value 0x03 at index 0, range 0 -> 255, using 8 bits Value 0x05 at index 1, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_056a&pid_0027&col04#7&792ed82&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=056A, Product=0027 (Version 1.7) Manufacturer= Wacom Co.,Ltd. Product= Intuos5 touch M Serial Number= Usage Page: D Input Report Byte Length: 38 Output Report Byte Length: 0 Feature Report Byte Length: 2 Number of Link Collection Nodes: 2 Number of Input Button Caps: 6 Number of InputValue Caps: 13 Number of InputData Indices: 19 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Value X at index 6, range 0 -> 32767, using 16 bits Value Y at index 7, range 0 -> 32767, using 16 bits Value Z at index 8, range 0 -> 1024, using 16 bits Value X at index 9, range 0 -> 2047, using 16 bits Value 0x5B at index 10, range 0 -> 2047, using 32 bits Value 0x5B at index 11, range 0 -> 2047, using 64 bits Value 0x77 at index 12, range 0 -> 2047, using 32 bits Value Y at index 13, range 0 -> 1024, using 16 bits Value 0x3D at index 14, range -9000 -> 9000, using 16 bits Value 0x3E at index 15, range -9000 -> 9000, using 16 bits Value 0x40 at index 16, range -9000 -> 9000, using 16 bits Value 0x3F at index 17, range 0 -> 36000, using 16 bits Value 0x41 at index 18, range 0 -> 36000, using 16 bits ************************************************************************** Device at "\\?\hid#vid_056a&pid_0027&col05#7&792ed82&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=056A, Product=0027 (Version 1.7) Manufacturer= Wacom Co.,Ltd. Product= Intuos5 touch M Serial Number= Usage Page: D Input Report Byte Length: 38 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 6 Number of InputValue Caps: 13 Number of InputData Indices: 19 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value X at index 6, range 0 -> 32767, using 16 bits Value Y at index 7, range 0 -> 32767, using 16 bits Value Z at index 8, range 0 -> 1024, using 16 bits Value X at index 9, range 0 -> 2047, using 16 bits Value 0x5B at index 10, range 0 -> 2047, using 32 bits Value 0x5B at index 11, range 0 -> 2047, using 64 bits Value 0x77 at index 12, range 0 -> 2047, using 32 bits Value Y at index 13, range 0 -> 1024, using 16 bits Value 0x3D at index 14, range -9000 -> 9000, using 16 bits Value 0x3E at index 15, range -9000 -> 9000, using 16 bits Value 0x40 at index 16, range -9000 -> 9000, using 16 bits Value 0x3F at index 17, range 0 -> 36000, using 16 bits Value 0x41 at index 18, range 0 -> 36000, using 16 bits ************************************************************************** 172: Error 6 [00000006] returned on HidD_GetAttributes: (\\?\hid#vid_1493&pid_001b#6&34f5874&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) Device at "\\?\hid#vid_1493&pid_001b#6&34f5874&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=007F, Product=0000 (Version 231.22) Manufacturer= Product= Serial Number= Usage Page: 0 Input Report Byte Length: 20 Output Report Byte Length: 0 Feature Report Byte Length: 64512 Number of Link Collection Nodes: 39968 Number of Input Button Caps: 64 Number of InputValue Caps: 20 Number of InputData Indices: 0 Number of Output Button Caps: 39672 Number of Output Value Caps: 64 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 256 Number of Feature Data Indices: 0 Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits ************************************************************************** Device at "\\?\hid#vid_046d&pid_c069#6&1488b66d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=046D, Product=C069 (Version 86.1) Manufacturer= Logitech Product= USB Laser Mouse Serial Number= USB Laser Mouse Device is a mouse Usage Page: 1 Input Report Byte Length: 7 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 4 Number of InputData Indices: 12 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 8 at indices 0 -> 7 Value Y at index 8, range -2047 -> 2047, using 12 bits Value X at index 9, range -2047 -> 2047, using 12 bits Value Wh at index 10, range -127 -> 127, using 8 bits Value Wh at index 11, range -127 -> 127, using 8 bits ************************************************************************** Device at "\\?\hid#vid_046d&pid_c31c&mi_00#8&186e03d5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=046D, Product=C31C (Version 100.0) Manufacturer= Logitech Product= USB Keyboard Serial Number= USB Keyboard Device is a keyboard Usage Page: 1 Input Report Byte Length: 9 Output Report Byte Length: 2 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 264 Number of Output Button Caps: 1 Number of Output Value Caps: 0 Number of Output Data Indices: 5 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_056a&pid_0027&col01#7&792ed82&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=056A, Product=0027 (Version 1.7) Manufacturer= Wacom Co.,Ltd. Product= Intuos5 touch M Serial Number= Usage Page: 1 Input Report Byte Length: 7 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 3 Number of InputData Indices: 8 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 5 at indices 0 -> 4 Value Y at index 5, range 0 -> 32767, using 16 bits Value X at index 6, range 0 -> 32767, using 16 bits Value Wh at index 7, range -127 -> 127, using 8 bits ************************************************************************** ********* FSUIPC4, Version 4.947a by Pete Dowson *********Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"Running inside Prepar3D v3 on Windows 8.0Module base=50530000FSUIPC4 Key is providedWIDEFS7 not user registered, or expired 16 System time = 11/10/2015 13:20:16 16 FLT path = "C:\Users\Walti\Documents\Prepar3D v3 Files\" 16 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 16 Found it: trying to connect 47 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\" 203 #### Initialising Dlrectinput Axis Scanning ... 219 Found correct joystick Id 0 219 ... and a "GUID" value 219 ... okay, Acquired device as #0! 219 ---------------------- Joystick Device Scan ----------------------- 219 Checking: \\?\hid#vid_044f&pid_b10a#6&1255c004&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 219 Product= T.16000M 219 Manufacturer= Thrustmaster 219 Vendor=044F, Product=B10A (Version 5.0) 219 Serial Number= Thrustmaster 219 Checking: \\?\hid#vid_056a&pid_0027&col02#7&792ed82&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 219 Checking: \\?\hid#vid_046d&pid_c31c&mi_01&col01#8&3031901a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 219 Checking: \\?\hid#vid_056a&pid_0027&col03#7&792ed82&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 219 Checking: \\?\hid#vid_046d&pid_c31c&mi_01&col02#8&3031901a&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 219 Checking: \\?\hid#vid_046d&pid_c31c&mi_01&col03#8&3031901a&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 219 Checking: \\?\hid#vid_056d&pid_0002#8&260220fe&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 235 Checking: \\?\hid#vid_056a&pid_0027&col04#7&792ed82&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} 235 Checking: \\?\hid#vid_056a&pid_0027&col05#7&792ed82&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030} 235 Checking: \\?\hid#vid_1493&pid_001b#6&34f5874&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 11, 2015 Report Share Posted October 11, 2015 it's crazy, but at the moment fsuipc 4.947a is not working anymore even with extra logging files! Another USB HID device seems to have "come alive", but it is causing the error: From HidScanner: 172: Error 6 [00000006] returned on HidD_GetAttributes: (\\?\hid#vid_1493&pid_001b#6&34f5874&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) Device at "\\?\hid#vid_1493&pid_001b#6&34f5874&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=007F, Product=0000 (Version 231.22) Manufacturer= Product= Serial Number= and, not coincidentally I'm sure, the last device being scanned by FSUIPC is that one, here: 235 Checking: \\?\hid#vid_1493&pid_001b#6&34f5874&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} So it looks like some sort of odd, (not quite valid or normal?), device recorded in Windows, and FSUIPC not properly handling that error 6 return. I think I can track that down now. Thanks very much for the feedback! Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 11, 2015 Report Share Posted October 11, 2015 Could you try FSUIPC 4.947b, just uploaded, please? I've done all I can to avoid a problem with odd devices during the scan. I'm still not totally sure how HidScanner got away with it when FSUIPC didn't! The code is almost identical. Anyway, I've included more precautionary checked. Thanks, Pete Link to comment Share on other sites More sharing options...
RCFlyer Posted October 11, 2015 Report Share Posted October 11, 2015 Pete: I tried 4.947b in P3DV3, windows 10. It crashed shortly after loading. Log follows: ********* FSUIPC4, Version 4.947b by Pete Dowson ********* Reading options from "I:\P3DV3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10.0 Module base=66070000 User Name="Danny Rice" User Addr="danny.rice@comcast.net" FSUIPC4 Key is provided WideFS7 Key is provided 0 System time = 11/10/2015 10:38:20 47 FLT UNC path = "\\DANNY-PC\Users\Danny\Documents\Prepar3D v3 Files\" 47 Trying I:\P3DV3\Modules\SimConnectP3D2.dll 47 !!! Error 126: The specified module could not be found. 78 Trying to connect to SimConnect Acc/SP2 Oct07 ... 172 FS UNC path = "\\DANNY-PC\P3DV3\P3DV3\" 453 Finished: 0 Profile files created 515 ---------------------- Joystick Device Scan ----------------------- 515 Product= Logitech Extreme 3D Pro 515 Manufacturer= Logitech 515 Vendor=046D, Product=C215 (Version 53.0) 515 Serial Number= Logitech 515 Product= Pro Flight Cessna Yoke 515 Manufacturer= Saitek 515 Vendor=06A3, Product=0BD3 (Version 1.22) 515 Serial Number= RD002687 515 Product= Saitek Pro Flight Rudder Pedals 515 Manufacturer= Saitek 515 Vendor=06A3, Product=0763 (Version 1.0) 515 Serial Number= Saitek 531 Product= Saitek Pro Flight Quadrant 531 Manufacturer= Saitek 531 Vendor=06A3, Product=0C2D (Version 2.0) 531 Serial Number= Saitek 531 Product= T.16000M 531 Manufacturer= Thrustmaster 531 Vendor=044F, Product=B10A (Version 5.0) 531 Serial Number= Thrustmaster 531 Product= Joystick - HOTAS Warthog 531 Manufacturer= Thustmaster 531 Vendor=044F, Product=0402 (Version 1.0) 531 Serial Number= Thustmaster 531 ------------------------------------------------------------------- 875 LogOptions=10000000 00000001 875 ------------------------------------------------------------------- 875 ------ Setting the hooks and direct calls into the simulator ------ 875 --- CONTROLS timer memory location obtained ok 875 --- SIM1 Frictions access gained 875 --- FS Controls Table located ok 875 --- Installed Mouse Macro hooks ok. 875 --- Wind smoothing fix is installed 875 --- All links checked okay 875 ------------------------------------------------------------------- 875 VRI port 1 "com7" failed to open 875 SimConnect_Open succeeded: waiting to check version okay 875 Trying to use SimConnect Acc/SP2 Oct07 38156 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 38156 Initialising SimConnect data requests now 38156 FSUIPC Menu entry added 38297 \\DANNY-PC\Users\Danny\Documents\Prepar3D v3 Files\UH60 at KOLM.fxml 38297 \\DANNY-PC\P3DV3\P3DV3\SimObjects\Rotorcraft\Virtavia Sikorsky H-60 Blackhawk\Blackhawk.air 77156 System time = 11/10/2015 10:39:37, Simulator time = 10:38:59 (17:38Z) 77562 Aircraft="Virtavia Blackhawk 160thSOAR nd" 82156 Starting everything now ... Switched back to 4.946 and everything works fine. Danny Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 11, 2015 Report Share Posted October 11, 2015 I tried 4.947b in P3DV3, windows 10. It crashed shortly after loading. Log follows: Well, whatever is wrong there it isn't related to the earlier reports in this thread. I need the crash details from Windows event viewer please as there's nothing helpful in the log as far as it got. "Starting everything now" iswhere it is all set up and ready to go. Pete Link to comment Share on other sites More sharing options...
RCFlyer Posted October 11, 2015 Report Share Posted October 11, 2015 Pete: The contents of the event log are below. Regards, Danny Version=1 EventType=APPCRASH EventTime=130890587827277781 ReportType=2 Consent=1 UploadTime=130890587828218677 ReportIdentifier=0d7f3fb7-703f-11e5-9c24-c86000c29d6e IntegratorReportIdentifier=881fb0d6-6c82-4880-8264-b7ec769a4ae3 WOW64=1 NsAppName=Prepar3D.exe Response.BucketId=6542c6c70e2f4020d7360cd46d6b27ad Response.BucketTable=1 Response.LegacyBucketId=107651510896 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=Prepar3D.exe Sig[1].Name=Application Version Sig[1].Value=3.0.10.14945 Sig[2].Name=Application Timestamp Sig[2].Value=560b4abe Sig[3].Name=Fault Module Name Sig[3].Value=FSUIPC4.dll Sig[4].Name=Fault Module Version Sig[4].Value=4.9.4.7 Sig[5].Name=Fault Module Timestamp Sig[5].Value=561a7ad2 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=00087172 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.10240.2.0.0.768.101 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=bdcb DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=689d DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=689d12abf00dd47c453b5e1a156c0fa3 UI[2]=I:\P3DV3\Prepar3D.exe UI[3]=Prepar3D exe has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=I:\P3DV3\Prepar3D.exe LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll LoadedModule[4]=C:\WINDOWS\SYSTEM32\USER32.dll LoadedModule[5]=C:\WINDOWS\SYSTEM32\GDI32.dll LoadedModule[6]=C:\WINDOWS\SYSTEM32\ole32.dll LoadedModule[7]=C:\WINDOWS\SYSTEM32\combase.dll LoadedModule[8]=C:\WINDOWS\SYSTEM32\msvcrt.dll LoadedModule[9]=C:\WINDOWS\SYSTEM32\RPCRT4.dll LoadedModule[10]=C:\WINDOWS\SYSTEM32\SspiCli.dll LoadedModule[11]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll LoadedModule[12]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll LoadedModule[13]=C:\WINDOWS\SYSTEM32\sechost.dll LoadedModule[14]=I:\P3DV3\api.dll LoadedModule[15]=C:\WINDOWS\SYSTEM32\MSVCP120.dll LoadedModule[16]=C:\WINDOWS\SYSTEM32\MSVCR120.dll LoadedModule[17]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll LoadedModule[18]=C:\WINDOWS\SYSTEM32\WINHTTP.dll LoadedModule[19]=C:\WINDOWS\SYSTEM32\IMM32.dll LoadedModule[20]=C:\WINDOWS\SYSTEM32\MSCTF.dll LoadedModule[21]=C:\WINDOWS\SYSTEM32\Cabinet.dll LoadedModule[22]=C:\WINDOWS\SYSTEM32\WS2_32.dll LoadedModule[23]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll LoadedModule[24]=C:\WINDOWS\SYSTEM32\NSI.dll LoadedModule[25]=C:\WINDOWS\SYSTEM32\SHELL32.dll LoadedModule[26]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[27]=C:\WINDOWS\SYSTEM32\windows.storage.dll LoadedModule[28]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10240.16384_none_49c02355cf03478c\COMCTL32.dll LoadedModule[29]=C:\WINDOWS\SYSTEM32\shlwapi.dll LoadedModule[30]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[31]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll LoadedModule[32]=C:\WINDOWS\SYSTEM32\shcore.dll LoadedModule[33]=C:\WINDOWS\SYSTEM32\powrprof.dll LoadedModule[34]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[35]=C:\WINDOWS\SYSTEM32\profapi.dll LoadedModule[36]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll LoadedModule[37]=C:\WINDOWS\SYSTEM32\CRYPT32.dll LoadedModule[38]=C:\WINDOWS\SYSTEM32\MSASN1.dll LoadedModule[39]=I:\P3DV3\acontain.dll LoadedModule[40]=I:\P3DV3\ai_player.dll LoadedModule[41]=I:\P3DV3\atc.dll LoadedModule[42]=I:\P3DV3\controls.dll LoadedModule[43]=I:\P3DV3\demo.dll LoadedModule[44]=C:\WINDOWS\SYSTEM32\SETUPAPI.dll LoadedModule[45]=I:\P3DV3\facilities.dll LoadedModule[46]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll LoadedModule[47]=I:\P3DV3\fe.dll LoadedModule[48]=I:\P3DV3\flight.dll LoadedModule[49]=I:\P3DV3\fs-traffic.dll LoadedModule[50]=I:\P3DV3\g2d.dll LoadedModule[51]=I:\P3DV3\g3d.dll LoadedModule[52]=I:\P3DV3\gps.dll LoadedModule[53]=I:\P3DV3\livingwater.dll LoadedModule[54]=I:\P3DV3\main.dll LoadedModule[55]=I:\P3DV3\menus.dll LoadedModule[56]=C:\WINDOWS\SYSTEM32\COMDLG32.dll LoadedModule[57]=I:\P3DV3\multiplayer.dll LoadedModule[58]=I:\P3DV3\pdk.dll LoadedModule[59]=I:\P3DV3\panels.dll LoadedModule[60]=I:\P3DV3\sim1.dll LoadedModule[61]=I:\P3DV3\simscheduler.dll LoadedModule[62]=I:\P3DV3\simprop.dll LoadedModule[63]=I:\P3DV3\sound.dll LoadedModule[64]=I:\P3DV3\symmap.dll LoadedModule[65]=I:\P3DV3\terrain.dll LoadedModule[66]=I:\P3DV3\util.dll LoadedModule[67]=I:\P3DV3\visualfx.dll LoadedModule[68]=I:\P3DV3\weather.dll LoadedModule[69]=I:\P3DV3\window.dll LoadedModule[70]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll LoadedModule[71]=C:\WINDOWS\SYSTEM32\WLDAP32.dll LoadedModule[72]=C:\WINDOWS\SYSTEM32\HID.DLL LoadedModule[73]=C:\WINDOWS\SYSTEM32\USERENV.dll LoadedModule[74]=C:\WINDOWS\SYSTEM32\DSOUND.dll LoadedModule[75]=C:\WINDOWS\SYSTEM32\MSACM32.dll LoadedModule[76]=C:\WINDOWS\SYSTEM32\dxgi.dll LoadedModule[77]=C:\WINDOWS\SYSTEM32\d3d9.dll LoadedModule[78]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[79]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_43.dll LoadedModule[80]=C:\WINDOWS\SYSTEM32\OPENGL32.dll LoadedModule[81]=C:\WINDOWS\SYSTEM32\GLU32.dll LoadedModule[82]=C:\WINDOWS\SYSTEM32\d3dx9_43.dll LoadedModule[83]=C:\WINDOWS\SYSTEM32\d3dx11_43.dll LoadedModule[84]=C:\WINDOWS\SYSTEM32\DDRAW.dll LoadedModule[85]=C:\WINDOWS\SYSTEM32\dwmapi.dll LoadedModule[86]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll LoadedModule[87]=I:\P3DV3\language.dll LoadedModule[88]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[89]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[90]=C:\Program Files (x86)\RivaTuner Statistics Server\RTSSHooks.dll LoadedModule[91]=C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9158_none_5091b51ebcb97cdc\MSVCR90.dll LoadedModule[92]=C:\WINDOWS\SYSTEM32\clbcatq.dll LoadedModule[93]=C:\WINDOWS\system32\nvspcap.dll LoadedModule[94]=C:\WINDOWS\SYSTEM32\PSAPI.DLL LoadedModule[95]=C:\WINDOWS\system32\nvapi.dll LoadedModule[96]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[97]=C:\WINDOWS\SYSTEM32\d3d10.dll LoadedModule[98]=C:\WINDOWS\SYSTEM32\d3d10core.dll LoadedModule[99]=C:\WINDOWS\SYSTEM32\MSXML6.DLL LoadedModule[100]=C:\WINDOWS\SYSTEM32\ntmarta.dll LoadedModule[101]=C:\WINDOWS\SYSTEM32\PROPSYS.dll LoadedModule[102]=I:\P3DV3\uiInterface.dll LoadedModule[103]=C:\WINDOWS\SYSTEM32\mscoree.dll LoadedModule[104]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll LoadedModule[105]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll LoadedModule[106]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll LoadedModule[107]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll LoadedModule[108]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[109]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[110]=C:\WINDOWS\SYSTEM32\dwrite.dll LoadedModule[111]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll LoadedModule[112]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll LoadedModule[113]=C:\WINDOWS\SYSTEM32\iphlpapi.dll LoadedModule[114]=C:\WINDOWS\SYSTEM32\WINNSI.DLL LoadedModule[115]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL LoadedModule[116]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL LoadedModule[117]=C:\WINDOWS\SYSTEM32\DNSAPI.dll LoadedModule[118]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll LoadedModule[119]=C:\WINDOWS\System32\fwpuclnt.dll LoadedModule[120]=C:\Windows\System32\rasadhlp.dll LoadedModule[121]=C:\WINDOWS\SYSTEM32\nvwgf2um.dll LoadedModule[122]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL LoadedModule[123]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[124]=C:\WINDOWS\SYSTEM32\apphelp.dll LoadedModule[125]=C:\Program Files (x86)\FileZilla FTP Client\fzshellext.dll LoadedModule[126]=C:\WINDOWS\system32\ntshrui.dll LoadedModule[127]=C:\WINDOWS\system32\srvcli.dll LoadedModule[128]=C:\WINDOWS\SYSTEM32\cscapi.dll LoadedModule[129]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10240.16384_none_3bccb1ff6bcd1849\comctl32.dll LoadedModule[130]=C:\WINDOWS\system32\netutils.dll LoadedModule[131]=C:\WINDOWS\SYSTEM32\coml2.dll LoadedModule[132]=C:\WINDOWS\system32\mssprxy.dll LoadedModule[133]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[134]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[135]=C:\WINDOWS\SYSTEM32\wintypes.dll LoadedModule[136]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll LoadedModule[137]=C:\WINDOWS\SYSTEM32\urlmon.dll LoadedModule[138]=C:\WINDOWS\SYSTEM32\iertutil.dll LoadedModule[139]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll LoadedModule[140]=C:\WINDOWS\SYSTEM32\nvd3dum.dll LoadedModule[141]=I:\P3DV3\Gauges\TargetInfo.dll LoadedModule[142]=C:\WINDOWS\SYSTEM32\wdmaud.drv LoadedModule[143]=C:\WINDOWS\SYSTEM32\ksuser.dll LoadedModule[144]=C:\WINDOWS\SYSTEM32\AVRT.dll LoadedModule[145]=C:\WINDOWS\SYSTEM32\msacm32.drv LoadedModule[146]=C:\WINDOWS\SYSTEM32\midimap.dll LoadedModule[147]=I:\P3DV3\radar.dll LoadedModule[148]=I:\P3DV3\D3DCOMPILER_47.dll LoadedModule[149]=I:\P3DV3\Oculus.dll LoadedModule[150]=C:\WINDOWS\SYSTEM32\dbghelp.dll LoadedModule[151]=I:\P3DV3\ControllableCamera.dll LoadedModule[152]=I:\P3DV3\Modules\FSUIPC4.dll LoadedModule[153]=C:\WINDOWS\SYSTEM32\DINPUT8.dll LoadedModule[154]=C:\WINDOWS\SYSTEM32\SHFolder.DLL LoadedModule[155]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[156]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9185_none_d0905a48442809b8\MSVCR80.dll LoadedModule[157]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9185_none_d0905a48442809b8\MSVCP80.dll LoadedModule[158]=C:\WINDOWS\SYSTEM32\DINPUT.DLL LoadedModule[159]=C:\WINDOWS\SYSTEM32\WINTRUST.dll LoadedModule[160]=I:\P3DV3\Modules\OpusPDK_v3.DLL LoadedModule[161]=C:\WINDOWS\SYSTEM32\MSVCR100.dll LoadedModule[162]=I:\P3DV3\Modules\DafWings.dll LoadedModule[163]=C:\WINDOWS\SYSTEM32\DPLAYX.dll LoadedModule[164]=C:\WINDOWS\SYSTEM32\MSIMG32.dll LoadedModule[165]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV LoadedModule[166]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10240.16384_none_d15682eeaf714889\gdiplus.dll LoadedModule[167]=C:\WINDOWS\SYSTEM32\OLEACC.dll LoadedModule[168]=C:\WINDOWS\SYSTEM32\WININET.dll LoadedModule[169]=C:\WINDOWS\SYSTEM32\RICHED32.DLL LoadedModule[170]=C:\WINDOWS\SYSTEM32\RICHED20.dll LoadedModule[171]=C:\WINDOWS\SYSTEM32\USP10.dll LoadedModule[172]=C:\WINDOWS\SYSTEM32\msls31.dll LoadedModule[173]=I:\P3DV3\SimDirector.dll LoadedModule[174]=I:\P3DV3\BGLCompLib.dll LoadedModule[175]=I:\P3DV3\simpropext.dll LoadedModule[176]=C:\WINDOWS\SYSTEM32\XInput1_4.dll LoadedModule[177]=C:\WINDOWS\system32\wbem\wbemprox.dll LoadedModule[178]=C:\WINDOWS\SYSTEM32\wbemcomn.dll LoadedModule[179]=C:\WINDOWS\system32\wbem\wbemsvc.dll LoadedModule[180]=C:\WINDOWS\system32\wbem\fastprox.dll LoadedModule[181]=I:\Addons\gauges\AS532AFCP.gau LoadedModule[182]=I:\P3DV3\HAPX.DLL LoadedModule[183]=C:\WINDOWS\SYSTEM32\mscms.dll LoadedModule[184]=C:\WINDOWS\SYSTEM32\WindowsCodecsExt.dll LoadedModule[185]=C:\WINDOWS\SYSTEM32\icm32.dll LoadedModule[186]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\webengine4.dll LoadedModule[187]=C:\Program Files (x86)\HIDMacro\Winhook.dll LoadedModule[188]=C:\WINDOWS\system32\dataexchange.dll LoadedModule[189]=C:\WINDOWS\system32\d2d1.dll LoadedModule[190]=C:\WINDOWS\system32\dcomp.dll LoadedModule[191]=C:\WINDOWS\system32\twinapi.appcore.dll LoadedModule[192]=C:\WINDOWS\system32\msctfui.dll LoadedModule[193]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll LoadedModule[194]=C:\WINDOWS\SYSTEM32\msiltcfg.dll LoadedModule[195]=C:\WINDOWS\SYSTEM32\msi.dll LoadedModule[196]=C:\WINDOWS\SYSTEM32\sxs.dll LoadedModule[197]=C:\Windows\SYSTEM32\ieframe.dll LoadedModule[198]=C:\Windows\SYSTEM32\mshtml.dll LoadedModule[199]=C:\WINDOWS\SYSTEM32\ieapfltr.dll LoadedModule[200]=C:\Windows\System32\vaultcli.dll LoadedModule[201]=C:\WINDOWS\SYSTEM32\Secur32.dll LoadedModule[202]=C:\WINDOWS\SYSTEM32\MLANG.dll LoadedModule[203]=I:\P3DV3\TritonResources\vc12\win32\TritonCUDA-MT-DLL.dll LoadedModule[204]=I:\P3DV3\TritonResources\dll\cudart32_42_9.dll LoadedModule[205]=I:\P3DV3\TritonResources\dll\cufft32_42_9.dll LoadedModule[206]=C:\WINDOWS\SYSTEM32\MSVCP100.dll LoadedModule[207]=C:\WINDOWS\SYSTEM32\nvcuda.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Prepar3D exe AppPath=I:\P3DV3\Prepar3D.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=EF24156912BB64EBC47D28B48728A7DC Link to comment Share on other sites More sharing options...
Pete Dowson Posted October 11, 2015 Report Share Posted October 11, 2015 Please download FSUIPC 4.947c, now available. Pete Link to comment Share on other sites More sharing options...
Walter Aeschbach Posted October 12, 2015 Report Share Posted October 12, 2015 Hi Pete, it works now for me (4.947c). I started prepar3d about six times and every time it worked perfectly :-) Thanks a lot. Walter Link to comment Share on other sites More sharing options...
BoxxMann Posted October 12, 2015 Author Report Share Posted October 12, 2015 4.947c works for p3d v2.5/v3 and FSX:SE. I also tested 4.947d with p3dv3 and all is good there. Thanks, Pete! Link to comment Share on other sites More sharing options...
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