helmut mackenroth Posted January 9, 2019 Report Share Posted January 9, 2019 after installing Client and content p3dv4.4 and then 5.15FSUIPC I've got the message in the p3dv4.4 Windows I see 5.15 is installed as registered user What have I done wrong? kindly regards helmut Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 9, 2019 Report Share Posted January 9, 2019 You posted in the FAQ subforum! Please always post support questions to the SUPPORT forum -- i.e. here. I've moved it for you. 12 minutes ago, helmut mackenroth said: in the p3dv4.4 Windows I see 5.15 is installed as registered user Something is wrong with your P3D installation! The message only appears with versions of FSUIPC later than 5.1 if it detects too early a version of P3D. FSUIPC uses facilities only added since P3D4.1. Please look in the P3D Modules folder for the FSUIPC5.LOG file. It will show what version it detects. Paste it here if you cannot figure it out. Also check the version number stated by P3D in its menu. Pete Link to comment Share on other sites More sharing options...
helmut mackenroth Posted January 9, 2019 Author Report Share Posted January 9, 2019 thank you for your answer, here is the row from the log file: 75141 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.4.16.27077 (SimConnect: 4.4.0.0) - the same is in p3dv4.4 - there is the correct 5.15 FSUIPC and 4.4.16.27077 there are some other users in facebookgroup p3d with the same problem Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 9, 2019 Report Share Posted January 9, 2019 10 minutes ago, helmut mackenroth said: 75141 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.4.16.27077 (SimConnect: 4.4.0.0) - the same is in p3dv4.4 - there is the correct 5.15 FSUIPC and 4.4.16.27077 Well, one of the modules in your 4.4 installation is corrupt. The message you showed refers to the list of FS controls FSUIPC obtains automatically. Try re-installing the P3D client (only). that doesn't take log (uoi need to uninstall first via the Windows "Programs" app -- you can do this and retain your registration). If you still need to come back here, please paste the entire LOG file after closing P3D. You can use the <> button above the edit area in order to enclose it tidily. 12 minutes ago, helmut mackenroth said: there are some other users in facebookgroup p3d with the same problem Why aren't they posting here, then? This aspect of FSUIPC hasn't changed since P3D4.1 times and the versions of FSUIPC since then. Before that FSUIPC provided a fixed list of FS controls which didn't change with P3D additions. Pete Link to comment Share on other sites More sharing options...
helmut mackenroth Posted January 9, 2019 Author Report Share Posted January 9, 2019 Pete, I looked in the old folder from last year and there is in the logfile : Windows 10 Pro 64 Bit reported as Build 16299, Release ID: 1709 and then in the next row Prepar3D.exe version = 4.2.21.24048 (with FSUIPC 5.123c) Reading options from "D:\Modules\FSUIPC5.ini" now in the actual logfile is Windows 10 Pro 64 Bit reported as Build 16299, Release ID: 1809 und in the next row is no version of Prepare3D.exe rather Reading options from "D:\Modules\FSUIPC5.ini" I think my problem exists since updating W10 to 1809. it would be coincidence that I have done the W10 update and then p3D update to 4.4 Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 9, 2019 Report Share Posted January 9, 2019 10 minutes ago, helmut mackenroth said: I think my problem exists since updating W10 to 1809. it would be coincidence that I have done the W10 update and then p3D update to 4.4 Well, many users are certainly using Win10 1809 without such a problem. Could you paste the entire (new) log please? Did you try the Client re-install as suggested? Pete Link to comment Share on other sites More sharing options...
helmut mackenroth Posted January 9, 2019 Author Report Share Posted January 9, 2019 yes, I have reinstalled the client but there are no changes here is the new log: ********* FSUIPC5, Version 5.15 (27th November 2018) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FFA622A0000Windows 10 Pro 64 Bit reported as Build 17763, Release ID: 1809 (OS 10.0) Reading options from "D:\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="helmut mackenroth" User Addr="nordhesse52@live.de" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 0 System time = 09/01/2019 16:14:47 0 FLT path = "C:\Users\nordh\Documents\Prepar3D v4 Files\" 71141 Using DialogMode 71157 FS path = "D:\" 71219 ---------------------- Joystick Device Scan ----------------------- 71219 Product= T-Rudder 71219 Manufacturer= Thrustmaster 71219 Vendor=044F, Product=B679 (Version 1.16) 71235 GUIDs returned for product: VID_044F&PID_B679: 71235 GUID= {AD9304A0-F88D-11E7-8001-444553540000} 71235 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z1023 71235 Product= T.16000M 71235 Manufacturer= Thrustmaster 71235 Vendor=044F, Product=B10A (Version 5.0) 71235 GUIDs returned for product: VID_044F&PID_B10A: 71235 GUID= {07B27090-34E5-11E8-8001-444553540000} 71235 Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255 71235 Product= TWCS Throttle 71235 Manufacturer= Thrustmaster 71235 Vendor=044F, Product=B687 (Version 1.16) 71235 GUIDs returned for product: VID_044F&PID_B687: 71235 GUID= {2895FA20-4165-11E8-8001-444553540000} 71235 Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z65535 71235 ------------------------------------------------------------------- 71250 Device acquired for use: 71250 Joystick ID = 1 (Registry okay) 71250 1=T-Rudder 71250 1.GUID={AD9304A0-F88D-11E7-8001-444553540000} 71250 Device acquired for use: 71250 Joystick ID = 0 (Registry okay) 71250 0=T.16000M 71250 0.GUID={07B27090-34E5-11E8-8001-444553540000} 71250 Device acquired for use: 71250 Joystick ID = 2 (Registry okay) 71250 2=TWCS Throttle 71250 2.GUID={2895FA20-4165-11E8-8001-444553540000} 71250 ------------------------------------------------------------------- 71250 LogOptions=00000000 00000001 71250 ------------------------------------------------------------------- 71250 SimConnect_Open succeeded: waiting to check version okay 71250 Opened separate AI Traffic client okay 71250 ### PDKmodeHelper callback registered! 75141 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.4.16.27077 (SimConnect: 4.4.0.0) 75141 Initialising SimConnect data requests now 75141 FSUIPC Menu entry added 75157 ... Using Prepar3D with Academic License Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 9, 2019 Report Share Posted January 9, 2019 35 minutes ago, helmut mackenroth said: ********* FSUIPC5, Version 5.15 (27th November 2018) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FFA622A0000Windows 10 Pro 64 Bit reported as Build 17763, Release ID: 1809 (OS 10.0) Reading options from "D:\Modules\FSUIPC5.ini" Checking the Registrations now .. Very strange. This implies that the standard Windows function "GetFileVersionInfo" failed, or at least returned wrong information. It examines the version information in Prepar3D.exe in your main P3D folder. Perhaps you could find that, right-click on it, select Properties and ensure that it too shows 4.4.16.27077. That P3D version shown later (time 75141) is supplied by SimConnect after connecting, too late though for correct FSUIPC initialisation. Can you also try running P3D by right-clicking on it and selecting "run as ... administrator". This gives it extra privileges. Maybe Windows is preventing the version info being read!? (Which would be very bad). One other check you could do, please. In FSUIPC's Options, go to Logging. In the Monitor facility, right hand side, enter 3124 for the Offset and U8 for the Type. Then check Normal log below, and see what FSUIPC logs for the value in 3124. Failing help provided by these actions, I will probably have to provide a test version of FSUIPC with extra logging around the code concerned. Pete Link to comment Share on other sites More sharing options...
helmut mackenroth Posted January 9, 2019 Author Report Share Posted January 9, 2019 1. right click on prepar3d.exe shows correct version 4.416.27077 2. starting as admin no change 3. logging with 3124 ********* FSUIPC5, Version 5.15 (27th November 2018) by Pete Dowson ********* User Name="helmut mackenroth" User Addr="nordhesse52@live.de" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 120328 System time = 09/01/2019 18:38:10, Simulator time = 15:06:12 (13:06Z) 120328 FLT path = "C:\Users\nordh\Documents\Prepar3D v4 Files\" [Continuation log requested by user] Running inside Prepar3D v4 on Windows 10 Module base=7FFA62050000 120781 Advanced Weather Interface Enabled 250969 Sim stopped: average frame rate for last 130 secs = 52.0 fps 250969 Max AI traffic was 0 aircraft 332125 Monitor IPC:3124 (S8) = 0 332141 LogOptions changed, now 20000000 00000001 332281 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 2016 (0x000007e0) <66507> 332297 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2017 (0x000007e1) <66508> 332297 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2022 (0x000007e6) <66508> 332297 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2023 (0x000007e7) <66508> 332297 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2019 (0x000007e3) <66508> 332297 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2020 (0x000007e4) <66508> 332297 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2024 (0x000007e8) <66508> 332297 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2025 (0x000007e9) <66508> 332297 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 2018 (0x000007e2) <66507> 332297 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2021 (0x000007e5) <66508> 332297 *** EVENT: Cntrl= 66834 (0x00010512), Param= 0 (0x00000000) <66834> 332297 *** EVENT: Cntrl= 66828 (0x0001050c), Param= 0 (0x00000000) <66828> 332328 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 2016 (0x000007e0) <66507> 332328 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2017 (0x000007e1) <66508> 332328 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2022 (0x000007e6) <66508> 332328 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2023 (0x000007e7) <66508> 332328 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2019 (0x000007e3) <66508> 332328 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2020 (0x000007e4) <66508> 332328 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2024 (0x000007e8) <66508> 332328 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2025 (0x000007e9) <66508> 332328 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 2018 (0x000007e2) <66507> 332328 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2021 (0x000007e5) <66508> 332328 *** EVENT: Cntrl= 66834 (0x00010512), Param= 0 (0x00000000) <66834> 332328 *** EVENT: Cntrl= 66828 (0x0001050c), Param= 0 (0x00000000) <66828> 332391 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 0 (0x00000000) <65708> 332391 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 0 (0x00000000) <65716> 332391 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 4192 (0x00001060) <65709> 332391 *** EVENT: Cntrl= 65717 (0x000100b5), Param= 0 (0x00000000) <65717> 332391 *** EVENT: Cntrl= 66479 (0x000103af), Param= 17301504 (0x01080000) adf complete set 332406 *** EVENT: Cntrl= 66556 (0x000103fc), Param= 17301504 (0x01080000) <66556> Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 9, 2019 Report Share Posted January 9, 2019 6 hours ago, helmut mackenroth said: 332125 Monitor IPC:3124 (S8) = 0 There's the problem. the version information is not being supplied by Windows! 6 hours ago, helmut mackenroth said: 1. right click on prepar3d.exe shows correct version 4.416.27077 I assume that was a typo for 4.4.16.27077? I'm afraid this will need further investigation with added logging. i'll see if that can be dealt with tomorrow and let you know. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 10, 2019 Report Share Posted January 10, 2019 11 hours ago, Pete Dowson said: I'm afraid this will need further investigation with added logging. i'll see if that can be dealt with tomorrow and let you know. Okay. I've added logging to the part where FSUIPC requests the File Version information. Please download FSUIPC5150c.zip and run that, then show me the Log. (The ZIP only contains the DLL to place into yout P3D Modules folder). Pete Link to comment Share on other sites More sharing options...
helmut mackenroth Posted January 10, 2019 Author Report Share Posted January 10, 2019 Thank you for your support Pete, I've done that now and here is the log ********* FSUIPC5, Version 5.150c (10th January 2019) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FF8E7290000 Windows 10 Pro 64 Bit reported as Build 17763, Release ID: 1809 (OS 10.0) GetFileAttributes failed error 3 [0X00000003] on path "\Device\HarddiskVolume4\Prepar3D.exe" Reading options from "D:\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="helmut mackenroth" User Addr="nordhesse52@live.de" FSUIPC5 Key is provided Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 10, 2019 Report Share Posted January 10, 2019 6 hours ago, helmut mackenroth said: GetFileAttributes failed error 3 [0X00000003] on path "\Device\HarddiskVolume4\Prepar3D.exe" There's the problem, though I've no idea what is causing it. A function asking Windows to tell FSUIPC where its containing Process is (that's Prepar3D.EXE of course) is saying it is in "\Device\HarddiskVolume4\Prepar3D.exe". That isn't a valid path in any case, hence the error 3 which is "path not found". If "Device" was the name of your PC, there should be \\ in front of it, not a single \. And having a shared path called "HarddiskVolume4" seems very odd. I note from earlier that your P3D is installed in the ROOT directory of drive D, not in any folder at all. That is very odd. Is there a reason for that? And do you have a PC called "Device" and a shared folder called "HarddiskVolume4"? Perhaps some description of exactly how you have configured your system would be useful, please, because we are really at a loss. It is as if standard Windows functions calls are returning unusable nonsense! [LATER] I've made another build which may or may not throw more light onto this mystery. Please try FSUIPC5150d.zip Pete Link to comment Share on other sites More sharing options...
helmut mackenroth Posted January 11, 2019 Author Report Share Posted January 11, 2019 On 1/9/2019 at 6:46 PM, helmut mackenroth said: prepar3d.exe is (very stupid) in root from D:\ but since beginning with p3d it is there and all was working well. There is no "HarddiskVolume4" and no"DEVICE" now I started with the 5150d and there are no errors p3d starts normaly 🙂 ********* FSUIPC5, Version 5.150d (10th January 2019) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FF8D41F0000 Windows 10 Pro 64 Bit reported as Build 17763, Release ID: 1809 (OS 10.0) Prepar3D.exe version = 4.4.16.27077 Reading options from "D:\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="helmut mackenroth" User Addr="nordhesse52@live.de" FSUIPC5 Key is provided Thank you so far and best regards Helmut On 1/9/2019 at 6:46 PM, helmut mackenroth said: Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 11, 2019 Report Share Posted January 11, 2019 3 hours ago, helmut mackenroth said: now I started with the 5150d and there are no errors p3d starts normaly 🙂 Good. I merely changed to a simpler version of a Windows function call to get the P3D EXE path. I think Win10 1809 has a bug, though seemingly only affecting root folder installations (which are rare) as there are really no other reports (at least here, where they should be). Pete Link to comment Share on other sites More sharing options...
helmut mackenroth Posted January 11, 2019 Author Report Share Posted January 11, 2019 I would not make this mistake again with the root installation - but thank you very much for the great support from you helmut Link to comment Share on other sites More sharing options...
FireRx Posted January 12, 2019 Report Share Posted January 12, 2019 Thank you Pete. I had the same issue and couldn't figure it out. 😁 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