von Posted April 25, 2016 Report Share Posted April 25, 2016 FSUIPC 4949P gives Simconnect error for P3Dv3-1 Working ok in FSX Acceleration Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 25, 2016 Report Share Posted April 25, 2016 FSUIPC 4949P gives Simconnect error for P3Dv3-1 Working ok in FSX Acceleration SimConnectP3D3, which was developed for P3D3.2, is only a "stub" as far as I am concerned, but it does embody the library from the SDK related to P3D version 3.2. It must be that Lockheed Martin have made that library incompatible with 3.1. That's a bit worrying. Since you also have FSX installed all you need to do is remove the SimConnectP3D3.DLL from the P3D Modules folder. FSUIPC will use the FSX SimConnect quite happily. Any reason you aren't updating to 3.2? It is said to be much better. I'll see if I can find a version 3.0 of the SimConnect.lib file and re-compile my interface DLL with that. Do you think you could test it for me when I have? I cannot install 3.0 or 3.1 now. Pete Link to comment Share on other sites More sharing options...
von Posted April 25, 2016 Author Report Share Posted April 25, 2016 Pete, Thanks for the quick follow up. "Since you also have FSX installed all you need to do is remove the SimConnectP3D3.DLL from the P3D Modules folder. FSUIPC will use the FSX SimConnect quite happily." Will do . "Any reason you aren't updating to 3.2? It is said to be much better." When all my addons are said to be ok with it I will uninstall all my aircraft and scenery from P3Dv3.1 .... a big job ... and the do a full Install of P3Dv3.2 .. or 3.3 if I wait long enough and all my addons and scenery .. another big job at least for me. Edit: "I'll see if I can find a version 3.0 of the SimConnect.lib file and re-compile my interface DLL with that. Do you think you could test it for me when I have? I cannot install 3.0 or 3.1 now." I just seen this comment .. thanks. Yes I could do the test now. I will stand by. Link to comment Share on other sites More sharing options...
von Posted April 25, 2016 Author Report Share Posted April 25, 2016 I just went to my P3Dv3.1 Modules folder and noticed there are two DLL files in there?? Edit: yes, I could do a test for you .... Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 25, 2016 Report Share Posted April 25, 2016 Yes I could do the test now. I will stand by. Okay. Thanks. Found a 3.0 version SDK (thank goodness I do regular backups) and rebuilt my DLL with that. It should be forward compatible with 3.1 as well as 3.2 (just tested okay with 3.2). Please download SimConnectP3D30.zip, and place the enclosed DLL into the Modules folder. When you run P3D I need to know only that it says this in the FSUIPC4.LOG file (near the beginning): Trying E:\Prepar3D v3\Modules\SimConnectP3D3.dll Found it: trying to connect and this, a little later: SimConnect_Open succeeded: waiting to check version okay Trying to use SimConnect Prepar3D Then we'll know it is working ok. Incidentally, the version number information (right-click properties) I include in the DLL is the version number of the SDK used to build it. Thanks, Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 25, 2016 Report Share Posted April 25, 2016 I just went to my P3Dv3.1 Modules folder and noticed there are two DLL files in there?? The SimConnectP3D2.DLL should have been deleted by the FSUIPC4 Installer. It does get deleted here. It won't be used unless you are using P3D version 2.x. Pete Link to comment Share on other sites More sharing options...
von Posted April 25, 2016 Author Report Share Posted April 25, 2016 "he SimConnectP3D2.DLL should have been deleted by the FSUIPC4 Installer." I would not know .. never pay attention to what is in there ... I moved both DLL's out of the P3Dv3.1 Modules folder and put them on my desktop for safe keeping. P3Dv3.1 started ok. What should I do next? Link to comment Share on other sites More sharing options...
von Posted April 25, 2016 Author Report Share Posted April 25, 2016 I will download your file and test it now. Link to comment Share on other sites More sharing options...
von Posted April 25, 2016 Author Report Share Posted April 25, 2016 Before doing the test do I need to put the DLL back into my Modules folder? Just looked at the ZIP .. It will be the only dll in the modules folder for the test. Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 25, 2016 Report Share Posted April 25, 2016 Before doing the test do I need to put the DLL back into my Modules folder? Er, not the original, obviously (that one crashes, as you showed me), but the replacement DLL in the ZIP I gave you a link to! If the DLL isn't there you aren't testing anything, are you? Pete Link to comment Share on other sites More sharing options...
von Posted April 25, 2016 Author Report Share Posted April 25, 2016 I only used the DLL from your zip in my modules folder ... P3Dv3.1 started OK now. 15 Trying F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 15 Found it: trying to connect 31 FS path = "F:\Lockheed Martin\Prepar3D v3\" 125 ---------------------- Joystick Device Scan ----------------------- 125 Product= CH PRO PEDALS USB 125 Manufacturer= CH PRODUCTS 125 Vendor=068E, Product=00F2 (Version 0.0) 125 Serial Number= 140 Product= Saitek X52 Flight Control System 140 Manufacturer= Saitek 140 Vendor=06A3, Product=075C (Version 1.16) 140 Serial Number= 140 Product= Saitek Pro Flight Yoke 140 Manufacturer= Saitek 140 Vendor=06A3, Product=0BAC (Version 3.3) 140 Serial Number= 140 Product= Saitek Pro Flight Quadrant 140 Manufacturer= Saitek 140 Vendor=06A3, Product=0C2D (Version 2.0) 140 Serial Number= 140 ------------------------------------------------------------------- 156 LogOptions=00000000 00000001 156 ------------------------------------------------------------------- 156 ------ Setting the hooks and direct calls into the simulator ------ 156 --- CONTROLS timer memory location obtained ok 156 --- SIM1 Frictions access gained 156 --- FS Controls Table located ok 156 --- Installed Mouse Macro hooks ok. 156 --- Wind smoothing fix is installed 156 --- All links okay (except older global weather setting method) 156 ------------------------------------------------------------------- 156 SimConnect_Open succeeded: waiting to check version okay 156 Trying to use SimConnect Prepar3D 32713 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0) 32713 Initialising SimConnect data requests now 32713 FSUIPC Menu entry added 32713 C:\Users\Vaughan\Documents\Prepar3D v3 Files\MooneyBravo-P3D-default-startup-flight.fxml 32713 F:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.air 76362 System time = 25/04/2016 13:43:18, Simulator time = 13:42:34 (17:42Z) 76378 Aircraft="Mooney Bravo" 77392 Starting everything now ... 77392 Run: "C:\Program Files (x86)\EZCA\EZCA.exe" 77439 ASN active function link set 77439 Ready for ASN WX radar 141415 === NOTE: not calling SimConnect_Close ... 142413 System time = 25/04/2016 13:44:24, Simulator time = 13:42:38 (17:42Z) 142413 *** FSUIPC log file being closed Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 25, 2016 Report Share Posted April 25, 2016 I only used the DLL from your zip in my modules folder ... P3Dv3.1 started OK now. 15 Trying F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 15 Found it: trying to connect ... 156 SimConnect_Open succeeded: waiting to check version okay 156 Trying to use SimConnect Prepar3D Okay. Good. Thanks. Those lines above are the ones which confirm it is using the revised DLL okay. It will be included in the next Installer Update. I'm just waiting for some feedback on the new PMDG 737NGX CDU offsets I've added. Thanks again Pete Link to comment Share on other sites More sharing options...
von Posted April 25, 2016 Author Report Share Posted April 25, 2016 "It will be included in the next Installer Update. I'm just waiting for some feedback on the new PMDG 737NGX CDU offsets I've added." Right, I seen you were testing in another post version Q .. Thanks for the fix. Have a good day. 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