Releases: opiopan/fsmapper
Releases · opiopan/fsmapper
v1.4.3
New Functions
- Command-line options and parameters now allow you to specify the window state at startup and the script to be executed. For more details, refer to this section.
Bug Fixes
- Fixed an issue where
mapper.enumerate_display_info()
did not return correct values for sub-displays with negative coordinate values.
v1.4.2
New Functions
- Expanded the information returned by
mapper.enumerate_display_info()
:id
,name
,adapter
Bug Fixes
- Fixed an issue where the display number specified in
displayno
parameter formapper.viewport()
might not match the display number assigned by Windows when a display is set to “Disconnect this display” in Windows Display Settings.
v1.4.1
Improvements
- Improved the algorithm and added a configuration parameter to address the issue where popped-out instruments in MSFS cannot be operated via touch.
Bug fixes
- Fixed an issue where the number specified for the
displayno
parameter inmapper.viewport()
may not match the monitor number shown in the Windows Settings app.
Others
- Upgraded the Windows App SDK from 1.6.3 to 1.6.4.
v1.4.0
Touch operation improvement for the MSFS instruments
- Completely revamped the workaround logic for addressing the issue of touch interaction with popped-out instrument windows in MSFS. Previously, fsmapper used secondary mouse messages generated by touch actions as triggers to perform mouse emulation interpretable by MSFS. The logic has been updated to use WM_TOUCH as the trigger. Consequently, the workaround logic now operates in a DLL injected into the MSFS process instead of the fsmapper process. These changes resolve issues where the workaround failed to function properly on certain touchscreen devices.
- Made parameters for touch interaction workaround configurable via the Settings page.
- Added parameters to address issues specific to Duet Display. For more details, refer here.
Others
- Updated the logo displayed when connected to MSFS 2024 to use the MSFS 2024 version instead of the MSFS 2020 version.
- Upgraded the Windows App SDK from 1.6.1 to 1.6.3
v1.3.0
New Functions
- Added functionality to dynamically integrate exported instruments from DCS World into a virtual instrument panel
- How to Integrate DCS instruments
WindowImageStreamer
objectCapturedImage
object
- In addition to the traditional method of displaying a viewport window as a Layered Window, a method using DirectComposition for composition is now available. For details, refer to the description of the
ignore_transparent_touches
parameter in themapper.viewport()
function. - To access user profile-related folder paths, the following variables have been added:
Performance Improvement
- The message pumping thread for the viewport window and the event-action mapping thread have been unified, improving the responsiveness of touch interactions.
Others
- Upgraded the Windows App SDK from 1.6.0 to 1.6.1
v1.2.1
- The limitation on code points that can be registered with BitmapFont has been removed, allowing you to specify code points in the range of 0-255 instead of being restricted to the ASCII code range
- Improved the efficiency of DCS exporter
v1.2.0
- Full support for DCS World is provided. Refer to the following sections in the documentation for more details.
- Upgraded the Lua version from 5.4.6 to 5.4.7
- Upgraded the Windows App SDK from 1.5.240627000 to 1.6.240829007
- Fixed an issue where the background color of the fallback window for a captured window was incorrect
- Fixed an issue where overlapping lifetimes of vJoy objects for the same device prevented proper functionality
v1.1.1
- Preparation for the release of Microsoft Flight Simulator 2024:
- Moved the library for interacting with Microsoft Flight Simulator from the
fs2020
namespace to themsfs
namespace - The value notified by the
mapper.events.change_aircraft
event can now also determine the version of Microsoft Flight Simulator
- Moved the library for interacting with Microsoft Flight Simulator from the
- Improved of the export script for DCS World
v1.1.0
- First step towards DCS World support:
You can now use themapper.events.change_aircraft
event to retrieve the start and end of missions in DCS World as well as the name of the aircraft you are piloting - Expanded the information of a table conveyed by the
mapper.events.change_aircraft
event - Windows App SDK has been upgraded to 1.5.5