Thomas Richter

That sounds like a virus checker is involved! Thomas

Hi, The first bit of the Install log file is missing? Thomas

Hi, when you use the sequence FSUIPC closed -> change INI -> save INI -> open FSUIPC -> reload settings. Everything changes here to the new settings, I used your settings for that. Thomas

Of course, that's the only interface. No direct code hacks into FSX/ P3D are used for that function. You can call that function as well direct in FSX/ P3D with a Button or Key press when assigned. Thomas

Hi, first of all that should go to IvAp support because it is clearly a problem of that add-on. The can be caused by two possibilities, depending on what connection IvAp is using to connect to P3Dv4: 1/ If it uses SimConnect direct then FSUIPC is not involved at all 2/ if it uses FSUIPC is IvAp compatible with FSUIPC5, some add-ons use the FSUIPC version check and don't know the value 12 vor FSUIPC5 (only up to value 10 for P3Dv3) So you would need to check with them what the problem is. Here might be a IvAp user that knows something but this Forum is the wrong place really. Thomas

Hi, FSUIPC 'ask' FSX/ P3D to save the situation but it doesn't have any control over the process other than telling a name to be used. AutoSave option shouldn't be used at all for PMDG and some other add-on AC's where FSX/ P3D has to save a big amount of data. Thomas

Hi, the log file shows the PanView buttons are definitely working correct. In case nothing is assigned in FSUIPC to it, it doesn't do anything. Check as well the Manual for button assigning. Thomas

Hi, as I said in ProgramData they shouldn't have those entries. They did already exist in P3Dv3, nothing new to v4. Those are mine from ProgramData\...: dll.xml exe.xml Also maybe you have an error in the dll.xml file, in its structure, and it is not loaded anymore. Check the correct structure. Thomas

But did you check your Offsets as I said? I.e. byte 4-7 is the control but have assigned private Offset<int> id = new Offset<int>(0x2904); what is byte 0-3 ... Thomas

Hi, did you use the same privileges for the installer as you did for the P3D installation, i.e. both as administrator (right click on file ...)? The dll.xml in ProgramData shouldn't have those entries at all ! Thomas

Hi, check your Offsets against Bytes 0–3: Aircraft Id (from the TCAS table) Bytes 4–7: The FS Control (see published lists) Bytes 8–11: A parameter for the control, if needed Thomas

Hi, if it worked at the time without FSUIPC and it doesn't any more, then it sounds as I said like a hardware problem. The files are in the folder, you have in folder settings Hide Full Name of known files (or Hide extensions of known file types ...) active. You need to change that in (your picture) File->Folder and Search options Start P3D and go to Add-ons, open FSUIPC -> click Logging. There select on the left 'Button and key operations'. Now Click 'Button and Switches' tab and operate the pan-view switch, then click OK to close FSUIPC. Close P3D, wait a moment and copy the files. The files in the folder are FSUIPC4 (Configuration settings) and FSUIPC4 (Text document). Thomas

Hi, what you show looks exactly like it was before the hotfix. What parts did you update of P3D? Please run a short session and close P3D, when fully closed please copy and paste the full content of the log file to your message or send the log file, but complete please. As long to don't want to use any facility of FSUIPC you don't need a registered version. Thomas

Hi, I think you are looking for AP Heading, 07CC 2 Autopilot heading value, as degrees*65536/360 Course, 0C4E 2 NAV1 OBS setting (degrees, 0–359) Thomas

Hi, can you show the FSUIPC4.ini file and which values you need to modify manually, please. Thomas

Hi, FSUIPC4.ini file and FSUIPC4.log file are located in your FlightSim main folder, a subfolder there \Modules\ Best would be to send both files. In case I have two of those Logitech Extreme 3D Pro joysticks here I can confirm they work correct with FSX-SE/ P3Dv3 and P3Dv4. Thomas

Hi, the problem in P3Dv4 was that with FSUIPC5 neither the COM-swap-freq nor the NAV-swap-freq button worked on the Carenado Bonanza GNS430's. Pete did a internal workaround until the Hotfix1 was released and the problem was solved. Just checked to confirm that with FSUIPC5.103e and P3Dv4.0.28.21686 both is still working correct. Also the logging shows the correct events Can you describe more precise your problem. Thomas

Hi, I do get that but did you try yourself. Attached the print Ground Traffic_EGLL.pdf Ground Traffic_EGLL.pdf

Hi, did you check the TrafficLook from Useful additional programs? Being in EGLL it gives me the information for AI on ground in a range of 39nm. It uses of course FSUIPC, I checked here with P3Dv3. That you get only a range of 6nm must be related to the way you read the info. Thomas

Hi, if the Pan button doesn't already in FSX/ P3D work then the first step is checking in Windows Gamecontroller Settings that the Joystick works correct at all. If there is a hardware problem then FSUIPC cannot read this function either. If the hardware is working correct, all axes, buttons and pan-view button, then attach your FSUIPC INI file to see what definitions you have done for the PanView button. Thomas

Hi, the FSUIPC installer you use can of course not find the correct P3D version because you use an installer form March 2016 please download the latest Install_FSUIPC4969.zip , unzip, install and run a P3D session. Then download latest interim version FSUIPC4969d.zip and unzip and overwrite in P3D's ..\modules\ folder the FSUIPC4.dll file. Important: After FSUIPC4 installation P3D needs to run first before any further FSUIPC update! Thomas

Hi, that's for sure some security setting/ behaviour of Windows itself or the Virus program even if it is switched off for live checking. Thomas

But did you check the manual? Thomas

Hi, you cannot modify the settings direct in FS via FSUIPC for Ground Vehicles, but for Airline/ General/ Ships & Ferries in FSUIPC there is a Hack that controls those via Offset (check Offset Status List), Offsets 0x0250 / 0x0251 / 0x0252. But you can for FSUIPC4 and FSUIPC5 use the new Facilities under [Traffic Limiter] in the INI file, but also controllable via Offsets, 0x86E0 to 0x86E7. Thomas

Because something on your system decides so. Did you re-download the installer ? The installer does check P3D and its version but only to make sure the P3D is not older than the minimum required version. The installer does not check if the P3D version is in a higher version with FSUIPC. But in any case it does not force FSUIPC_Installer to crash at all. The installer in your case crashes before it is doing anything, even a messed up Registry would be noted but not forcing a crash. In case you are here the only one with that problem there is something on your system that forces that crash. That what it looks like with P3D HF1 and 102 / 103 That's on Win10 with MS build Antivirus (defender) only. Thomas