cmercier Posted July 31, 2017 Report Posted July 31, 2017 Hi Pete, I just did a clean reinstall of FSX:SE and immediately reinstalled FSUIPC v4.949d. When the module is enabled, FSX crashes not without first telling me that FS had a problem with FSUIPC. If I disable the module FS launches correctly. I assume something left over from the previous install in the config or registry entries is causing FS to crash, but I cannot find the culprit I'm attaching the following files: FSUIPC4 Install.log, FSUIPC.log and the Windows Event log: Hop you can help me out Thanks Christophe Mercier FSUIPC4 Install.log Quote Installer for FSUIPC4.DLL version 4.969 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=F:\Steam\steamapps\common\FSX Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX Parameter"Install_Path" ... >>> OK! FOUND FSX-SE! <<< ... SetupPath=F:\Steam\steamapps\common\FSX ************ BUT this is the same path as for FSX! Will only install for FSX-SE ************ Looking in registry for Prepar3D v1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX-SE: SetupPath="F:\Steam\steamapps\common\FSX\" Checking version of the FSX-SE EXE: ... Version 10.0.62615.0 (Need at least 10.0.62607.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 62615 (Steam) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL ... No previous valid version found. FSX-SE Modules folder already exists. Okay -- installed FSUIPC4 into "F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\User\AppData\Roaming" Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default.migrated\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\DefaultAppPool\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\User\AppData\Roaming" Found FSX_SE.CFG in "C:\Users\User\AppData\Roaming\Microsoft\FSX-SE\FSX_SE.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking for the current user's Application Data path: ... found as "C:\Users\User\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default.migrated\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\DefaultAppPool\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\User\AppData\Roaming" ... No FSX.CFG there Looking for the current user's Application Data path: ... found as "C:\Users\User\AppData\Roaming" Now finding \Microsoft\FSX\FSX_SE.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default.migrated\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\DefaultAppPool\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\User\AppData\Roaming" ... No FSX_SE.CFG there "Modules\FSUIPC Documents" folder created okay! Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "The 2016 List of FSX and P3D Controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay Installed "FSUIPC4_Loader.dll" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC CHECK Checking FSUIPC registration ... Registration check for FSUIPC4 was successful! (result code 00) *************** End of Install Log *************** FSUIPC4.log Quote ********* FSUIPC4, Version 4.969d (5th July 2017) by Pete Dowson ********* Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=582F0000 User Name="Christophe Mercier" User Addr="e-mail address redacted" FSUIPC4 Key is provided WideFS7 Key is provided 16 System time = 30/07/2017 13:02:12 16 FLT UNC path = "\\ASUS-CMS\Users\User\Documents\Flight Simulator X - Steam Edition Files\" 16 ------ Module Version Check ------ 16 acontain.dll: 10.0.62615.0 16 api.dll: 10.0.62615.0 31 controls.dll: 10.0.62615.0 31 fs-traffic.dll: 10.0.62615.0 31 G3D.dll: 10.0.62615.0 31 language.dll: 10.0.62615.0 31 sim1.dll: 10.0.62615.0 31 visualfx.dll: 10.0.62615.0 31 weather.dll: 10.0.62615.0 31 window.dll: 10.0.62615.0 31 ---------------------------------- 62 Trying to connect to SimConnect Steam ... 78 FS UNC path = "F:\Steam\steamapps\common\FSX\" 219 ---------------------- Joystick Device Scan ----------------------- 281 Product= Microsoft Nano Transceiver 1.1 281 Manufacturer= Microsoft 281 Vendor=045E, Product=07FD (Version 3.21) 281 ------------------------------------------------------------------- Event log: Quote Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a Faulting module name: FSUIPC4.dll, version: 4.9.6.904, time stamp: 0x595e1155 Exception code: 0xc0000417 Fault offset: 0x000cd5c0 Faulting process id: 0x2398 Faulting application start time: 0x01d3095deb95340e Faulting application path: F:\Steam\steamapps\common\FSX\fsx.exe Faulting module path: F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.dll Report Id: 5f71a716-8a58-4ae4-a088-c23c525811cd Faulting package full name: Faulting package-relative application ID:
cmercier Posted July 31, 2017 Author Report Posted July 31, 2017 I found another thread where the OP is having the same issue as me where it appears that a Microsoft mouse is being identified as a joystick. (workaround is to disconnect the mouse, launch FS and reconnect). This behavior did not happen with previous versions of FSUIPC (4.947) Thanks Christophe Mercier The extended log file is as follows: Quote ********* FSUIPC4, Version 4.969d (5th July 2017) by Pete Dowson ********* Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=16090000 User Name="Christophe Mercier" User Addr="e-mail address redacted" FSUIPC4 Key is provided WideFS7 Key is provided 15 System time = 31/07/2017 00:20:23 15 FLT UNC path = "\\ASUS-CMS\Users\User\Documents\Flight Simulator X - Steam Edition Files\" 15 ------ Module Version Check ------ 15 acontain.dll: 10.0.62615.0 15 api.dll: 10.0.62615.0 15 controls.dll: 10.0.62615.0 15 fs-traffic.dll: 10.0.62615.0 31 G3D.dll: 10.0.62615.0 31 language.dll: 10.0.62615.0 31 sim1.dll: 10.0.62615.0 31 visualfx.dll: 10.0.62615.0 31 weather.dll: 10.0.62615.0 31 window.dll: 10.0.62615.0 31 ---------------------------------- 62 Trying to connect to SimConnect Steam ... 78 FS UNC path = "F:\Steam\steamapps\common\FSX\" 219 #### Initialising Dlrectinput Axis Scanning ... 219 (Entry from GetRegisteredOptions) 219 ---------------------- Joystick Device Scan ----------------------- 219 Checking: \\?\hid#atk4001#3&2b9532e0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 219 Usage=12, UsagePage=1, =Flight Mode Switch 219 Checking: \\?\hid#vid_045e&pid_07fd&mi_01&col03#7&b2a196e&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 219 Usage=4, UsagePage=65281, =Game Controller 219 Product= Microsoft Nano Transceiver 1.1 219 Manufacturer= Microsoft 219 Vendor=045E, Product=07FD (Version 3.21) 219 ------------------------------------------------------------------- 219 ****** Registry scanning: VID=045E, PID=07FD ****** 219 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_045E&PID_07FD\Calibration\0" 219 ... and a "GUID" value 219 GUID= {1A2DF9B0-A1FC-11E6-8002-444553540000} 219 NB: not valid for this device according to GetConfig!
Pete Dowson Posted July 31, 2017 Report Posted July 31, 2017 3 hours ago, cmercier said: I found another thread where the OP is having the same issue as me where it appears that a Microsoft mouse is being identified as a joystick. Yes, and I was still waiting for the logging I asked for. Also I ALWAYS need the FSUIPC4.Joyscan.csv file, which tells me in compact form exactly what the joystick scanner did. Also please try this version, which is the Release Candidate for 4.70 which I am hoping to release tomorrow. I you could test it soon and show me both the Log (with that extra logging option enabled still, as you have now), AND the joyscan file -- whether it works or not, it would be very useful to me, please. FSUIPC4969g.zip Pete
cmercier Posted July 31, 2017 Author Report Posted July 31, 2017 Hi Pete, Thanks for the quick reply. The issue seems to be solved with the file you provided. I'm attaching both versions of the CSV file, both for v4.969d and for v4.969g. Thank you very much for your support Christophe Mercier FSUIPC4.log Quote ********* FSUIPC4, Version 4.969g (26th July 2017) by Pete Dowson ********* Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=581D0000 User Name="Christophe Mercier" User Addr="email address redacted" FSUIPC4 Key is provided WideFS7 Key is provided 15 System time = 31/07/2017 08:16:33 31 FLT UNC path = "\\ASUS-CMS\Users\User\Documents\Flight Simulator X - Steam Edition Files\" 31 ------ Module Version Check ------ 31 acontain.dll: 10.0.62615.0 31 api.dll: 10.0.62615.0 31 controls.dll: 10.0.62615.0 31 fs-traffic.dll: 10.0.62615.0 46 G3D.dll: 10.0.62615.0 46 language.dll: 10.0.62615.0 46 sim1.dll: 10.0.62615.0 46 visualfx.dll: 10.0.62615.0 46 weather.dll: 10.0.62615.0 46 window.dll: 10.0.62615.0 46 ---------------------------------- 515 Trying to connect to SimConnect Steam ... 531 FS UNC path = "F:\Steam\steamapps\common\FSX\" 687 #### Initialising Dlrectinput Axis Scanning ... 687 (Entry from GetRegisteredOptions) 687 ---------------------- Joystick Device Scan ----------------------- 687 Checking: \\?\hid#atk4001#3&2b9532e0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 687 Usage=12, UsagePage=1, =Flight Mode Switch 687 ------------------------------------------------------------------- 687 ------------------------------------------------------------------- 687 ---------- Making INI JoyNames Section ---------- 687 wJoyIDsUsed=0000 687 ------------------------------------------------- 687 Checking and assigning Joy Letters as needed 703 #### Completed Dlrectinput Axis Scanning 718 LogOptions=00000000 02000011 718 ------------------------------------------------------------------- 718 ------ Setting the hooks and direct calls into the simulator ------ 718 --- CONTROLS timer memory location obtained ok 718 --- SIM1 Frictions access gained 718 --- FS Controls Table located ok 718 --- Installed Mouse Macro hooks ok. 718 --- Wind smoothing fix is fully installed 718 --- SimConnect intercept for texts and menus option is off 718 --- All links checked okay 718 ------------------------------------------------------------------- 718 SimConnect_Open succeeded: waiting to check version okay 718 Trying to use SimConnect Steam 718 Opened separate AI Traffic client okay 2546 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 2546 Initialising SimConnect data requests now 2546 FSUIPC Menu entry added 2546 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 2546 \\ASUS-CMS\Users\User\Documents\Flight Simulator X - Steam Edition Files\MMMX.FLT 2546 F:\Steam\steamapps\common\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.air 2546 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=N 2578 Memory in use: 566Mb, Avail=3530Mb, MaxFreeBlock=2036Mb 62640 Memory in use: 610Mb, Avail=3485Mb, MaxFreeBlock=2036Mb 82843 ***** This device has been removed: 82843 Device at "\\?\HID#VID_045E&PID_07FD&MI_00#7&2f015730&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 82843 ***** This device has been removed: 82843 Device at "\\?\HID#VID_045E&PID_07FD&MI_01&Col01#7&b2a196e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 82843 ***** This device has been removed: 82843 Device at "\\?\HID#VID_045E&PID_07FD&MI_01&Col02#7&b2a196e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" 82843 ***** This device has been removed: 82843 Device at "\\?\HID#VID_045E&PID_07FD&MI_01&Col03#7&b2a196e&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" 82843 ***** This device has been removed: 82843 Device at "\\?\HID#VID_045E&PID_07FD&MI_02#7&18ad2454&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 86593 ***** A device has been attached! 86593 ***** HID USB device reconnected: re-initialising FSUIPC connections 86593 #### Initialising Dlrectinput Axis Scanning ... 86593 (Entry from CheckDeviceChange) 86593 ---------------------- Joystick Device Scan ----------------------- 86593 Checking: \\?\hid#atk4001#3&2b9532e0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 86593 Usage=12, UsagePage=1, =Flight Mode Switch 86593 ------------------------------------------------------------------- 86593 ------------------------------------------------------------------- 86609 ---------- Making INI JoyNames Section ---------- 86609 wJoyIDsUsed=0000 86609 ------------------------------------------------- 86609 Checking and assigning Joy Letters as needed 86609 #### Completed Dlrectinput Axis Scanning 86609 ***** A device has been attached! 86609 ***** A device has been attached! 86609 ***** A device has been attached! 86609 ***** A device has been attached! 122687 Memory in use: 613Mb, Avail=3483Mb, MaxFreeBlock=2036Mb 182750 Memory in use: 614Mb, Avail=3482Mb, MaxFreeBlock=2036Mb FSUIPC4.JoyScan_v4.969d.csv FSUIPC4.JoyScan_v4.969g.csv
cmercier Posted July 31, 2017 Author Report Posted July 31, 2017 I've also edited the title to accurately reflect the root cause (the MS mouse) and help other users that may face the same issue
Pete Dowson Posted July 31, 2017 Report Posted July 31, 2017 4 minutes ago, cmercier said: The issue seems to be solved with the file you provided. Great news! Thank you. This is wehat I needed to know before releasing 4.969g as 4.97 tomorrow. 6 minutes ago, cmercier said: I'm attaching both versions of the CSV file, both for v4.969d and for v4.969g. Thank you. I will check those so that I can confirm that the intended action has indeed been carried out correctly. 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