Pete Dowson Posted November 1, 2015 Report Posted November 1, 2015 Thomas, to repeat, is there any possibility of me seeing the Log from the "worked flawlessly" run, please? I need to check through that what it is doing is what I think it should be doing. That was the point of you volunteering to test it for me! When I'm confident it is doing all the right things I can make a formal release. Thanks. Pete
Thomas Greer Posted November 5, 2015 Author Report Posted November 5, 2015 Sorry Pete for the delayed response. My PC took a funny turn and I couldn't start P3D. All seems good now. Here is the log. ********* FSUIPC4, Version 4.947i by Pete Dowson ********* Reading options from "J:\P3D\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=5A350000 User Name="Thomas Greer" User Addr="greerthomas@me.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 515 System time = 05/11/2015 18:18:08 515 FLT path = "C:\Users\user\Documents\Prepar3D v3 Files\" 515 Trying J:\P3D\Modules\SimConnectP3D2.dll 578 Found it: trying to connect 594 FS path = "J:\P3D\" 750 #### Initialising Dlrectinput Axis Scanning ... 765 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0" 765 Found correct joystick Id 0 765 ... and a "GUID" value 781 ... okay, Acquired device as #0 797 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0BAC\Calibration\0" 797 Found correct joystick Id 1 797 ... and a "GUID" value 797 ... okay, Acquired device as #1 797 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\0" 797 Found correct joystick Id 2 797 ... and a "GUID" value 797 ... okay, Acquired device as #2 812 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\0" 812 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\1" 812 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\2" 812 Found correct joystick Id 3 812 ... and a "GUID" value 812 ... okay, Acquired device as #3 844 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\0" 844 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0461&PID_4E25\Calibration\1" 844 Found correct joystick Id 4 844 ... and a "GUID" value 844 ... okay, Acquired device as #4 922 ---------------------- Joystick Device Scan ----------------------- 922 Checking: \\?\hid#vid_0461&pid_4e25&mi_01&col04#8&b8180dc&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#saitekkeyboard#2&1e0e23ca&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#saitekmouse#2&7354a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_1b1c&pid_0a06&mi_03#8&1656656c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_0461&pid_4e25&mi_01&col01#8&b8180dc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_0461&pid_4e25&mi_02#8&1855bce6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_0461&pid_4e25&mi_01&col02#8&b8180dc&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_06a3&pid_0763#7&fa88d7b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Product= Saitek Pro Flight Rudder Pedals 922 Manufacturer= Saitek 922 Vendor=06A3, Product=0763 (Version 1.1) 922 Serial Number= Saitek 922 Checking: \\?\hid#vid_0461&pid_4e25&mi_00#8&2f58be9e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_06a3&pid_0bac#8&2cdfde68&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Product= Saitek Pro Flight Yoke 922 Manufacturer= Saitek 922 Vendor=06A3, Product=0BAC (Version 3.4) 922 Serial Number= Saitek 922 Checking: \\?\hid#vid_0461&pid_4e25&mi_01&col03#8&b8180dc&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Product= HP Wireless Keyboard Kit 922 Manufacturer= Hewlett Packard 922 Vendor=0461, Product=4E25 (Version 1.50) 922 Serial Number= Hewlett Packard 922 Checking: \\?\hid#saitekhotkeys#2&15d37534&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_062a&pid_3286&mi_00#8&3304aab0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_062a&pid_3286&mi_01&col01#8&31ee8380&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_062a&pid_3286&mi_01&col02#8&31ee8380&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_062a&pid_3286&mi_01&col03#8&31ee8380&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 Checking: \\?\hid#vid_062a&pid_3286&mi_01&col04#8&31ee8380&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} 922 ------------------------------------------------------------------- 922 #### Completed Dlrectinput Axis Scanning 922 ---------- Making INI JoyNames Section ---------- 922 Joy#0: finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0763\" 922 Joy#0: OEMName = "Saitek Pro Flight Rudder Pedals" 922 Joy#0: GUID = {1D58BA90-7763-11E5-8006-444553540000} 922 Joy#1: finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0BAC\" 922 Joy#1: OEMName = "Saitek Pro Flight Yoke" 922 Joy#1: GUID = {BFA06680-7A2F-11E5-8001-444553540000} 922 Joy#2: finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0461&PID_4E25\" 922 Joy#2: OEMName = "HP Wireless Keyboard Kit" 922 Joy#2: GUID = {1D5670A0-7763-11E5-8001-444553540000} 922 Joy#3: finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0461&PID_4E25\" 922 Joy#3: OEMName = "HP Wireless Keyboard Kit" 922 Joy#3: GUID = {1D581E50-7763-11E5-8003-444553540000} 922 Joy#4: finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0461&PID_4E25\" 922 Joy#4: OEMName = "HP Wireless Keyboard Kit" 922 Joy#4: GUID = {1D581E50-7763-11E5-8002-444553540000} 922 ------------------------------------------------- 937 LogOptions=00000000 02000011 937 ------------------------------------------------------------------- 937 ------ Setting the hooks and direct calls into the simulator ------ 937 --- CONTROLS timer memory location obtained ok 937 --- SIM1 Frictions access gained 937 --- FS Controls Table located ok 937 --- Installed Mouse Macro hooks ok. 937 --- Wind smoothing fix is installed 937 --- All links okay (except older global weather setting method) 937 ------------------------------------------------------------------- 937 SimConnect_Open succeeded: waiting to check version okay 937 Trying to use SimConnect Prepar3D 1578 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 2640 Memory in use: 652Mb, Avail=3444Mb 61703 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 61703 Initialising SimConnect data requests now 61703 FSUIPC Menu entry added 61719 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 61719 C:\Users\user\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 61719 J:\P3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 71781 Memory in use: 1081Mb, Avail=3015Mb 132156 Memory in use: 1064Mb, Avail=3032Mb 208109 === NOTE: not calling SimConnect_Close ... 209125 System time = 05/11/2015 18:21:37 209125 *** FSUIPC log file being closed Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps Minimum available memory recorded was 32768Mb Memory managed: 4 Allocs, 4 Freed ********* FSUIPC Log file closed ***********
Pete Dowson Posted November 5, 2015 Report Posted November 5, 2015 Sorry Pete for the delayed response. My PC took a funny turn and I couldn't start P3D. All seems good now. Here is the log. Thanks, but was that after you used JoyIDs to renumber the pedals and yoke back as devices 1 and 2? The fact that the log is from a session with today's date seems to indicate it isn't the test run at all. It looks more like they had already been renumbered as 4 and 5 as per your previous test. I was hoping really to see confirmation that FSUIPC had done the renumbering from 1/2 to 4/5. That was the purpose of the test. Pete
Thomas Greer Posted November 5, 2015 Author Report Posted November 5, 2015 JoyIDs still show them both as 1 and 2.
Pete Dowson Posted November 5, 2015 Report Posted November 5, 2015 JoyIDs still show them both as 1 and 2. Hmm. That's strange. So FSUIPC has not changed the numbers fully -- if it had JoyIDs would have seen the change too. Here, if I force the change JoyIDs sees that, so there must be something else different in your system. I'll have to examine what other parts of the Registry JoyIDs examines. Ah, well .... that's for next week. I'm away for the next three days. Thanks for your help. I'll have to take it alone from here. If I get a version made which I think ought to fix it fully, including JoyIDs, perhaps you could then test it for me? To that end I think it might be best for me to contact you by email. Could you send me confirmation to petedowson@btconnect.com so that I have a way of responding, please? Pete
Pete Dowson Posted November 9, 2015 Report Posted November 9, 2015 same problem for me What "same problem"? It's no use at all adding such a comment to a three-page thread with all sorts of things going on and matters fully resolved for the user. Have you actually read any of it? Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now