John Dowson

What is AAU2? What weight data from FSUIPC are you using? Have you tried monitoring the weight offsets used, to see if they hold the correct data? I have checked a few of these offsets and they seem correct in the 787-10: 0x1400: PAYLOAD STATION WEIGHT:1 - 170.0 0x1420: PAYLOAD STATION NAME:1 - "Pilot" 0x1430: PAYLOAD STATION WEIGHT:2 - 170.0 0x1450: PAYLOAD STATION NAME:2 - "Co-Pilot" ... 0x30C0: TOTAL WEIGHT: - 440876.40625 0x30C8: TOTAL WEIGHT - 13702.8886714 Not sure why they would say this. Nothing has changed in FSUIPC as far as the weight data is concerned. If this occurred after an aircraft update, it will be the aircraft update that caused this. If you need further assistance, please provide more information, i.e. which offsets are being used

I can only seem to change the heading with the Heading Bug Inc/Dec controls. The fast versions of these controls do not work either. Both the fast versions of these controls and writing to offset 07CC use the Heading Bug Set control - this control doesn't seem to be working in the FBW A320. However, it is probably better to use the FBW custom events (or presets). These events are provided in a file called flybywire-aircraft-a320-neo.evt located in your EventFiles subdirectory. Copy or move this file to your FSUIPC7 installation folder (i.e. up one level) to use. Once installed, you will have the following custom events that you can use for the FCU heading: A32NX.FCU_HDG_INC A32NX.FCU_HDG_DEC A32NX.FCU_HDG_SET A32NX.FCU_HDG_PUSH A32NX.FCU_HDG_PULL If you want to control the heading via offset 07CC, you would need a lua script to monitor this offset and send the value (when changed) to the sim using the A32NX.FCU_HDG_SET event, or, probably easier, using calculator code. If you want to do it this way, let me know and I can look into providing a script for you.

You have additional logging activated - check and clear your Log->Custom value. Looks like logging for custom value x10 (all simconnect events) The DontLogThese ini parameter only applies to standard event logging,

No, its read-only... Ok, that is strange What version of FSUIPC7 are you using? Make sure you are using the latest version, 7.3.21: 0x07CE 2 AUTOPILOT HEADING LOCK DIR:3 Responded Autopilot target heading value, as degrees*65536/360 Not sure when that was added but was quite a while ago... As I said, I am no A320 expert, but I can take a look for you tomorrow and report back. John

Which version of the FBW A32NX are you using? I am no expert for the A320, but I think this can depend on the AP mode (managed or selected). If the Autopilot Heading lock is set (offset 0x07C8) then you cannot update this value. You could try offset 0x07CE (target heading), or look at the available MF presets to see what they use to control the AP heading value, and use that - either the preset directly or the lvar (or whatever the preset is using). I will update the title and maybe some other FBW users can help.

No need to change the comments as they are rewritten. It is not possible that the control numbers change unless you change them. If you are editing the ini when FSUIPC is running, make sure the appropriate assignment panel is open first, and click the reload button once you have saved any changes. No problem. Cheers, John

If you want full access to the facilities data, you will have to use the SimConnect SDK. I can look into providing an offset area for facilities data requests, but this would return limited data. I can look into this to see what I could provide, but it won't be until at least September now. I will make a note and get back to you when I have looked into this in more detail. John

👍😎

Please see the following post: That post includes a preset for the condition lever that moves it between the 4 discrete positions on an axis. Basically the condition levers positions are controlled by the lvars L:MSATR_CONDITION1_POS and L:MSATR_CONDITION2_POS which take a value between 0 and 3, with each number representing a discrete position.

License sent via PM.

I have updated and released MakeRwys for P3Dv6. The Lorby Scenery Exporter has also been updated but not tested. Please report any issues, Thanks to Lorby (Oliver) for the fast update of the Scenery Exporter. Regards, John

Note that I have now released v6.2.0 which includes this update.

I have now updated MakeRunwys for P3Dv6. However it will also need an update of Lorby's SceneryExporter to process Add-On scenery. I will release the update version when this is available. FSUIPC6 v6.2.0, compatible with P3D versions 4. 5 & 6, has been released. John

All presets are provided by the FS community driven by MobiFlight, and available from https://hubhop.mobiflight.com/presets/. I can see you have already asked the MF team about this on their discord channel, which is generally the correct place to ask about presets. John

I haven't yet but will...don't think there is a P3D version check in MakeRunwys but I will test over the weekend. The bgl format should be the same.

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.