John Dowson

No. This is the problem - that will just load the flight plan. Use the Load button on the bottom left of the scenario dialog box, or from the Scenario drop-down menu. John

From page 33: What you are expecting is correct. Looks like I have introduced a bug somewhere recently and the offset and parameter are not being stored correctly. I will look into this asap. John

You can but a new license for FSUIPC7, and will get a discount if you have already purchased another version of FSUIPC (4, 5 or 6). I will send you a trial key. John

Have you tried selecting yes? I think the message is misleading, it is just asking to move the aircraft to the point specified in the auto-save file.... By selecting no, it is just leaving the aircraft in the same position. John

No - don't think so, but you can use offset conditions. From the Advanced User guide on key programming: So you can use offset conditions rather than compound conditions on a button. Convert your assignments to use an offset condition, rather than a button condition. I am only going by the documentation - try it but if it doesn't work, switch to using offset conditions. I don't see why compound button conditions cannot be used on key press assignments though. This is maybe something I could add (if this doesn't already work) in the future. John

It is logged if you ask FSUIPC to log this, as I have advised. It is not something that should be always logged...well, its been like this for 15+ years so I don't think this needs to be changed now! If you want this logged, just keep those additional logging directives in your ini. Cheers, John

Hi Ray, No, I haven't forgotten... I didn't realise it was you posting, was in a rush and just fired off a stock response for such issues when using PMDG aircraft. Not as far as FSUIPC is concerned - it just calls the simconnect function to save the flight each time an auto-save is performed. The timestamps are milliseconds since start, so the difference between them is just over half a second. You can try logging auto-save and either keep the logging console open or take a look at the log file when you get a pause, and this should tell you if its related to auto-save or not. To log auto-save, add the following to the [General] section of your FSUIPC6.ini file: Debug=Please LogExtras=x4 Are you using the traffic limiter? If so, as its only happening at the start of a flight, presumably when there is lots of AI traffic injected, maybe it is related to this, with FSUIPC trying to remove traffic that is continually getting injected? Just a thought (and I can't remember this ever causing issues before) - you can also log the traffic limiter by using a LogExtras value of x100 (or x104 for logging both auto-save and the traffic limiter). Otherwise I am not sure what to advise. Is this a new issue? Cheers, John

But this is clearly explained in the Installation and registration guide: What do you not understand about that?

There isn't that much information, and it is spread thinly. The Asobo/MSFS documentation is the reference documentation, and the MobiFlight discord server (as well as the HubHop site) is also very useful. There is also plenty of documentation that comes with FSUIPC. Lua is the scripting language that FSUIPC supports - I don't provide any documentation on standard lua (use google/www for this), but documentation is provided on the additional lua functions I provide that are specific to flight simulation, and how lua plugins are used, and there are plenty of examples included. Also check out the FAQ and User Contributions sub-forums here. John

Long pauses with PMDG are almost always due to auto-save, and these are getting worse as Microsoft increases anti-virus protection. You need to exclude various folders from anti-virus scanning. See

This is because the loaded aircraft is already assigned to an axis profile. Once this is done, you can only assign axes to the same profile. If you want to assign an axis to the general profile, start with an aircraft that is not already in a profile. If you want to remove that aircraft from the profile, you have to do this via editing the FSUIPC7.ini, by removing the aircraft name from the profile section (best done when FSUIPC7 is not running). Disable means unchecked. It does say that this option is 'enabled by default', and by default the option is checked (i.e. enabled). Not sure where the confusion comes from. What DC3 are you using? If this is the Duckworks mod, it looks like the throttle is controlled by an lvar in this aircraft - see John

No. Events are standard FS controls. Presets are a different mechanism. A preset is a name associated to a string of calculator code. When you execute a preset , the calculator code is sent to the WASM and applied to the current aircraft. When you select for an assignment, you can choose to assign to an FS control (event), a preset, or an Input Event (introduced in the latest version of FSUIPC7, 7.4.0, released a few days ago). Did you check Select for Preset? Look at the checkboxes at the bottom left of the key assignment panel. John

Please consult the documentation before posting - from the Lua Library reference document: so it would be: ipc.execPreset("AS1000_PFD_HEADING_SYNC", 0) John

For the G1000 (stock and Working Title), you should use the available presets. Take a look at https://hubhop.mobiflight.com/presets/ and search for AS1000 (as all G1000 presets start with this). Alternatively, in FSUIPC7's Button assignment panel, select to send a preset and click the Find Preset button. Then look under MobiFlight->Micorsoft->Generic->Avionics, and you will see the following presets: And also similar presets for the PFD FMS. Could it be those? Or look through the available preset list.

No problem, glad you figured it out. Your assignments look fine so I was wondering what the problem was and was going to take a look at the aircraft to see if those presets were still valid... Thanks! John

As the documentation states: So the offset you are reading hold the ATC id, which seem to be the Airline + Flight number, not the tail number. To get the tail number, you have to change the options, which for airborne traffic are at F068: Alternatively, you can set the TCASid ini parameter: TCASid=Tail See the Advanced User guide on this ini parameter. John

Si el gamepad es un dispositivo XINPUT, consulte la nota sobre este tipo de dispositivos en el archivo README.txt:

@Davide You attached a screenshot containing your key details. NEVER share or disclose your key details in a public forum. This invalidates your license. I have removed your screenshot but if you do this again I will invalidate your key. Did you actually read the provided documentation on this issue, as indicated in my comment you quoted?

Post them individually. Your limit will increase the more you post. If too large, you can also send them to me in a message - click my user icon then message. If you are assigning with 'Send direct to FSUIPC calibration', I do not understand why you cannot see the axis values change in the calibration panels. PMDG aircraft do sometimes have issues with FSUIPC calibration. If assigning with 'Send direct to FSUIPC calibration' causes issues, try assigning with 'Send to FS as normal axis' and remove the calibration. I don't understand why this was previously working and has suddenly stopped. What has changed? You also said that this was for the x-axis/aileron, but now you also say that this applies to the y-axis/elevator as well. Has it changed again?

Yes, an Input Event can also trigger a standard FS event/control as well as activating hvars, and setting other variable types (L, A , etc). Not exactly. It can depend on the current state of another button, or to the flag associated to the button, which is toggled each time the button goes from off to on. Yes - you do this by manually editing the ini file. You need to make the first assignment, comment that out in the ini file, reload the ini file and make the second assignment. Then, remove the comment for th first assignment and reload the ini file again. Doing this, you can have as many assignments as you like on a single button press or release. This is normal, as i have said - the Input Event will trigger the FS control. You do not need to assign to both. First, just assign to the control and see if that works. It may work in the sense that the function is performed, but the UI may not be updated. If this is the case, switch to using the Input Event. You should not need to also have to assign to the control - when you trigger the Input Event, the control will also be sent. John

Are yo using any 3rd-party anti-virus software? This seems to be an issue with McAffry blocking the installer.

What are your two questions? I do not see any there.... Please note that I support FSUIPC ONLY. I do not, and cannot, know about every aircraft and every controller/device. You really need to understand some basic things about MSFS and how the different control mechanisms work. I do NOT support this. I provide access to these mechanisms/functionality, not information on any specific aircraft. Although I try to help and point you in the right direction. I cannot help you to implement things if you do not understand the basics of MSFS. This is beyond the scope of what I provide. And these sort of topics take up far to much of my time.... If you have any questions regarding FSUIPC, I will answer them. But I am sorry but I just don;t have the time or patience to explain the vrious different control mechanisms, what lvars are, what calc code does, how to discover hvars, etc. That is up to the user. I just provide the mechanisms so that you can use these in assignments. Furthermore, I have explained in detail what you need to do for this assignment. You don't seem to have even tried this. Please re-read the advice I have already given, I really don't know what more to say. I am closing this topic now. John

Strange question....the latest release allows assignments to Input Events, released yesterday, and also in the beta version that you were previously using...

No. The communication is between WideServer, which is now built into FSUIPC, and WideClient. You can have WideClient running on as many PC's as you like, but they all communicate to WideServer/FSUIPC on the FS machine, not with each other. John P.S. Why post the same question three times? I will delete your other posts.

I understand what is happening, what I am saying is that it is impossible for FSUIPC7 to start another copy of itself (unless you specifically ask it to via the [Programs] section of the ini file). Something else is starting another copy, maybe MSFS, maybe another add-on, I just do not know. What happens if you remove the start of FSUIPC7 from your EXE.xml - is it still started or are no copies started? Try that. If FSUIPC7 isn't started, add it back and see if that fixes things. Other than that, I cannot really help. This has nothing to do with FSUIPC7 itself. If two copies are started via the EE.xml (that previous test I mention should tell you this), then maybe ask on the Asobo forums. John