John Dowson

Yes of course. FSUIPC6 v6.2 will be compatible with P3Dv6. I am planning to release this version at the weekend. It is a free upgrade for FSUIPC6 users. John

Yes, you need to purchase a WideFS7 license to activate WideServer in FSUIPC7. The license is per user, so you only need one license. Note also that it is also possible to run FSUIPC7 on client PC's with no additional license required. This is not exactly the same as using WideClient, but should be suitable for most needs. Please see the appendix in the Advanced User manual on how to set this up. John

Please see the provided documentation - the Installation and Registration guide. There is a section on invalid key issues. If you are entering your details correctly, then the issue will be that your VC++ redistributables need updating. Please also note for future use that you should use the FSUIPC7 sub-forum for all issues relating to FSUIPC7. John

FSUIPC already uses the facilities interface to get information on the nearest airports to the user aircraft, held in offset 0x0658. It doesn't use the SimConnect_AddToFacilityDefinition function though - I don't really see a need for this in FSUIPC.... What information exactly do you want to access via FSUIPC?? Can you provide a use case of want you actually want to do/achieve with this in FSUIPC?

Yes, the general button section is inherited in profiles, but not for axes. This is explained in the user guide. It works this way for technical reasons and cannot be changed. It has been like this for 15+ years. If you want to use the general axis assignments, delete the profile specific sections. When you create a profile-specific axis section, you are asked if you would like to import the general axis assignments - this is done only when you initially create the profile specific axis section. After that, it is up to you to update this section if needed when you change the general axis section.

The way the tracking for GPS strings is calculated (i.e. ground tracking used with excessive winds) has been stable for 15+ years - I am not going to change this. Offset 0x0580 is requested at sim frame rate, and offset 0x6040 is requested at visual frame rate. If the offset (and therefore tracking) is being updated at a lower rate, then this is because the associated simvars are being updated at this lower rate. There is nothing I can do about this, sorry. I really don't understand why you are seeing such low rates without excessive wind. This is what I see: With excessive wind, when offset 6040 is used, I see similar results to you, with the tracking updated every second or so. This must be because the sim is only updating the simvar GPS GROUND MAGNETIC TRACK every second. I have also tried changing the request frequency for this simvar to frame rate, and the result is the same, Therefore the tracking update rate in strong winds will only be every second or so, and I cannot do anything about this.

Yes, of course.... Of course not, as they are using profile-specific axis assignments. This is the point of a profile-specific assignment section... The whole idea behind profiles is that the assignments are different for different aircraft. It makes no sense at all to update/change a profile-specific axis section when updating the general axis section, as this would override the specific assignments for that profile. If you want to use the general axis assignments for an aircraft, then don't add a profile-specific axis section. I think you are missing the point of what a profile is....

Yes - to change an axis assignment (in the GUI) for a profile, you need to load an aircraft that uses that profile first.

Sorry, but please check again - there is/should be an Add to Cart button on the SimMarket page, to the right of the screenshots. Which version are you interested in?

MSFS knows nothing about FSUIPC or the FSUIPC7.ini file. It is FSUI{C7 that re-writes the ini file on start-up, and each time you close an assignments panel. When you see "-{MAGNETO1_SET}-" or "-{SET_STARTER1_HELD}-" these are comments, and are always re-written based upon the control of the assignment. If you want to change a control, you change the control number and parameter (if needed), not the comment, i.e the part in bold. 0=CP(+A,8)A,30,C66400,0 -{MAGNETO1_SET}- If you change the comment only, that will get re-written based on the control number when you start FSUIPC7.

I only set up some tests with presets for this (not lua - but the underlying mechanism that executes the calc code is the same) both using buttons and axis assignments. As I said, it didn't work for me when sent using the same value to set multiple simvars, only when using registers. I don't know or understand why. Something else may be going on - I also had an issue with two presets that looked/are exactly the same, but one works and the other not, so it could be related to this. I don't have time to look into this further at the moment. I may revisit this at some other point. Just use whatever works for you.

When you have removed that additional P, you may also want to remove this line: You also need to remove/re-assign the buttons/axes that were assigned to your device A: John

I have no idea.... I was testing with presets. Simplest example, to just set lever to 50% on a button press, this works: Test Two Engine Throttle 50#0.5 s0 (>A:GENERAL ENG THROTTLE LEVER POSITION:1, percent over 100) l0 (>A:GENERAL ENG THROTTLE LEVER POSITION:2, percent over 100) but this doesn't: Test Two Engine Throttle 50#0.5 (>A:GENERAL ENG THROTTLE LEVER POSITION:1, percent over 100) 0.5 (>A:GENERAL ENG THROTTLE LEVER POSITION:2, percent over 100) For further information, see that discord thread. No idea why...

No it isn't. It is the syntax to add a compound button condition. To assign two controls to one switch/button, you just duplicate/overload the assignment. The log you posted is useless - I see no button presses. Did you activate logging for buttons & keys? You also have logging for axis controls activated - please turn that off. And you used the New Log feature, which I explicitly asked you not to use as I need to see a full log. However, looking at your ini: First, you have an additional 'P' (highlighted in bold) that you need to remove. Then, when you press button 30 without button 8, MAGNETO1_OFF will be sent. When you press button 30 with button 8 being pressed, MAGNETO1_SET will be sent, followed by MAGNETO1_OFF. You probably want: i.e. you only send MAGNETO1_OFF when button 8 is not pressed. Similar changes needed for this: to But I am confused as to what you are actually trying to achieve with this....

it is valid RPN code, but it doesn't do what you expect when I tried it - there is a discussion about this on the MobiFlight discord channel: https://discord.com/channels/608690978081210392/1028408626643214336/threads/1121089790553632850 If it works as expected for you, then thats fine. Just didn't work for me. i was testing using presets, not lua, but they both use the same mechanism to execute the calculator code, so not sure why it works for you but not for me. Look a the the code i provided: The value provided is stored in register 0 (s0), and then the register is used to provide the value for the subsequent simvars (l0). I am no expert in using registers in calc code - this was provided by the MF team in that thread I referenced. I started that thread as the calc code in the style you are using wasn't working for me and I couldn't understand why.

Ok, but I am surprised at this as it doesn't work here...I can only get it to work using registers. Ok, interesting - I didn't know that syntax in lua....! John

Sorry, I don't know what this means... Then there must be an assignment somewhere that is doing this. Logging should help - activate logging for Buttons & Keys and Events, open the logging console and see what is logged when you turn the knob. You can also attach your FSUIPC7.log and FSUIPC7.ini files here and i can take a look. Please attach complete files, not paste contents, and make sure the log is full, i.e. exit FSUIPC7 before attaching, and don't use the New Log feature. As this is about FSUIPC7 / MSFS, I will move this topic to the sub-forum for this product.

No problem - I deleted your post in the User Contribution for this script as not needed. John

You have set the key press to start the lua script: So when you press the key, it kills the script and starts it again, Re-read the post - you need to set the keypress to LuaSet Smooth Brake (not Lua Smooth Brake) with a parameter of 211

Can you show me/attach your FSUIPC7.ini file please. The log file looks strange... Also a complete log file - do not use the New Log function when posting logs....

Have you checked that the lua is actually running - have you added it to your Auto section? Try lua plugin logging and take a look at the logging console or log file...

You can assign however you like, either on a single switch or on a double switch. It is up to you. Yes - please see the section COMPOUND BUTTON CONDITIONS on page 21 of the Advanced User guide. John

No. I just want to see (i.e. attach them to a comment posted in this topic) your FSUIPC7.ini and FSUIPC7.JoyScan.csv files, both of which are located in your FSUIPC7 installation folder, in the same location as your FSUIPC7.log file. If you cannot see these files, see the addendum Identifying Files in Windows Explorer on the last page of the Installing and Registering FSUIPC7 document/pdf. And I would like to know what device you are using for the cut-off levers. You previously posted a link to Etsy, which is of no use. Please paste a link to the actual controller. I am only asking you to show me some files on your system (which are easy to find...) and provide information on your controller. This is not difficult, regardless of your computer experience... John

But why are you pasting the contents of that file. As I said: Please read my comments if you want assistance. Also, please attach files rather than pasting their contents.

If the issue is with a corrupt weather file, the problem is in the Simconnect SDK libraries provided by microsoft that read this file. We cannot do anything about this in FSUIPC. Did you try adding that ini parameter, as advised?