John Dowson

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

I can download the zip file today/now and it doesn't get quarantined, so maybe Microsoft have now corrected this - can you try please? You maybe need to update your virus definitions if you don't have that set to automatic, or wait until you get the latest update, which is Security intelligence version 1.409.501.0 (created 25/04/2024 03:28). John

But this is just not possible. If you move the rudder while moving on the ground, the aircraft will turn, but from the rudder effect not the nosewheel steering. There is no nosewheel steering on this aircraft (as far as I am aware). If it is steering too much via the rudder only (compared to real life), then this is an issue with the model. You may be able to adjust this by updating some of the model parameters, but I cannot help with this - you need to talk to the aircraft developers. What do you mean? If you changed that section of code to exit/return if ground speed was above 20 knots/37 kph, then no differential braking would be used above this speed. You could do that, but I think what you would want is the rudder controls to also work, but it is not clear to me if you want the rudder to work when below this ground speed or above, and this is the section of code that determines when to send the rudder controls: So, please explain exactly what you would like the script to do. You can also try adapting it yourself... Note the following restrictions due to the way the aircraft is modeled - to get these changed you need to talk to the aircraft developers: - the brake lever only moves when you send the BRAKES control, so when differential braking, the lever will not be in the correct position - how the aircraft steers on rudder control only when on the ground is up to the aircraft model John

I have already pinned the topic 'Download link virus detected' to the top, which contains the link to the solution in my response. No. Windows will just quarantine the installer zip file if that is still around. It won't detect anything wrong with FSUIPC7 itself or any of the files installed, so that will not be affected, and even the Install_FSUIPC7.exe is clean. It seems to only affect the zip file, which is why the latest beta is the exe only. When I release 7.4.12, I will provide the usual downloadable zip but also separate downloads for the zip contents - the FSUIPC7 installer, the readme.txt and changes.txt files, and installation and registration guide/pdf.

Yes, I probably should...I was hoping Microsoft would fix this asap, but will create a FAQ entry on this issue for now, and maybe a sticky/featured topic in the FSUIPC7 sub-forum (although there is already one) - not that many people will find these before posting....!

This is a false-positive and has been reported many times before. See If you don't want to install, that is up to you. But the fix for this must come from Microsoft in its virus updates, and I do not know how long this will take (it has been reported to Microsoft already). This is a false-positive, and you can install by temporarily allowing the installer to be downloaded and ran - instructions in the link I posted above. John

There is no virus in FSUIPC7, and no virus is detected in the FSUIPC7.exe. However, since a windows defender virus update a few weeks ago, there is a false-positive detection of a virus by Windows Defender in the FSUIPC7 installer (i.e. in the installer, not in FSUIPC7 itself). There are many posts about this, including instructions on what to do to install FSUIPC7 for the time being. I have also informed Microsoft and hopefully this will be rectified in a future virus definition update. Those version numbers make no sense. Current released version is 7.4.11 That message should be obvious. You are using a version of FSUIPC that is expecting to be used with WASM 1.0.3, but you have 1.0.2 installed. Nothing to do with firewalls. To get rid of this warning, install WASM 1.0.3. Or better still, just re-install FSUIPC7 (including WASM) via the FSUIPC7 installer. It is also only a warning - generally you should be mostly fine running mismatched versions as I try to keep the interface roughly compatible. However, you may have issues trying to use any new features introduced in 1.0.3 (as you are still running WASM 1.0.2), if there were any. John

It should do when no braking is applied... No - the script controls differential braking, which activates when the brake lever is pressed and the rudder has > 16 degrees deflection. There is no differential braking without using the script, unless you have also assigned that directly to your rudder axis. as it is supposed to... Of course, as it is being steered by the rudder. Are you saying that you do not want any rudder changes deflection to be sent when on the ground? Any rudder deflection will effect the steering when on the ground. Why would that help? You can use the letter or the id/number, but the result would be the same. Note that no steering controls are being sent - only rudder controls. It is this that is steering the aircraft when on the ground. You can prevent this, but then you would also see no rudder deflection when moving the rudder when on the ground. Try the attached script for this. i.e. rudder controls only sent when airborne. Please look at the scripts and work out what is happening. If you understand them, you can modify them yourself to suit your needs. John nanchangBrake.lua

You will automatically get a discount on check-out if you have purchased an earlier version of FSUIPC, otherwise no discounts.

Does not match what? What do you mean by this? The ini file does not match anything.... it is unique to your system and set-up. Your ini looks like a default ini file - no profiles or assignments, and with one lua file recognised (PMCO_FNX32X.lua). You have to configure/set-up FSUIPC7 for what you want to use. Please see the provided documentation - start with the User guide and also look through the Advanced User guide. This will give you an idea of what you can do with FSUIPC7. Otherwise, please explain why you think you have an issue, and what you actually want to do with FSUIPC7. Also, before purchasing FSUIPC7 I recommend trying the trial license first (available at the top of this forum) to make sure it is suitable for your needs. But too late now! John

See this post on how to assign the Bravo trim wheel for default elevator trim controls (and AP functions): This uses a lua script for fast/slow trim control, and uses FSUIPC offsets to set the trim value. You can increase/decrease the delta for both the fast and slow trim buttons if required. This is the standard way to set-up a trim wheel in FSUIPC, providing the aircraft supports the standard controls. If not, you can still use the lua script (for fast and slow virtual buttons), but you would need to change the assignments to the fast/slow virtual buttons to whatever controls the trim in the aircraft (n the aircraft profile). Checked in the DA62 and those assignments are valid for this aircraft, but you probably want to increase the delta values - the current values of 24 (for slow) and 50 (for fast) seem a bit low. Just increase them to whatever feels good for you. There isn't much documentation that I know of, only this: https://docs.flightsimulator.com/flighting/html/Additional_Information/Reverse_Polish_Notation.htm John

I get a similar rate (i.e. every 800ms or so) when lua plugin logging is enabled: but if I turn off lua plugin logging the rate increases to roughly every 63ms (and faster rates if I reduce the ipc.sleep delay at line 59, which defaults to 48ms): So, what rate do you see if you turn off the lua plugin logging?