FSUIPC 3.96 (FS9) und 4.57 (FSX)

Hier die Änderungen

Zitat

FSUIPC 3.966 Changes since 3.96

1. The default JoystickTimeout value set in version 3.96 has been changed to 20 mSecs, after feedback showing that some joystick drivers can sometimes fail to respond in 15 mSecs. Version 3.961 will automatically update a JoystickTimeout value of 15, set by version 3.96, to 20. Furthermore, this timeout is only applied to joysticks returning an error to the timed-out poll. Joysticks not returning any error are subjected to a time out of 4 times the JoystickTimeout value, or a minimum of 60 mSecs.

2. The JoystickTimeout now only applies to the Axes and the Buttons & Switches tabs in FSUIPC’s options, not to the Joysticks tab, nor to flight modes.

3. The "black mark" placed on joysticks which are timed out is erased on each new entry to the Axes or Buttons tabs, giving them another chance. This also applies when the "Reload" button is used to reload assignments.

4. An error in the Lua "gfd" library function gfd.SetDisplay is fixed. This error could have caused FS to crash if the string sent for the display was shorter than the display capacity.

5. The Lua event.button() function now works correctly on all buttons on all supported devices: Windows joysticks, GoFlight modules, EPIC. It works for both locally-connected devices and those connected to WideFS client PCs. It does not work with the "virtual button" offsets, however.

An example of the use of this button trapping event is also provided. "TripleUse.lua" can be started initially by an ipc.macro call in ipcReady.lua. It will allow any selected button(s) to have three distinct uses: one each for a single short press, double short press and a longer press.

6. A confusing cosmetic problem in the Joystick calibration options dialogue is fixed. The "REV" and "Filter" check boxes were not being cleared when the calibration of a control was Rest, so next time you tried to "Set" the same control, they could appear to indicate the Reverse or Filter action was enabled even though it wasn't, having been reset.

7. A long-standing error in the Options has been fixed. Amending only the Flaps detente calibrations, and nothing else in the Joysticks tab of the options, was not taken note of on exit and so the INI file was not correctly updated.

8. Fixed an error introduced in version 3.953 which had the odd (and so far unexplained) effect of making the COM and ADF frequencies slow and progressively slower in PMDG aircraft, or even possibly in other aircraft if PMDG aircraft are also installed. The actual change which caused it was found, eventually, by a process of elimination, but how it managed to have such a strange and selective effect still hasn't been determined. The NAV radios and Transponder were not affected at all!

9. Fixed an error in assigning Offset controls to axes or axis ranges.

10. Added a new INI parameter to stop FSUIPC polling the GoFlight TQ6 module. It seems that all axes and buttons on this device are already handled through Windows as a joystick device, so having FSUIPC also scan it gives dual indications in the Buttons tab in FSUIPC options (seen as Joystick 169).

To stop FSUIPC seeing the TQ6 without messing up your FSUIPC access to any other GoFlight module, change "PollGFTQ6=Yes" to "PollGFTQ6=No". This parameter will be found in the [General] section after running the updated FSUIPC, but any change won't take effect until to next start FS.

FSUIPC 4.579 Changes since 4.57

1. The default JoystickTimeout value set in version 4.57 has been changed to 20 mSecs, after feedback showing that some joystick drivers can sometimes fail to respond in 15 mSecs. Version 4.572 will automatically update a JoystickTimeout value of 15, set by version 4.57, to 20. Furthermore, this timeout is only applied to joysticks returning an error to the timed-out poll. Joysticks not returning any error are subjected to a time out of 4 times the JoystickTimeout value, or a minimum of 60 mSecs.

2. The JoystickTimeout now only applies to the Buttons & Switches tab in FSUIPC4’s options, not to Axes or joysticks tab, and not to flight modes.

3. The "black mark" placed on joysticks which are timed out is erased on each new entry to the Buttons tabs, giving them another chance. This also applies when the "Reload" button is used to reload assignments.

4. An error in the Lua "gfd" library function gfd.SetDisplay is fixed. This error could have caused FS to crash if the string sent for the display was shorter than the display capacity.

5. The option to inhibit reverser action via FSUIPC4 offset 32F8 now works correctly.

Note also that there is an error in the FSX Offsets Status document in the description of offset 3410. The bits used are of course 4, 5, 6 and 7, just as in offset 32F8 and FSUIPC3, and not 2, 3, 4, 5 as listed there.

6. The Lua event.button() function now works correctly on all buttons on all supported devices: Windows joysticks, GoFlight modules, EPIC. It works for both locally-connected devices and those connected to WideFS client PCs. It does not work with the "virtual button" offsets, however.

An example of the use of this button trapping event is also provided. "TripleUse.lua" can be started initially by an ipc.macro call in ipcReady.lua. It will allow any selected button(s) to have three distinct uses: one each for a single short press, double short press and a longer press.

7. A confusing cosmetic problem in the Joystick calibration options dialogue is fixed. The "REV" and "Filter" check boxes were not being cleared when the calibration of a control was Rest, so next time you tried to "Set" the same control, they could appear to indicate the Reverse or Filter action was enabled even though it wasn't, having been reset.

8. A long-standing error in the Options has been fixed. Amending only the Flaps detente calibrations, and nothing else in the Joysticks tab of the options, was not taken note of on exit and so the INI file was not correctly updated.

9. Additional offsets are provided for possibly more accurate computations related to aircraft position and attitude. These are:

0584, 4 byte DWORD: Bits here mark which of the aircraft situation variables (LLAPBH, Lat-Lon-Alt-Pitch-Bank-Heading) in offsets 0560-0580 were updated by FS at the time provided in offset 0588. The bits are (bit 0 = least significant): 0 = Lat, 2 = Lon, 4 = Alt, 6 = Pitch, 7 = Bank, 8 = Heading. So the value 0x01D5 means all six.

0588, 8 byte or 64-bit double floating point value giving the elapsed real time, in seconds, at the last time any of the aircraft situation variables (LLAPBH, Lat-Lon-Alt-Pitch-Bank-Heading) in offsets 0560-0580 were updated by FS.

The time is elapsed real time, not FS time, so if the data is being used to compute speeds et cetera you'll also need to check against offset 04A8 which is FS elapsed time. Alternatively deal with sim rate changes, pauses and stoppages (as in menu access).

Note that this time is that read from Windows when FSUIPC4 actually received the data from SimConnect. There is no timestamp at the transmission end. However, with FSX updated to SP2/Acceleration level, the delay between the two should be minimal.

10. An additional offset value is provided to indicate re-connections to SimConnect. This is as follows:

3BF6, 2 byte, 16-bit SimConnect re-connection count, incremented each time FSUIPC4 succeeds in connecting or re-connecting to SimConnect.

Re-connection is sometimes needed if SimConnect starves FSUIPC4 of information for longer than the timeout (set by the INI parameter SimConnectStallTime, defaulting to 1 second), other than during normal flight loading or menu stoppage times (i.e. between Stop and Start notifications).

11. Facilities have been added to allow sub-menus to be added to menus created in the "Add-Ons" menu via the use of FSUIPC offset 2FE0 and the Hot Keys table at 3210. Full documentation will be included in the next SDK update, but meanwhile the included "MenuDemo.lua" plug-in and the following notes should be sufficient to allow full use:

Having already setup the main menu, as already documented, write this, in one write, to 0x2FE0:

Byte 0 = 0x80 + slot number of main entry, as before (i.e. 0 for 3210, 1 for 3214 etc. Remember the max is 55, there being 56 slots).
Byte 1 = Response value (any non-zero value 1 - 255). This is merely a value for you to test so you know which submenu was selected.
Bytes 2-31 = The zero-terminated string for the submenu entry

There's a limit of 16 submenus per menu entry (imposed by SimConnect), and there are no further sub-levels.

When the user selects the submenu FSUIPC will fill in byte 3 of the slot with the "Response value" provided. Naturally you don't get notified when the main menu entry is selected when there are submenus.

You can remove a submenu by doing the same as above but with a null string for the submenu entry (i.e. a single zero byte).

The included Lua plug-in demonstrates addition and deletion of submenus, as well as basic things like adding and removing the main menu, detecting which entry was selected, and maintaining the menu against the imposed timeout.

Note that this facility will not be provided in FSUIPC3.

12. Fixed an error in assigning Offset controls to axes or axis ranges.

13. Added a new INI parameter to stop FSUIPC polling the GoFlight TQ6 module. It seems that all axes and buttons on this device are already handled through Windows as a joystick device, so having FSUIPC also scan it gives dual indications in the Buttons tab in FSUIPC options (seen as Joystick 169).

To stop FSUIPC seeing the TQ6 without messing up your FSUIPC access to any other GoFlight module, change "PollGFTQ6=Yes" to "PollGFTQ6=No". This parameter will be found in the [General] section after running the updated FSUIPC, but any change won't take effect until to next start FS.

Alles anzeigen