Repository navigation
Fenix 0.1.6 makes patch updates in Flightdeck recoverable. A failed update no longer leaves Fenix unusable.
- Failed updates keep the installed patch. Nothing of an update takes effect before its final step. If an update fails, the installer immediately reinstates the verified installed patch and removes the unused staging copy. Fenix keeps working and Update patch can simply run again. Before, every later action required Restore, which goes back to the profile from before the first patch.
- Stuck installations are recovered. Installations left unfinished by earlier versions are recovered by the next update, settings or Fenix action. The setup shows the installed patch again. A changed or partly published transaction is still kept for Restore.
- Unconfigured profiles update cleanly. Updates no longer write Fenix display settings into profiles that are not configured yet. This could stop the update when the settings folder was missing.
- Less disk use. The profile copy taken before each completed update is removed, because Restore never uses it. A copy left by an interrupted commit is kept.
Flightdeck 0.3.11 ships the same recovery for its own setup and installs this release automatically before the next Fenix or MSFS start. The Steam setup updates in place and was not affected. Wine and DXVK payloads are unchanged from 0.1.5; only the runtime helper was rebuilt.