Thomas Richter

Hi, as the log shows you have an SimConnect stall, that starts with the start of vPilot. Just try a session without vPilot. 164160 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 164222 ASN active function link set 164222 Ready for ASN WX radar 165361 Weather Read request (Nr Station) to area 5: Lat=51.48, Lon=-0.43, Alt=0.0, Req=1 167046 Deactivated for PID=19132, "vPilot.exe" 167046 Lost focus to PID=19132, "vPilot.exe" 167498 Weather Read request (Global set) to area 1: ICAO="GLOB", Req=0 169854 WX Error: timed out, WX request type 5, Lat=51.4759, Lon=-0.4342, Alt=0.0m Thomas

Hi, the code base for that will not have changed in FSUIPC5 compared to FSUIPC4. Did you try the MyTraffic forum first to make sure there is no change in P3Dv4 with MyTraffic because of AI change in P3Dv4? Thomas

Hi, the log shows Registration dialog exit: selected FSUIPC CHECK That means you selected the Check Registration option but if there is no Registration key file in the folder from previous registration you will get an error (16). You need to select Enter New Registration instead and the copy and paste your details, don't try typing what leads to error. Thomas

Hi, no there is no other place than SimMarket. But I did myself purchases at SimMarket with Debit-Card without problem, as I always do in other places also (Visa Debit, always accepted). Thomas

Hi, do you maybe check offset 0x3308 for FS version, P3Dv4 is value 12 ? Thomas

Hi, the FSUIPC4.log file is missing. Also change the setting to 'Yes' in AutoAssignLetters=No to AutoAssignLetters=Yes Then run the sim for a short session, after FS has fully closed please copy and paste the full content of the FSUIPC4.ini and FSUIPC4.log file to your message. Thomas

Hi, there have been bugfixes from PMDG because of their use of an FSUIPC 32-bit library in their 64-bit code. Search for invisible gear and so with FSUIPC5 activated in their forum. Others reported that fixed the problem. Thomas

Hi, it is possible they haven't been activated yet because of the PMDG error where they needed to fix the use of an old FSUIPC 32-bit library. Thomas

Hi, nothing attached. Just copy and paste the full content of the log file after closing the session to your message. Something must have changed because the same problem doesn't exist in your FSX, so something has changed in P3D as it worked with the same FSUIPC version before. Thomas

Hi, as the log shows the first SimConnect stall happens already after 15.25 minutes (915 seconds). In case you use PMDG777 check that you installed their latest updates as they had an error where they used an very old 32-Bit version lib of FSUIPC they now removed. Also please try with a default aircraft instead with an add-on to eliminate those errors. Thomas

Hi, this is the wrong forum for that. FSUIPCClient.dll is by Paul Henty and his latest version FSUIPCClient RC2 works for .Net2/ .Net4 and also for 32-Bit and 64-Bit FSUIPCClient3.0_RC2 Question about FSUIPCClient and .Net applications are best placed in the Sub-Forum, FSUIPC Client DLL for .NET Thomas

Hi, first, as always, the FSUIPC4.log file is needed to have some information. In case Vpilot doesn't work anymore it indicates an error with simConnect because Vpilot does use SimConnect but not FSUIPC. Also in case FSX-SE on the same PC with the sane FSUIPC4 version works ok and the problem happend suddenly means that there was a change in P3D that causes this new problem and not FSUIPC itself. What did change in P3D before you switched down/ or before you used it last time before the error? Thomas

Hi, Thomas, if you were referring to my post, you may have misunderstood my question; I do realize it's a new product. What I meant was that I purchased FSUIPC4 two weeks ago, but didn't need it, I needed FSUIPC5 instead. And if I should handle here or with SimMarket. yes, has to be done with SimMarket as you successfully did already. I just bought fsuipc4/widefs from simMarket 5/28/17, so I haven't been using it since 2006. I'm a P3D user, I was planning on P3Dv4 this weekend or next. I referred to your post but I thought the first given date might have been wrong ... because you said you didn't use it since 2006 and you were already a P3D user and wanted to switch to P3Dv4. But anyway well sorted! Thomas

Hi, please copy and paste the full content of your FSUIPC4.log and FSUIPC4.ini file to your message and attach the FSUIPC4.JoyScan.csv. That will give much more info. Thomas

Hi, FSUIPC5 is a new product developed for new Prepar3Dv4 64-Bit, it is not an upgrade version and so it is independent of any earlier version like FSUIPC4. You will have to buy a registration key for FSUIPC5. Please note if you bought already a licence key for WideFS7 (FSUIPC4) you don't need to buy it again, you can use it with a registered version of FSUIPC5. Thomas

Hi, this error will show in a message box if you didn't read the attached MakeRwys README.pdf file. It will tell you that you have to run the MakeRwys.exe inside the FS folder, depending which FS you use (FSX/ FSX-SE/ P3D). Thomas

Hi Herve, the FSUIPC5 History.pdf file is installed with latest FSUIPC5.102 installer, of course as you already noticed after installing FSUIPC5. Check your email in case you still don't have the file ... Thomas

Hi, easiest way is always to tick the box 'Disable Controller' in FS/P3D. Thomas

Hi, FSUIPC5 is as FSUIPC4 and FSUPC3 was, a independent product for different FS platforms. FSUIPC3 for FS9 and older, FSUIPC4 for FSX/ FSX-SE/ P3Dv1-v3 and FSUIPC5 for P3Dv4. Each version had been from the ground up developed. So for each version you want to use you will have to buy a registration key. Note that one WideFS licence key would work for both, FSUIPC4 and as well for FSUIPC5. Thomas

Hi, Server: ID=192.168.1.1 Subnet: 255.255.255.0 Client: ID=192.168.1.6 Subnet: 255.255.255.0 The readings I hope mean something to you, as for me I am lost ! That looks good as it shows you are in the same network with both PC's, and if the WorkGroup for both PC's is still the same (as you checked before) then that should be OK. Make sure both PC's can see each other and you have full read and write control from one PC to the other, Network File Sharing is ON and there is no password needed. In WideClient.ini file (on your Client-PC) you use already ServerName=owner-pc what is correct, but check that the PC name is spelled correct! You can also try ServerIp=192.168.1.1 instead of ServerName= , one or the other should work as long the value (name or Id is correct). Thomas

Hi, 1/ when assigning the functions in FSUIPC it is best to assign everything in FSUIPC instead of having it mixed, some in FSUIPC and others in FS/P3D. So you should disable Controllers in FS/P3D (in P3D in controls menu bottom) 2/ Best is to change this in FSUIPC5.ini file to Yes AutoAssignLetters=No change to AutoAssignLetters=Yes This will assign letters to each controller. Your assignments will then be related to the letter instead of the number. When it then happens that identical controller changed their number because of i.e. a USB port swap by mistake, then you can easily swap the assigned letter of the controller and the defined functions stays with the 'letter' When Controllers are disabled in FS/P3D then any change of controller doesn't has any effect in FS/P3D. Thomas

Hi, just in addition I can confirm that there is NO problem with Extreme 3D Pro, neither with FSUIPC4.968 nor with FSUIPC5.101m, as I have x2 devices here. Thomas

Hi, all FSUIPC stuff included the module (DLL) itself is located in ..\Prepar3D v4\Modules\ So just find your FS (P3Dv4) installation folder and check in subfolder Modules Thomas

Hi, please copy and paste the full content of the FSUIPC5.log file after the session has been closed, ideally of course a session when the 'crash' happend. Thomas

Hi, still as it says Error=10013 --> Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). Did you check you have the Network address and subnet mask correct set manually and not automatic on both PC's, i.e. (only an example): Server: ID=192.168.1.10 Subnet: 255.255.255.0 Client: ID=192.168.1.11 Subnet: 255.255.255.0 Thomas