John Dowson

That would be using simvars, not the axes. @jmig You could try sending the axes to the aileron/rudder trim offsets, 0C02 and 0C04. Select 'Sent to FSUIPC offset' in the axis assignment panel, with 'Offset Word Set'. John

I also reported this to Asobo. However, there response was that these axes don't exist in FSX, so why should they in MSFS. However, they do exist in MSFS, its just that they are not documented. John

Aileron and rudder trim axes are currently not available in MSFS. If you look at the release note, under 'Functionality to be Added', you will see: 4. Re-instate aileron/rudder trim control axes: either when/if axes added back to SDK, or switch to using simulator variables John

Depends upon the pause mode used at present. There are 3 different styles of 'pause' in MSFS: 1. Active pause (default key: PAUSE): this is more like a lat/long/alt freeze - it freezes the plane, but the world moves on. Be careful when using this! 2. Sim pause (default key: ESC): takes you to the MSFS menus. Not really a pause, more of a temporary stop! 3. The real pause (no default key): this is the proper pause and is activated by the Pause On and Pause Off controls (no toggle) The third one is the one that FSUIPC7 currently uses (as there is no way to detect the others at present). This pause mode also updates offset 0x0264 correctly. I've checked offset 0x0262, and that works for pausing/unpausing (with the real pause). For the time being, I'll mark offset 0264 as partially working, until we can get the pause state correctly from the other pause modes. John

We tried that but it didn't have that much of an affect, only a few fps. You can de-activate the AI by adding ProvideAIdata=No to the [General] section of your ini.

OpenOffice is open source and also available on OS X, so you could install that for the time being.

You should be able to access it with Excel or OpenOffice (Calc). I can add a pdf version as well for future updates. John

Write is also working.

Its already added to my original comment.

For the time being, you can use documentation for FSUIPC4/5 or 6. If you don't have this, its available from here: Only the FSUIPC4 documentation is there at the moment, but I'll add the FSUIPC5 and FSUIPC6 documentation which will be slightly more relevant. John

This is the expected behavior and is due to the windows API being used only supporting the first 32 buttons (0-31). However, a lua plugin can be used to read and process (best sent to "virtual buttons" for assignment) all buttons. There is an example provided in the lua examples zip (provided with FSUIPC4/5/6) called "HidDemo.lua". That handles many axes and up to 256 buttons on a device, mapping them to "virtual buttons" in FSUIPC which will be seen in the Buttons & Switches tab and can be assigned there. All you should have to do is change these two lines: Vendor = 0x16C0 Product = 0x05B5 John Lua example attached: HidDemo.lua

First, you posted in a sub-forum not related to your question. I have moved your post for you. Please post in the correct place. Really? Where did you read this? FSUIPC6 requires a license for FSUIPC6, and a FSUIPC4 or FSUIPC5 license is not valid. There is a special upgrade price from FSUIPC5, but not from FSUIPC4. Please see John

Sorry, but I don't understand this. You do not need the SimConnect.dll with the latest build as it is compiled against the (recently added) static SimConnect.lib. John

There is no default 'Sound' folder in MSFS. I'm therefore going to remove setting a default for this parameter. It will still be read, when manually set by the user, for FSUIPC's sound interface, and it can always be set by the lua sound.path function. John

Looks like this was a problem in FSUIPC7 where the rate was hard-coded to be always 0, probably because this wasn't working in an early version of the SDK. Its now working and I've updated FSUIPC7, so this should be resolved in the next release. I'll re-check the write status before I release. John

Not related to this thread, but all FSUIPC7-beta users should update to the latest build. For details, please see I recommend all beta users to follow that thread, as that is where I will be posting updates on new build releases during the beta test period. Cheers, John

Here: http://fsuipc.simflight.com/beta/GFDevDLL64.zip Yes. John

This issue has been addressed, and hopefully fixed, in the latest release. The locations are different depending upon steam vs ms store install. For details, see Note that I will be posting there when I update the FSUIPC7-beta release.

0x0262 is for setting - its 0x0264 for reading. Please note that there are 3 different styles of 'pause' in MSFS: 1. Active pause (default key: PAUSE): this is more like a lat/long/alt freeze - it freezes the plane, but the world moves on. Be careful when using this! 2. Sim pause (default key: ESC): takes you to the MSFS menus. Not really a pause, more of a temporary stop! 3. The real pause (no default key): this is the proper pause and is activated by the Pause On and Pause Off controls (no toggle) The third one is the one to use. This pause mode also updates offset 0x0264 correctly. I've checked offset 0x0262, and that works for pausing/unpausing (with the real pause). For the time being, I'll mark offset 0264 as partially working, until we can get the pause state correctly from the other pause modes. John

There are currently issues with the SimConnect functions to load/save files. Asobo are aware of this issue. There is also a problem in FSUIPC7 related to the location of such files, and currently they won't be removed correctly. I reported this here: John

This problem didn't exist in the Alpha and Beta releases - it was introduced in the official release.... John

Thanks for reporting, I'll update.

Ok, glad its now working. This was mentioned in the release note, under 'Issues'. John

Thanks for reporting this. Looks like the reading is ok via a simvar, but the setting via an event isn't working. I'll check it to see if its an issue with the event or an FSUIPC7 issue and get back to you. This may take a while though. John

Well, that folder itself seems to be the 'default' location - this is where FSUIPC's auto-save files are saved. The ones from MSFS seem to go into different places under this folder, depending upon where you save from. Check under MISSIONS\Custom or MISSIONS\Custom\CustomFlight maybe.