Sabrefly Posted February 27, 2017 Report Share Posted February 27, 2017 This one is longer now: ********* FSUIPC4, Version 4.963d (27th February 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.3.5.17625 Reading options from "F:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=565C0000 User Name="Igor Petrov" User Addr="petrovigor@umail.ru" FSUIPC4 Key is provided WideFS7 Key is provided 0 System time = 27/02/2017 21:53:16 0 FLT UNC path = "\\I6\Prepar3D v3 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 3.3.5.17625 0 api.dll: 3.3.5.17625 0 controls.dll: 3.3.5.17625 0 fs-traffic.dll: 3.3.5.17625 0 G3D.dll: 3.3.5.17625 0 language.dll: 3.3.5.17625 0 sim1.dll: 3.3.5.17625 0 visualfx.dll: 3.3.5.17625 0 weather.dll: 3.3.5.17625 0 window.dll: 3.3.5.17625 0 ---------------------------------- 0 Trying F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 16 Found it: trying to connect 16 FS UNC path = "\\I6\Prepar3D v3\" 78 #### Initialising Dlrectinput Axis Scanning ... 78 EnumDevices: 0.GUID={C82A9610-1924-11E6-8001-444553540000} 78 EnumDevices: 1.GUID={6353CB80-18FC-11E6-8003-444553540000} 78 EnumDevices: 2.GUID={C82C6AD0-1924-11E6-8002-444553540000} 78 EnumDevices: 3.GUID={C87A3CB0-1924-11E6-8003-444553540000} 78 EnumDevices: 4.GUID={C87B2710-1924-11E6-8004-444553540000} 78 EnumDevices: 6.GUID={E21EB120-1927-11E6-8001-444553540000} 94 EnumDevices: found CH Control Manager Device 2 94 EnumDevices: GUID matches our device 0 Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 27, 2017 Author Report Share Posted February 27, 2017 Please show me the log using this one: FSUIPC4963e_TEST.zip So far I've only tested on Win 7. I'll see if I can connect my two game controller devices to my one and only Win10 PC. -- not easy. it's only got one USB port so I need to free up a USB hub from somewhere ... :-( Pete Link to comment Share on other sites More sharing options...
Sabrefly Posted February 27, 2017 Report Share Posted February 27, 2017 It's almost the same,.Pete: ********* FSUIPC4, Version 4.963e (27th February 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.3.5.17625 Reading options from "F:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=57760000 User Name="Igor Petrov" User Addr="petrovigor@umail.ru" FSUIPC4 Key is provided WideFS7 Key is provided 16 System time = 27/02/2017 22:54:33 16 FLT UNC path = "\\I6\Prepar3D v3 Files\" 16 ------ Module Version Check ------ 16 acontain.dll: 3.3.5.17625 16 api.dll: 3.3.5.17625 16 controls.dll: 3.3.5.17625 16 fs-traffic.dll: 3.3.5.17625 16 G3D.dll: 3.3.5.17625 16 language.dll: 3.3.5.17625 16 sim1.dll: 3.3.5.17625 16 visualfx.dll: 3.3.5.17625 16 weather.dll: 3.3.5.17625 16 window.dll: 3.3.5.17625 16 ---------------------------------- 16 Trying F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 16 Found it: trying to connect 16 FS UNC path = "\\I6\Prepar3D v3\" 94 #### Initialising Dlrectinput Axis Scanning ... 94 EnumDevices: 0.GUID={C82A9610-1924-11E6-8001-444553540000} 94 EnumDevices: 1.GUID={6353CB80-18FC-11E6-8003-444553540000} 94 EnumDevices: 2.GUID={C82C6AD0-1924-11E6-8002-444553540000} 94 EnumDevices: 3.GUID={C87A3CB0-1924-11E6-8003-444553540000} 94 EnumDevices: 4.GUID={C87B2710-1924-11E6-8004-444553540000} 94 EnumDevices: 6.GUID={E21EB120-1927-11E6-8001-444553540000} 109 Entered EnumDevices callback ... 203 EnumDevices: found CH Control Manager Device 2 203 EnumDevices: GUID matches our device 0 Thanks! Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 27, 2017 Author Report Share Posted February 27, 2017 Managed to test on Win10 ... and I get EXACTLY the same results. It's a Win10 bug!!!! Drat. Win10 is the main one with the Joystick ID missing problems, and the very function I found which would enable it to be fixed is broken! :-( Not sure what I can do about this ... I'll experiment here. Pete Link to comment Share on other sites More sharing options...
Sabrefly Posted February 27, 2017 Report Share Posted February 27, 2017 12 minutes ago, Pete Dowson said: Managed to test on Win10 ... and I get EXACTLY the same results. It's a Win10 bug!!!! Drat. Win10 is the main one with the Joystick ID missing problems, and the very function I found which would enable it to be fixed is broken! :-( Not sure what I can do about this ... I'll experiment here. Pete Strange, with all my joysticks and HIDs I've never had a problem with Win10 doesn't recognize or changes them Thank you! Igor. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 27, 2017 Author Report Share Posted February 27, 2017 41 minutes ago, Sabrefly said: Strange, with all my joysticks and HIDs I've never had a problem with Win10 doesn't recognize or changes them It's just this one function. The callback is supposed to be repeated called by Windows until either I say enough or it says there's no more. Once I've invoked this procedure it's out of my control, theonly code in my program is when it calls me. The logging shows it simply doesn't call me after the first device. I've posted this as a question on MSDN but i'm not hopeful for an answer that way. It looks like I'll have to test for Win10 and not include this improvement (on the very system in which it is most needed!). Such a shame. I'll continue to look for a solution. Maybe sleeping on it will give me some bright idea. Pete Link to comment Share on other sites More sharing options...
Sabrefly Posted February 27, 2017 Report Share Posted February 27, 2017 4 minutes ago, Pete Dowson said: I'll continue to look for a solution. Maybe sleeping on it will give me some bright idea. Pete Thank you very much, Pete. Please let me know when you need further tests on Win10. Igor. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 28, 2017 Author Report Share Posted February 28, 2017 Okay! The work-around is to enumerate All devices, not just Attached devices. Somehow they've broken the "attached" device checking in Win10, as it works fine in Win7. I've modified my code to cope, and have already uploaded 4.963f to the Download Llinks subforum. Please use that. I'd like to see the log still please, but only with the "LogExtras=x200000 parameter set if there's still a problem. Pete Link to comment Share on other sites More sharing options...
Sabrefly Posted February 28, 2017 Report Share Posted February 28, 2017 (edited) v4.963f has been withdrawn, is a newer one coming? Thanks, v4.963f is still a problem, I'll post the log shortly. Edited February 28, 2017 by Sabrefly Link to comment Share on other sites More sharing options...
Sabrefly Posted February 28, 2017 Report Share Posted February 28, 2017 ********* FSUIPC4, Version 4.963f (28th February 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.3.5.17625 Reading options from "F:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=55E40000 User Name="Igor Petrov" User Addr="petrovigor@umail.ru" FSUIPC4 Key is provided WideFS7 Key is provided 0 System time = 01/03/2017 00:23:42 0 FLT UNC path = "\\I6\Prepar3D v3 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 3.3.5.17625 0 api.dll: 3.3.5.17625 0 controls.dll: 3.3.5.17625 0 fs-traffic.dll: 3.3.5.17625 0 G3D.dll: 3.3.5.17625 0 language.dll: 3.3.5.17625 0 sim1.dll: 3.3.5.17625 0 visualfx.dll: 3.3.5.17625 0 weather.dll: 3.3.5.17625 0 window.dll: 3.3.5.17625 0 ---------------------------------- 0 Trying F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 0 Found it: trying to connect 15 FS UNC path = "\\I6\Prepar3D v3\" 78 #### Initialising Dlrectinput Axis Scanning ... 78 EnumDevices: 0.GUID={C82A9610-1924-11E6-8001-444553540000} 78 EnumDevices: 1.GUID={6353CB80-18FC-11E6-8003-444553540000} 78 EnumDevices: 2.GUID={C82C6AD0-1924-11E6-8002-444553540000} 78 EnumDevices: 3.GUID={C87A3CB0-1924-11E6-8003-444553540000} 78 EnumDevices: 4.GUID={C87B2710-1924-11E6-8004-444553540000} 78 EnumDevices: 6.GUID={E21EB120-1927-11E6-8001-444553540000} 93 Entered EnumDevices callback ... 187 EnumDevices: found CH Control Manager Device 2 187 EnumDevices: GUID matches our device 0 Thanks, Igor. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 28, 2017 Author Report Share Posted February 28, 2017 2 hours ago, Sabrefly said: v4.963f has been withdrawn, is a newer one coming? Thanks, v4.963f is still a problem, I'll post the log shortly. Don't use anything later than 4.963 on Win10 at all, until I release 4.964. I've had to revert back to the older joystick scanning. The new one, which looks so good on Win7, is simply using broken facilities on Win10. Maybe I'll try again in 6 months or a year in the hope that MS will fix it. 4.964 will be 4.963 with a couple of other fixes, not relevant here. 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