John Dowson

First, please exit FSUIPC7 before attaching logs. Your log just shows that FSUIPC7 received key presses (from MSFS) and did nothing with them as you have no assignments. As these key presses were received from MSFS (and they are not masked), I don't see how FSUIPC can be intercepting these keys or preventing actions assigned elsewhere. It is also strange that initially only keyup's were received, and then only keydown's over a minute later.... Can you therefore please check things at your end, and also try with default aircraft.

Those offsets hold the value of the simulator A-type variables: 0x3160 - ATC TYPE 0x313C - ATC ID 0x3148 - ATC AIRLINE If they are being reset to be empty strings, it is because FSUIPC7 is receiving this update from MSFS. This is probably because there is no ATC for the aircraft once the power is off.... There is nothing I can do about this - FSUIPC7 just shows the data as received from the FS. If the ACARS system still needs this information, it should make a copy and use that. You can even copy those offsets to other offsets, and if you only copy when non-empty then you will always have the last available values. John

Can you show me/attach a log file please with that offset being monitored and IPC writes logging activated as well as Axis controls. Also attach your ini file. Then something is setting it to 0 - the logging should confirm this... What keyboard assignment? No.

What does this mean? What is the 'desktop screen'? Not sure I fully understand this either. If it is still in the task bar, then you did not close/exit FSX. It is not possible to have two copies running. Well, there is something wrong somewhere...I have already advised to re-install FSX.... John

If you change a lua script, just run it to pick up the changes. if it is already running, when you run it again the currently running script will be killed. For ini file changes, it depends on what is changed. Some parameters are only read at start-up, others when needed. When changing assignments, you should always do this either with FSUIPC7 not running, or with the relevant assignment panel open, and click to reload the changes after saved. Just disable logging for Lua Plugins - ipc.log statements will still be logged. No. Lua scripts are compiled by FSUIPC7 just before being ran, and they are onky ran when FSUIPC7 is connected to MSFS and you have an aircraft ready to fly (i.e. not in the main menus). Of course, you can use standard lua outside of FSUIPC7, but you will not be able to use the additional lua functions provided by FSUIPC. John

You are using a very old version of FSUIPC7 - 7.0.2 from November 2020. The latest version is 7.4.2 - please update. FSUPC will receive all keystrokes (from MSFS via SimConnect), but it will not do anything (as you are using an unregistered version) except log them, if activated.

Well, you could use FSUIPC to assign default commands to buttons and switched, and profiles for different actions for different aircraft. But if you want to use other tools for assignment, that is fine. Just remember where things are assigned and best not to assign a button/switch in multiple places.... I have had support requests with people using the GoFlight Interface Tool and not realising they were using that and not FSUIPC for some assignments! John

No problem!

You don't need this if using the FSUIPC GoFlight driver...I'm not sure what that does (never used it!), but I would remove this if you have any issues. This is the driver that FSUIPC uses for GoFlight devices, and it needs to be in your FSUIPC installation folder.

I have no idea.... something must have changed, but I have no idea what. it is the FS that opens the FSUIPC window when the add-ons menu item is selected. This is why I think your FSX installation is corrupted, and you need to verify/re-install. I do not know what else to suggest, sorry. John

0BB6 is the aileron input control, so writing to that should set the aileron position. Are you sure that you are writing to this correctly? Try monitoring that offset using FSUIPC's offset monitoring facilities (as S16). This will tell you what value the offset holds. Also, if you have an axis assigned to the aileron. that could be overwriting the value you are setting, so check that you don't have an axis assigned to the aileron anywhere, in FSUIPC or in P3D.

No, sorry - I can't see any way to select a specific AI camera. It may be possible by writing to offset 0x8680, but you would need to know the camera definition name, which I don't think is available for the AI cameras.

Do you have the GoFlight driver installed? I cannot see the GF driver being detected in your log file - this is what is in mine: ?

Ah - I had AI traffic turned off. I can see the AI traffic views now. No idea how to set one though - I will take a look....

What is the 'ai traffic view'?

FSUIPC is not crashing - it is exiting as MSFS has crashed: You are also using an old and unsupported version of FSUIPC, 7.4.1 - the latest and only supported version is 7.4.2. Please update. I do not know why MSFS is crashing. Check your windows event viewer to see if there are any crash reports there, and check the Asobo forums for similar issues. I cannot help with MSFS CTDs. This is nothing to do with FSUIPC. John

Yes, but you will not have access to the registered facilities - assignments. lua, etc I am sorry but I have no idea why the FSUIPC window isn't being opened. All I can suggest is that you try either verifying your FSX installation (easy with a steam install, not sure how to do this otherwise) or try tr-installing FSX. If you re-install, make sure that you also install SP1 and SP2. John

What do you mean by this? So it looks like this is the software that is screwing up the registry, as that phantom device with no name but the same GUID as your yoke is now showing again. I am surprised it works with those files, as your B device is missing... You have two options. If its working, just leave it as is. Otherwise, you need to go through the whole procedure again (as we are back at the beginning), and then figure out why your 'joystick wasn't working correctly'. Maybe it needs calibration in the windows game controller panels. John

There is the Pause (ms) control - from page 29 of the Advanced User guide: This works in the same way as any other control. Not 100% sure what you mean by 'I want to sleep for 750 ms between two button presses' though, as it is you who are pressing the buttons, not FSUIPC... If you overload your assignments so that multiple controls/events are sent on a button press, then you can use this control to insert a delay between the controls being sent. John

To make multiple assignments to a key press, do the following: 1. Make the first assignment to the key press, as normal. Confirm, click Ok to close the key assignment panel, then re-open the key assignment panel 2. Open the FSUIPC7.ini file in an editor. Find the key assignment just made, then comment it out by placing a semi-colon (;) before the assignment line number and save. 3. In the key assignments panel, click 'Reload all keys'. 4. You can now make the 2nd assignment to the key press. 5. if you want to make more assignments, reload the file in the editor and do the same, i.e. comment out the assignment in the file and save, reload the assignments in the UI, and then make the new assignment. Repeat until all assignments made. 6. When all assignments are made, uncomment (i.e. remove the semi-colon you added) all the previous assignments and save. Do this with the key assignments panel in FSUIPC7 open. 7. Reload all keys again. You should now have multiple assignments to the same key press. The UI will only show the first assignment and it will be grayed-out/disabled. This indicates that there are multiple assignments on that key press, and you can no longer change this via the UI, only by editing the ini file. John

No, it is NOT registered. But how? You say there is no FSUIPC window displayed. And as you are running an unregistered version, if it was displayed then the calibration tab would not be available in an unregistered copy. I am confused... And i can see/find no record of you having ever purchased a license for FSUIPC4. You purchased a license for FSUIPC3 on 10/10/2004. An FSUIPC3 license is NOT valid for FSUIPC4. You are therefore, and have always been, using an unregistered copy. If you think you have purchased a license for FSUIPC4, please let me know your order number. I do not know why you keep posting when you are not following my instructions. PLEASE do the following - if not, I cannot help you. 1. install the simconnect.dll for version 10.0.61637.0. This is the SP2/X-pack version. If you do not have this on your system, you can download from a link in this post: https://www.avsim.com/forums/topic/503093-simconnect-version-100616370/ 2. Download and install the latest VC++ redistibutable packages, both x64 and x86, available from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist 3. Reboot then re-install FSUIPC4. 4. Run FSX/FSUIPC. Can you see FSUIPC in the Add-ons menu now? If so, does it open the FSUIPC4 main window? After performing ALL steps, any issues, please show me/attach both your Install FSUIPC4.log and FSUIPC4.log files. John

This issue has been reported many, many many times, and the solution is both in the provided documentation and in hundreds of similar support requests. You need to update your VC++ redistributables. From the latest README.txt (not exactly like this in the current release though, as I have updated to make it clearer - not thatmany people bother actually reading the documentation or checking the forums before posting....): John

There is already an option to have the window always open on start-up, controllable from Options -> Open On Start. This is et automatically when a new version is detected, so that the user is aware that a new version is available. I will not disable this feature. Just update when this happens - it only takes a minute or two. Then you will have to continue doing this until you update. The other option would be for me to display a separate pop-up box when a new version is available. But then you would have to acknowledge that message, just as you need to close the main window. Sorry, but I will not be changing this. I get too many support requests from folks using old versions, and not checking to see if a new version is available first. This feature is implemented this way to prevent such issues. John

But why? Why do this? You should ONLY install the simconnect dll/msi that comes with your FSX installation. But it was previously working WITH FSUIPC...your issue was that FSUIPC is not registered, and that the FSUIPC main window was not being displayed. It would help both of us if you could just follow my instructions and report back... i am now confused about your situation. Is FSUIPC installed? is it registered? If it is not installed, please install. Any issues with installation (or if FSUIPC is not showng in the Add-ons menu after installation), show me the installation log. Can you register ok after installation? If you have problems with registration, let me know your FSUIPC4 order number so that I can check your registration details here.

Thanks - all looks good now. Use the attached ini file and you should be ok. FSUIPC7.ini John