John Dowson

@GeorgeBarlow Sorry for the delay. I did ask Pete about this when he got back from his holidays, and he says he has no technical references of any Cockpit Sonic hardware. Many years ago he developed a driver for a 737 forward overhead from CockpitSonic for ProSim, but has no experience with any other hardware from CockpitSonic, and that was a long time ago. Sorry I (or Pete) can't be of more help. John

That is the console window for the bat file. That is created but should be iconised, i.e. in your system tray. That window will stay around until FSUIPC7 is started, but if you kill that window, then FSUIPC7 will not start. Does that window actually show, or are you opening it from your task bar? If you just leave things and wait, you should see that console window disappear and FSUIPC7 will then start. Also, please post in the correct forum for support, which for FSUIPC7 is the FSUIPC7 / MSFS sub-forum - I have moved your post. John

I just checked your details here and they are fine. I have PM'ed you a key file to try - please see if this validates in the installer, and if FSUIPC7 is running as registered. John

Strange way to start a support request... What version of FSUIPC are you using? As you attached the README.txt (why?) from FSUIPC7, I suspect that you are using FSUIPC7, in which case you posted in the wrong forum. There is a specific sub-forum for FSUIPC7 - please use that sub-forum for all issues with FSUIPC7. I will move your post. Have you tried updating your VC++ redistributables, as indicated in the README.txt that you attached (for some unknown reason - I have and distribute that, no need to send it back to me!): This accounts for 95% of the problems that people have with registration, with the other 5% being user error... If you have done that, then please let me know your FSUIPC order number (do NOT post your key details) and I will check them here. Did you also see the section Invalid Key Problems in the Installation and Registration guide? If not, please also read that - that also tells you to update your VC++ redistributrables, and gives instructions on how to manually create the key file, normally only needed for people who use unicode. John

Many people have reported issues with the throttle assignment in the Fenix A320. You have to calibrate the throttle first in the Fenix MCDU, and then assign as 'Send to FS as normal axis' using the Throttle 1/2 Axis Set Ex1 controls. See Also make sure that you do not have any calibration - to do this create a profile-specific calibration section and reset any throttle calibration. Only add calibration if needed, as post-calibration may cause issues in the Fenix (not sure though as I don't have this aircraft). John

Duplicate post: As I keep telling you, your registration details are available from your SimMarket account, if you have lost your purchase email where they are also given. Any further issues, please use your original thread, I am closing this one now. John

As I said, you can download FSUIPC4 from either the download section of this forum, here: or from fsuipc.com, and your registration details are available from your SimMarket account, i.e. log into SimMarkey and go to Your Orders and click on your purchase and the registration details will be there.. What do you not understand? Can you not download and install FSUIPC4, or can you not access your SimMarket account?

Correction - I can add the COM ACTIVE FREQ TYPE:1 simvar to an offset, but the units is Number and not String for some reason. If I add this to the myOffsets.txt file: And I add logging for this offset in FSUIPC7, I see this logged when on the runway with COM on the tower frequency: So it looks like you can use this simvar.

Ok, I have taken a look at this and there seems to be an issue adding string values to offsets - I will investigate and get back to you. John

Looking at the PFC.dll user document it doesn't seem possible when assigning in the dll. However, you should be able to do this when assigning/calbrating in FSUIPC, using the "Map 1->12, 2->34" option in the throttle calibration pages.

You can download all of my products from the download links section of this forum, or from fsuipc.com. If you have purchased any licenses, all license details will be available in your SimMarket account. John

Would this then mean I would have to loop through all of the airports and frequencies within the current airport to determine the frequency type, or is there a more efficient way to receive the value? No - they are the airport com frequencies, not the type of the active com frequency in the aircraft. You need to read the value of the COM ACTIVE FREQ TYPE:1 simvar, as you say. What was the problem when adding the simvar to an FSUIPC offset? That would be the way to read this simvar using FSUIPC.

@jean-louis I do not understand why you posted that file. If you want me to help me, please respond to my (previous) questions. Your issue may be obvious to you, but it is not clear to me which is why you need to respond to my questions, otherwise I cannot help you. Have you installed the GoGlight driver for FSUIPC4? Please show me your FSUIPC4.log file. The loading of the GoFlight driver should be logged, together with any GoFlight devices detected.

Please try the attached lua - I have added a new local variable for the effective ground speed: John nanchangBrake.lua

The auto-save functionality in FSUIPC relies on the SimConnect SDK function SimConnect_FlightSave, which is still documented as NOTE: The current status of this function is NO ERROR, NO RESPONSE, which is Asobo's way of saying that this function is still not fully working. I have recently asked about this again on the Asobo forums but have yet to receive a response - see https://devsupport.flightsimulator.com/t/status-of-simconnect-flightsave-function-still-not-working-correctly/8743. It seems that some folks have more success with this than others, and it does seem to be dependent on the aircraft, with more success on GA/simpler aircraft than with more complex airliners. There is no list of aircraft where this function is fully working 100% of the time as far as I am aware, Although it is Asobo who provide the flight save/load functionality, it will be up to the aircraft developers to implement the saving/loading of the panel state, so you will get issues if this has not been implemented (correctly) by the aircraft devlopers. I presume Volanta autosave has the same issues as that will also be using the MSFS SDK to save the flight state. Volanta also state: Not all third-party aircraft may be supported as saving/loading of panel state can differ by aircraft. Note: If an aircraft works with the simulator's default save/load function, it will work with Volanta. which also applies to FSUIPC auto-save.

Sorry, but what is MINS? Also note that the PMDG offsets are read-only, i,e, not for input. To input values, you need to look into the PMDG custom controls. The only thing I can see with 'mins' is this at offset 0x65B4.: 65B4 2 BYTE x 2 EFIS_MinsSelBARO[2] Boolean John

You can use the windows facilities provided for this - look into Magnify: https://support.microsoft.com/en-us/windows/use-magnifier-to-make-things-on-the-screen-easier-to-see-414948ba-8b1c-d3bd-8615-0e5e32204198 John

Note that the trojan virus detected in 7.4.11 seems to have been corrected by Microsoft in Security intelligence version 1.409.501.0 (created 25/04/2024 03:28). John

Note that the virus detection in 7.4.11 seems to have been corrected by Microsoft in Security intelligence version 1.409.501.0 (created 25/04/2024 03:28). John

Yes - this seems to have been corrected by Microsoft in Security intelligence version 1.409.501.0 (created 25/04/2024 03:28).. John

Thanks for reporting this and thanks for the update. Regards, John

Yes - look under the Add-ons -> PFC menu. The PFC driver for MSFS is the same as the one for FSX, except that it is 64-bit vs 32-bit. Please see the PFC.DLL User Guide document - this is valid for both the 32-bit PFC.com driver and the 64-bit PFCcom64.dll driver. John

That is not an error from FSUIPC7 itself, but from an FSUIPC client. I cannot diagnose issues with FSUIPC clients - you need to contact the developer of the client. John

Using PFC COM devices in FSUIPC7 / MSFS2020 is pretty much the same as using them in FSUIPC4 / FXX - you need to install the appropriate PFC com driver. The only difference is that for FSUIPC4 you would use the 32-bit driver (PFC.dll) and for FSUIPC7 you need the 64-bit driver (PFCcom64.dll) - all available from fsuipc.com, COM functionality in FSUIPC7 is pretty much exactly the same as in earlier versions. John

What exactly was this message? Was it from FSX or windows? But is it detected by FSUIPC? Is FSUIPC still running with FSX? If FSX is no longer loading FSUIPC, maybe see John