birdguy Posted July 24, 2017 Report Share Posted July 24, 2017 My keyboard is dead after starting P3Dv4. I have to start the Task Manager and then just close it to get the keyboard to work. Everything runs fine after that. My Saitek X52 works fine on startup, only the keyboard is dead. My log below: ********* FSUIPC5, Version 5.103 (26th June 2017) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FED83A0000 Windows 7 Professional 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1) Sailplane.exe version = 4.0.28.21686 Checking the Registrations now ... User Name="Noel Sivertson" User Addr="birdguy@cableone.net" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 0 System time = 23/07/2017 21:53:24 0 FLT path = "C:\Users\Noel\Documents\Prepar3D v4 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 4.0.28.21686 0 api.dll: 4.0.28.21686 0 controls.dll: 4.0.28.21686 0 fs-traffic.dll: 4.0.28.21686 0 G3D.dll: 4.0.28.21686 0 language.dll: 4.0.28.21686 0 sim1.dll: 4.0.28.21686 0 visualfx.dll: 4.0.28.21686 0 weather.dll: 4.0.28.21686 0 window.dll: 4.0.28.21686 0 ---------------------------------- 16 FS path = "D:\Lockheed Martin\Prepar3D v4\" 125 ---------------------- Joystick Device Scan ----------------------- 125 Product= Saitek X52 Flight Control System 125 Manufacturer= Saitek 125 Vendor=06A3, Product=075C (Version 1.0) 141 GUIDs returned for product: VID_06A3&PID_075C: 141 GUID= {68843CD0-533F-11E5-8001-444553540000} 141 Details: Btns=34, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V1023,X2047,Y2047,Z255 141 ------------------------------------------------------------------- 141 Device acquired for use: 141 Joystick ID = 0 (Registry okay) 141 0=Saitek X52 Flight Control System 141 0.GUID={68843CD0-533F-11E5-8001-444553540000} 141 ------------------------------------------------------------------- 156 LogOptions=00000000 00000001 156 SimConnect_Open succeeded: waiting to check version okay 156 Opened separate AI Traffic client okay 55427 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.28.21686 (SimConnect: 4.0.0.0) 55459 Initialising SimConnect data requests now 55474 FSUIPC Menu entry added 55505 ... Using Prepar3D with Academic License 55505 C:\Users\Noel\Documents\Prepar3D v4 Files\ZZZ_Sailplane.fxml 55505 D:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DG808S\DG808S.air 131244 Aircraft loaded: running normally now ... 131244 User Aircraft ID 2 supplied, now being used 132055 System time = 23/07/2017 21:55:36, Simulator time = 14:51:35 (21:51Z) 132055 Aircraft="DG808S" 139060 Starting everything now ... 140214 Advanced Weather Interface Enabled 162460 Sim stopped: average frame rate for last 31 secs = 22.2 fps 162460 Max AI traffic was 1180 aircraft (Deleted 0) 165939 === Closing session: waiting for DLLStop to be called ... 175189 === DLLStop called ... 175189 === Closing external processes we started ... 176188 === About to kill any Lua plug-ins still running ... 176344 === Closing global Lua thread 177342 === About to kill my timers ... 177545 === Restoring window procs ... 177545 === Unloading libraries ... 177545 === stopping other threads ... 177545 === ... Button scanning ... 177639 === ... Axis scanning ... 177748 === Releasing joystick devices ... 177748 === Freeing macro memory 177748 === Removing any offset overrides 177748 === Clearing any displays left 177748 === Calling SimConnect_Close ... 179838 === SimConnect_Close done! 179838 === AI slots deleted! 179838 === Freeing button memory ... 179838 === Closing my Windows ... 179838 === Freeing FS libraries ... 180852 === Closing devices ... 180852 === Closing the Log ... Bye Bye! ... 180852 System time = 23/07/2017 21:56:25, Simulator time = 14:52:05 (21:52Z) 180852 *** FSUIPC log file being closed Minimum frame rate was 19.2 fps, Maximum was 23.0 fps Average frame rate for running time of 31 secs = 22.2 fps Maximum AI traffic for session was 1180 aircraft Memory managed: 14 Allocs, 13 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Thomas Richter Posted July 24, 2017 Report Share Posted July 24, 2017 Hi, did you try with latest interim version from download area? Thomas Link to comment Share on other sites More sharing options...
birdguy Posted July 24, 2017 Author Report Share Posted July 24, 2017 I have version 5,103 (25th June 2017) installed. I don't see a later one in the downloads section. Noel Link to comment Share on other sites More sharing options...
Thomas Richter Posted July 24, 2017 Report Share Posted July 24, 2017 Hi, above this Forum, Download Links -> Updated Modules ... FSUIPC version 5.103j only, for those with 5.103 or ... Thomas Link to comment Share on other sites More sharing options...
birdguy Posted July 24, 2017 Author Report Share Posted July 24, 2017 Still no joy Thomas. I downloaded version 5.103j and installed FSUIPC5.dll and GFDev64.dll into the modules folder and overwrote the old FSUIPC5.dll and then rebooted (cold reboot) my computer and the problem is still there. It's not a catastrophic thing. Once I bring up the Task Manager and then shut it down the keyboard works normally. It's only the keyboard that's disabled, not the Saitek controls. Noel Link to comment Share on other sites More sharing options...
birdguy Posted July 25, 2017 Author Report Share Posted July 25, 2017 It's not your problem Thomas. I disabled FSUIPC.dll in the modules folder and the problem persists. I'll have to look elsewhere for the solution. Sorry to have troubled you. Noel 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