Release 1.6.6120.2
User Notes
This release includes the DCS interface for the community mod OH-6A Cayuse from Tobsen and Eightball. It also contains a RWR patch and template for the F-5E 2024. There are a number of bug fixes included in this release.
Developer Notes
Click to see more information about this release
- Implement hostname support for DCS interfaces. Hostnames need to resolve to an IP V4 address. (#857) @BlueFinBima
- Fix to support the change to the ED Hornet UFC cueing indicator character mentioned in #854 @BlueFinBima
- Fix for #848 to correct the function of the PotentiometerIndicatorClickable @BlueFinBima
- Corrections to the CH-47F CDU needed because of ED module changes. @MadKreator37 @BlueFinBima
- Add F-5E 2024 RWR viewport template. @BlueFinBima
- New Patch level for 2.9.10.4160 which changes the RWR for the Hornet and CH-47F, and adds viewport patch for the "F-5E 2024" @MadKreator37 @BlueFinBima
- Fix for #854 which was caused by the width of the apostrophe character being too great. @BlueFinBima
- Fix for "Reset Monitors" problem described in #847. This fix reintroduces a problem with the Lock Aspect Ratio tick box, but this is of lesser consequence. This fix has appeared in 1.6.611 Hotfix 1. @BlueFinBima
- Pilot Callsign not populated in Falcon Interface #852 @Todd1215
- AH-64D - Change of the name for the standby altimeter which might require minor changes to existing Apache profiles. @BlueFinBima
- Fix for deserialisation error on the AH-64D MFDs. @BlueFinBima
- Additional flight control elements added to the interface of the CH-47F @MadKreator37 @BlueFinBima
- Add the OH-6A Cayuse / Loach Soft Interface from Tobsen and Eightball. @MadKreator37
- Fix for #846 which reports that some/most output binding for the CH-47F are no longer working after 2.9.9.2280 changed the
devices.lua
in a non-backward compatible manner. @BlueFinBima - Fix for Hornet ADF switch problem in the F/A-18C type 1 interface and also the JSON version #844 @BlueFinBima
- Fix for empty rectangle being passed to ConvertToDCS in MonitorSetupGenerator when simulate monitor in profile tool is selected. #584 @BlueFinBima
- Tighten up the profile monitor checking against the physical displays in
HeliosProfile
because it was returning a match when the profile only contained a subset of the real monitors. Now the number of Monitors in the profile must match the number of displays. @BlueFinBima
Full change notes from previous releases
Iris Screen Exporter can be downloaded here