Releases: BitsAndDroids/FlightConnector-Rust
Releases · BitsAndDroids/FlightConnector-Rust
App v0.7.1
Connector
New features
- Revamped the custom output menu
- It's now possible to add multiple categories to an event.
- Added filters for commands so it's easier to find the event you're looking for. You can filter by creator, id, category or text in the event/description.
Fixed
- The connector now remembers if the connection was active when navigating away from the home page. The state is restored when returning to this page (the red dots aren't currently cached; this will be added later).
Technical
- Added a boatload of tests to aim for a stable foundation
App v0.6.2
Connector
- Fixed saving and retrieval of wasm outputs
App v0.6.1
Library
- Fixed wrong type of function causing compilation errors
Connector
- Resending of values now also works for wasm values
App v0.6.0
Connector
New
- Added functionality automatically starting the last used setup when Microsoft Flight Simulator 2024 launches. This requires you to toggle the start on sim launch setting if you've already set this setting. The benefit of this feature is that you don't have to press start anymore when launching the sim.
Fixed
- Wasm (custom) outputs weren't sent to the controller.
- The order of initializing the application resulted in edge cases where the default preset would overwrite the saved preset.
App v0.5.1
Connector
- Fixed missing scroll option in the custom output menu
- Aligned the home screen dropdowns to properly include the icons
App v0.5.0
Connector
- You can now filter the bundle menu (selected, all categories, etc.).
- I added a search input to the bundle menu. Searches are applied to the checkbox text and the underlying command. The search isn't case-sensitive.
- Restyled the bundle menu.
- You can now see at which interval data gets transmitted (this will be editable in the future).
App v0.4.2
Connector
- Added a max size for the logfile (20mb)
App v0.4.1
Connector
- Fixed default values being too big. By accident, if the update_every_ms value hasn't been changed, it defaults to 1000ms, rendering communication with your controllers useless.
- Added extra log entries when reading messages.
App v0.4.0
Connector
New features
- Made the rate at which messages get sent to your controller variable. This setting can be altered in the settings menu. You can now set the time between messages depending on your use case. Certain controllers like the Arduino Uno can't keep up when bulk data gets transmitted. Increasing the time between messages ensures the controller can handle the incoming data (for an Arduino Uno, 8ms seemed like the sweet spot, while the ESP32 can handle 0). The default value is set to 6ms.
- Send a connect and disconnect signal to the controller to check for connection on the controller side.
- Added ping request to actively check the connection with the connector from a controller
- Added manual retrieval of output value. This is intended to retrieve the last received value of an active output.
Fixed
- Sending the initial data to a microcontroller with a transmit-ready signal activated (reset on connection) would lead to the data arriving before the reset was complete. I've added a 2-second delay before sending any data to combat this.
- Removed redraw events from the log window
Library
- Added connection variable. This is a public variable that can be reset from your code. This variable determines whether or not you're currently connected to the connector.
//If connected
connector.connected == 1
//If disconnected
connector.connected == 0
- A function was added to manually retrieve the last value of a given ID (must be in the current bundle).
// Force a resubmit by the connector of the last value of ID 100
connector.sendGetValueById(100);
Docs
- A contribution chapter was added, including an explanation of the output structure.
- Added a first draft of the output menu (this will be completed ASAP).
App v0.3.30
Connector
- Hotfix for the connector not connecting when missing setting value
The settings were optional in the front end but were being loaded into a stricter type. When a new setting is added to the connector, it tries to load nothing into the strict type, which results in a panic. I've added checks and balances to avoid similar bugs in the future.