John Dowson

What is 69632 - is that a custom control number? I have no idea what that is or how you would access via FSUIPC, unless it is one of the values added to the PMDG offset area. Are there changes to the SDK that require an update of the PMDG offset area? Maybe if you can show me the latest SDK header file I can compare it to the one we used the last time we updated the PMDG offsets, to see if it has changed.

But where are they getting the values from? You also say so I presume the offsets are holding the correct values. To make sure, you can log them using the Offset logging facility. If the offsets are correct, there must be something going on with how your external display is getting these values.

If you are assigning in FSUIPC, best to start with an empty profile in MSFS for that device. If you create a new profile in MSFS, it will be empty by default, so just do that for each of your controllers (except mouse and keyboard, and also leave the default profile for the xbox one or 360 controller if you have one of those). What do you mean 'nothing happens'? You should assign when you have an aircraft loaded and ready-to-fly.

Which aircraft? And as @Djeezsays, make sure you are using the latest official version ot one of the beta's (7.0.8, 7.0.9a or 7.1.0a)

Ok, thanks for letting me know.

Better to keep your TBM as profile specific. You can copy your TBM axis profile section to the general axis section, then that can be used by other/all aircraft (not in a specific profile) and also change as needed (without affecting the TBM). You can then import those assignments when you create another new profile (although you can do this also by specifying a new profile based upon your TBM one). It is always a good idea to have at least the main axes defined in your general axis section. If you experience your issue again (i.e. axis controls not wprking), then please show me your latest FSUIPC7.ini and .log files from that session.

Is anyone using this beta release? If so, I would appreciate some feedback. Thanks.

Not much activity here - is anyone using this? Any feedback would be appreciated, both positive and negative. If nobody wants/needs the access to the additional buttons, I can drop this update for FSUIPC6.

What do you mean by ' FSUIPC7 is sending 4 Digits only from the FS'? The COM1/COM2 frequencies in offsets 0x034E & 0x3118 are in BCD format (4-digits only). Try offsets 0x05C4 & 05C8 which contain the frequency in HZ as 32-bit ints.

Well, there is always some logging, but yes, you can activate the axis controls logging when you start your landing procedure. You could also maybe log offset 0x0366 (as U16), SIM ON GROUND, which will then add a log entry when you touch-down so I can tell when your ground steering starts.

Yes - FSUIPC6 is installed in the folder you chose (or accepted) during the installation process. It will default to your previous installation location, if either FSUIPC5 or FSUIPC6 is already installed. If not previously installed (which would be your case if you just installed P3Dv5) it will default to either the location of your add-on.xml file (if it does, you should change this) or maybe c:\FSUIPC7 (I can't remember if I made that change to FSUIPC6, sorry). But, this is all explained in the provided Installation and Registration document - please see that. John

There is no point attaching a log file without axis logging enabled - it doesn't show me anything! And its very strange that you say that it sometimes is working and sometimes is not working...there must be something different going on in each of these situations, and you need to try and work out what is causing this. The logs can help. So, as I said, please activate logging for axis controls. This can generate large log files, but don't worry about that (you can always zip them up to show me them). Then, try and capture a log for when it is working and for when it isn't (with same aircraft/assignments). Then compare the logs to see if they reveal anything. You can also zip them up and post them and I will take a look. It may also help if you keep the log/console open so you can see the log in real-time. You can also start a continuation log (so that the landing sequence is isolated in its own log file), but if you do this I still need to see all the log files generated, not just the last one.

That shows it was the Logitech MSFS plugin - this is a common issue with this plugin. If you are using it, you can manually add it back in to your EXE.xml. Your EXE.xml with both should look like this: Note that white space is not important in xml files, and the FSUIPC7 installer creates its entry with no white space (including new lines) - this doesn't matter. Yes - the installation will now continue and complete, but FSUIPC7 will not be auto-started with MSFS. To resolve, you have to do as the log message says, remove/rename the EXE.xml file and then re-install.

There is currently no lvar support in FSUIPC7. This is documented in many places! I recently released a WASM + API + test client for lvar/hvar support - see I am currently working on integrating this new API into FSUIPC7, to provide access to both lvars and hvars. Until that is released, you cannot use the lvar functionality in FSUIPC7 (it has been removed , hence the error) and should use MobiFlight directly for accessing lvars.

I've done this now. If there is a corrupt EXE.xml, the installer will now log the following lines and continue:

Ok - I may have forgotten to compress the executable in the earlier version.... There seem to be a couple of other add-on installers out there that are corrupting the EXE.xml - or maybe writing it in a format that the FSUIPC7 installer doesn't understand. If you could attach your renamed EXE.xml, I will take a look. I'm also going to see if the FSUIPC7 installer can handle this a bit more gracefully - its getting to be a common problem,

First, for all such issues I need to know which flight sim and version of FSUIPC you are using, and I need to see your assignments (your ini file) and a log file generated that is showing your issue (i.e. with axis controls logged). If it is sometimes working and sometimes not, then a log for each situation would be useful to see what the difference is. Is that when it IS working as well as when it isn't? Or do you mean when it is? Is the latency on the steering tiller itself or on the aircraft movement?

If the installer crashes it is usually a problem with a corrupt EXE.xml file. You need to delete this file (or rename) and then re-run the installer. Depending upon whether you have an MS Store or Steam install, this file will be in the following location: Steam: <user>\AppData\Roaming\Microsoft Flight Simulator MS Store: <user>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache Not sure what the size of the previous installers was, but this shouldn't have changed by much. Current size is 11,660KB. Make sure you extract the installer from the zip file before you run it - don't run it directly from within the zip....

Have you asked about this over on the FBW forums? There also seem to be quite a few posts on the Asobo forums on starting the A320, e.g. https://forums.flightsimulator.com/t/cant-start-engines-airbus-320/358396/9 Does this work via the UI controls? If so, you could see what event are being used and try to duplicate. Otherwise, if there are any A320 users out there that have this working, maybe they can comment... Joh

Ok, tested with this and now both the old and the new offsets seem to work ok. The old offsets only allow 0/1, but you can also now write 2 to those offsets, which will set the EX1 simvar correctly but the non-EX1 version will get changed back to 1. I see no harm in allowing this, but I could also revert the old offsets back to only allow a 0/1 to force the new offsets to be used...

Did or do you have a Saitek Pro Flight Throttle Quadrant? Of not, you can remove these lines from your [JoyNames] section: A=Saitek Pro Flight Throttle Quadrant << MISSING JOYSTICK >> A.GUID={2AA55AD0-177E-11EB-8002-444553540000} C=Saitek Pro Flight Throttle Quadrant C.GUID={AC57F5C0-4ECD-11EB-8001-444553540000} D=Saitek Pro Flight Throttle Quadrant D.GUID={0BF99240-4F2D-11EB-8002-444553540000} And also your assignments to device 'A': 19=PA,2,K72,9 -{Key press: shft+H}- 20=PA,3,K80,24 -{Key press: alt+P}- Other than that, your ini looks ok, although you should change this: to You log shows that you didn't even load an aircraft, so I don't know why your assignments weren't working. Please load an aircraft and then if your assignments aren't working, show me your updated log and ini files. Note that all your axes assignments are in your TBM930 profile - you have no general axis assignments, so you won't have any axes working except in the TBM930. You do have some general button assignments, all to key presses. Your TBM930 profile button presses are to controls, which is generally better.

First, please make sure you are using the latest official release, v7.0.8. If not using that, please update first. Then, I need to see your FSUIPC7.log and FSUIPC7.ini files. That just means that you already have a profile assigned to the loaded aircraft. Note also that, by default, when you create a profile for an aircraft, the full aircraft name is used to assign to the profile. So, if you load a slightly different version of the aircraft, the profile won't be assigned. Rather than re-assigning the aircraft to the same profile, you should edit your ini file to give a substring name for the aircraft that identifies all versions of the aircraft (and no others). Your profile assignments will then work with all versions of that aircraft.

This doesn't matter. Very strange. I don't really no what you are talking about, sorry - must be to do with your "Legacy" format. However, all facilities provided by FSUIPC7 are accessiblee from the main window. Either 'Show...' that, or try Alt-F, which is the default HotKey to display the main window.

Ah, ok, thanks. I'll also test with this later.

Can you please show us your FSUIPC logs, as before, but using that FSUIPC6.dll please.