John Dowson

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?

You cannot change that file - it is generated on-the-fly from the macros loaded. You need to define your own macro for GoAround for your aircraft if the default implementation isn't working, either in a PFC.mcro file (for all aircraft) or in an aircraft-specific macro file. Please see the PFChidDLL User Guide on configuring macros, as well as the FSUIPC documentation on macros and other support requests on defining macros for PFC devices. John

You can use the lvar XMLVAR_Transponder_Mode with the following values: 0 - ALT RPTG OFF 1 - XPDR 2 - TA ONLY 3 - TA/RA 4 - STBY To assign to an lvar, you can either define your own preset, use a macro or add the lvar to an FSUIPC offset and use the offset controls to change the offset value and this update the lvar. For example, to use a preset, add the following to your myevents.txt file: //HorizonSim/787-9/Controls Horizon_787_Trannsponder_Mode#$Param (>L:XMLVAR_Transponder_Mode) and assign to that preset with a parameter of 4,0,1,2 or 3 for the various positions. John

That will be the 'F' key. Did you change this> The default is to use Alt+F, which is: InvokeFSUIPCOptionsKey=70,12 Your log should also tell you what hot-key was registered, e.g. 250 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) John

No, the same offset is used. What aircraft are you flying? How have you assigned the throttle? Could you show me your lua script, FSUIPC7.ini and FSUIPC7.log files please. Please add offset logging for offset 0x310A (as UB in hex), and once you have set auto-pilot please activate logging for Axes Controls.

That is because you haven't set-up the brake lever button correctly. If you are not using the joy letters functionality (you should!), then just set the brakeLeverJoystickLetter variable to the joystick number, i.e. local brakeLeverJoystickLetter = 2 I have modified in the attached to make it clear that you can use the joyletter or number. John nanchangBrake.lua

No. As far as FSUIPC is concerned, your controller is just a collection of buttons and axes just like any other hardware throttle, and setting up all controllers is exactly the same. What is more important is the aircraft you are setting this up for. I don't have the FSLabs A320, but I think that uses quite a few custom controls via the Rotor Brake control. You need to check what custom controls are available if the standard controls don't work. These should be documented with the aircraft, or check the FSLabs forums. You can also try logging - this should tell you if a standard event/control is used or a custom control (a custom control number or the Rotor Brake control parameter) . Activate logging for Events (non-axes controls) and open the logging console. Then you can click the function in the VC and see what is logged and then use that (i.e. assign to the event/control and parameter used). Also I think the Pilot's Deck plugin works for the A320 - you could check that out and see what that uses. John

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. I have moved your post, but please take care to post in the correct forum for support. What have you tries? What problems are you having? Does FSUIPC recognise your throttle? If so, it should be relatively straightforward to assign. What aircraft are you using in P3D?

You can save offset data when saving a flight using the SaveDataWithFlights ini partameter - see the Advanced User guide on using this parameter. It can be controlled from the Miscellaneous option (Options->Miscellaneous...) Reload FSUIPC data - change this from Never to Always or for Autos. John

This has been reported many times already - see John

It wasn't obvious where to download the new installer in the post I referenced as it was included in a comment further down the page. I have updated this now to reference the installer in the first post. You can download from here: https://fsuipc.simflight.com/beta/Install_FSUIPC7beta.exe. John

That link is good, Your log file shows that FSUIPC7 was auto-started via the EXE.xml file: As I said in my post above, there is an issue with lua performance when FSUIPC is started this way. Can you either exit FSUIPC7 once started and restart it manually, or better to re-install and accept the default installation options, which should auto-start via the batch file and not the EXE.xml file. John

I get a 404 error (page not found) with that link.

No problem...however, I just updated the attached script, so please download again if you already downloaded.

Can you try the following lua script. To use, first save this file to your FSUIPC6 installation folder (or your Lua library folder if you have set a different folder for lua files via the LuaPath ini parameter). You then need to: 1. Have the lua file auto-started. To do this, add to your profile [Auto.xxx] section (or just [Auto] if using profiles-in-separate-files, in your profile file), e.g.: 2. Assign your rudder axis with Send to FSUIPC Offset, and use control Offset Dword Set and offset xA010 (you can use a different offset, but if you do you also need to change the offset used in the script, local variable rudderAxisOffset) 3. Open the lua file you installed and set the following variables to specify the joystick & button you are using to control the brake lever: 4. You can also set logging if you want to see what is happening by changing the enableLog value from false to true. 5. You can adjust the repeat rate for standard brakes by altering the brakesInterval value - increase for slower braking, decrease for faster braking Let me know how it goes and if you need further tuning. I have commented the script so you should be able to tune for your needs. John nanchangBrake.lua