Skip to content

Releases

Fenix 0.1.6

Choose a tag to compare

@marselnenaj marselnenaj released this 13 Nov 21:07

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.

Fenix 0.1.5

Choose a tag to compare

@marselnenaj marselnenaj released this 08 Nov 18:02

Fenix 0.1.5 adds verified Proton repair for standalone Steam installations and protects overlay files against write-through access via Proton's Windows-profile links.

  • Repair Fenix Proton is available in browser setup, terminal setup and the CLI (./install.sh repair --steam msfs2024; use msfs2020 for MSFS 2020).
  • Repair validates the unchanged Wine build, stages and verifies the replacement, switches it atomically and keeps the old tool as a backup. Aircraft, sign-in, Windows profile and original restore point are retained. Known earlier patch versions then follow the normal update path.
  • Shared MSFS 2020/2024 tools are locked together, with idle checks before replacement.
  • Checksum errors include the path and expected/actual hashes and wrap correctly on mobile.
  • Preserve the exact 0.1.4 upgrade metadata for all four supported overlays. Wine/DXVK payloads are unchanged; the installer and native runtime helper are rebuilt for 0.1.5.

Close MSFS and Fenix for every simulator sharing the tool, extract the linux-x86_64.zip, run install.sh and choose Repair Fenix Proton if an existing tool reports changed overlay files. The .fenix-repair-* backup is retained under Steam's compatibilitytools.d.

Validation: 149 tests passed (3 existing opt-in tests ignored), rustfmt and Clippy passed; browser repair was exercised at desktop and mobile sizes against injected corruption in the published CachyOS 11 overlay. A Windows certificate-query control started through the repaired runner with all 27 runner hashes unchanged. The exact causes of issue #21's reports and its full-simulator startup failure remain unverified.

The source archive contains the complete corresponding project and upstream sources. SHA256SUMS covers both downloads; Flightdeck metadata is provided for compatible independent patch updates. Flightdeck's embedded installer code is updated with Flightdeck releases.

Fenix 0.1.4 — security and manifest consistency

Choose a tag to compare

@marselnenaj marselnenaj released this 30 Oct 12:08
9827e0d

Security maintenance and runtime manifest consistency for the standalone Steam installer and Flightdeck integration.

  • Include patched ZIP, rustls and certificate-verification dependencies.
  • Keep runtime-helper destination hashes identical to the actual integration payload. Refuse inconsistent root/variant metadata before building a release.
  • Retain prior upgrade/restore identities and existing Wine/DXVK/Windows payloads.

This supersedes 0.1.3, withdrawn from stable updates after its stale prefix-helper checksum was caught in Flightdeck's real archive upgrade test. Use 0.1.4.

Requires Flightdeck 0.3.5 or newer; installer contract 2 remains unchanged. No new full-flight or FenixSystem memory qualification is claimed.

Validation: all four PR CI jobs, Rust 1.98 workspace tests, static installer validation and strict Clippy/fmt pass. The exact candidate ZIP upgrades all four supported runners through Flightdeck in disposable profiles while retaining original runner files and add-on sentinels. All five final-main assets are byte-identical to that candidate. Complete corresponding sources and notices included.

If you manually tried the withdrawn 0.1.3 installer and it reports a changed Fenix dependency, use Restore original profile before installing 0.1.4. Restoration retains the replaced profile separately. Direct upgrade validation covers the preceding stable 0.1.2 release; an automatic migration from inconsistent 0.1.3 prefix metadata is not claimed.

Fenix A320 Linux Patch 0.1.2 — CLR loader repair

Choose a tag to compare

@marselnenaj marselnenaj released this 29 Oct 17:00
31b6320
  • Preserve native CLR priority with mscoree=native,builtin, including after
    the Microsoft Framework installer finishes. Existing native-only settings
    are backed up and repaired before setup, staged upgrade and Fenix app startup.
  • Keep disabled/builtin preferences, per-app overrides and DLL files intact.
    Add idempotent migration, backup failure and ambiguous-registry regressions.
  • Retain the Wine/DXVK and Windows payloads from 0.1.1 and its exact upgrade
    identities for all four runners. Rebuild the Rust installer/runtime programs.
  • Require Flightdeck 0.3.5 for the matching launcher-side repair. Standalone
    Steam setup remains available independently.
  • Reproduce and repair the IL-only loader failure using Microsoft's verified
    .NET 8.0.33 assembly in an account-free profile. This is not
    a new full-flight, GPU or System-memory qualification.

Flightdeck users: update to Flightdeck 0.3.5 for the paired launcher-side loader repair. Standalone Steam setup uses this installer directly.

0.1.1 — linked Wine fonts

Choose a tag to compare

@marselnenaj marselnenaj released this 25 Oct 22:17

0.1.1 — linked Wine fonts, 25 October 2026

  • Fix Expected a regular file: tahoma.ttf when a Wine profile or runner uses
    font symlinks. Copy readable linked font contents into the selected profile
    atomically; repair broken profile links from the runner. Preserve shared
    source fonts, existing ordinary/custom fonts and 64-bit font registration.
  • Keep font-directory containment and bounded ordinary-file reads. Add
    regressions for shared, runner and broken font links and parent escapes.
  • Retain the exact Wine/DXVK and Windows helper payloads from 0.1.0. Preserve
    0.1.0 snapshots for upgrades on all four runners.
  • After an interrupted setup, use Restore original profile, then retry with
    the new installer. Flightdeck users need its corresponding launcher font fix.

Fenix A320 Linux Patch 0.1.0

Choose a tag to compare

@marselnenaj marselnenaj released this 24 Oct 22:03

0.1.0 — first regular release

  • Replace the remaining Linux Python launch and display helpers with the
    statically linked fenix-runtime Rust program. Keep inherited licensed image
    descriptors, temporary view cleanup, process ownership checks, bounded
    refresh attempts and durable display-preference recovery.
  • Replace the optional memory sampler and the CI source-archive extraction
    with Rust maintainer commands. No Python runtime is needed by the patch's
    installer or Linux helpers; upstream Wine build tools remain separate.
  • Retain every Wine/DXVK module and Windows helper from preview.11. Preserve
    exact preview.11 snapshots for upgrades on all four pinned runners.
  • Require Flightdeck 0.2.22 for installer contract 2 and the native helper
    layout. Steam setup remains self-contained; earlier Flightdeck versions
    require a launcher update before adopting this patch.
  • Keep the published scope experimental: FenixSystem memory growth (#12),
    full-flight Fenix v3 stability and the earlier Wine assertion are unresolved.
    A regular release does not establish new simulator or GPU qualification.

See release scope and checks.

Download the Linux installer ZIP for installation. The source archive contains corresponding sources and notices, without the compiled Wine payload.

Fenix A320 Linux Patch 0.1.0-preview.11

Pre-release

Choose a tag to compare

@marselnenaj marselnenaj released this 23 Oct 16:10

0.1.0-preview.11 — experimental, 23 October 2026

  • Include @malik05051's PR #15:
    add Fenix.GqlGateway.exe to the existing loader-name allowlist. Rebuild
    matching x64 PE NTDLL for all four runners and repin the tested payloads.
    The reporter confirms Gateway logging, port 8083 and a working EFB on
    Fenix 3.0.0.7454 / Steam MSFS 2020 / CachyOS 11 / NVIDIA-PRIME.

  • Document working GPU displays on that setup with USE DISPLAY SAFE MODE
    off
    . This setting creates two devices instead of thirteen in the supplied
    comparison. CPU mode remains available; no new graphics override is forced.

  • Preserve existing Fenix loader behavior and unrelated executable names.
    All 64 own-code baseline/candidate name comparisons pass across four
    runners. Smoke now checks Gateway names and negative near-matches.

  • Explicitly select server synchronization for Fenix: PROTON_NO_NTSYNC=1
    for pinned Wine 11 and WINE_DISABLE_FAST_SYNC=1 for CachyOS 10. Steam
    updates retain other Python settings while adding these switches; the
    standalone application's environment and legacy launch script agree.
    Synchronization alone did not fix #7; the Gateway correction is the separate
    loader-name change above.

  • Retain exact preview.10 snapshots for upgrades; native overlay modules
    except for the four rebuilt PE NTDLL files; runner pins stay unchanged.

  • Rewrite English/German READMEs around setup, evidence, restore and
    troubleshooting. Add an own-code graphics-initialization diagnostic and
    document the corrected #7 findings and remaining #12 work. The earlier
    OutputReport-size estimate is withdrawn; certificate-related accumulation
    is the main qualified System-memory lead. No System-memory fix is claimed.

See release readiness and the
Display/Gateway investigation. The published download
is preview.11; this section does not announce a regular release.

Close MSFS and Fenix before updating. Steam users can extract this release and choose Update patch. Flightdeck integration is included in 0.2.19; an existing Flightdeck installation needs that launcher update.

Fenix v3 full-flight stability, the earlier Wine assertion and the separate Fenix 2 System-memory issue #12 remain open. This is an experimental prerelease.

0.1.0-preview.10 (experimental Fenix v3)

Choose a tag to compare

@marselnenaj marselnenaj released this 23 Oct 07:52

0.1.0-preview.10 — experimental, 23 October 2026

This test release reaches user-confirmed cockpit displays with Fenix
3.0.0.7454, official Installer 1.0.359, MSFS 2024 1.8.16.0 and
Xodus 11.0 / 7c0b4354. Known issue: one startup hit Wine's
create_view assertion after System boot. A later fresh production run and
five warm backend restarts did not reproduce it; its cause remains unknown.
No full flight or MSFS 2020/GE regression check has been completed.
See the test sequence and limits.

  • Return the native no-package error from WinRT ApplicationData.Current
    for ordinary desktop processes. The new installer's existing SQLite
    fallback then works, and the official aircraft installation completes.
  • Implement a bounded SHA1/SHA256 PE indirect-data route for
    CryptSIPCreateIndirectData, replacing the startup stub. Complete native
    SIP representation and certificate trust conformance are not established.
  • Reopen GLOBALROOT aliases through their actual volume mapping, preserve
    separator counts, and store a rooted current directory. This clears the
    brief invalid-name failure and later engine/content-root lookup failures.
  • Map the missing PBKDF2 pseudo-handle to Wine's existing implementation.
  • Support unnamed ephemeral NCrypt ECDH_P256 keys with scoped BCrypt
    parameter validation, provider lifetime and HASH/raw derivation handling.
    Other curves, named keys and the full CNG API remain outside this change.
  • Include matching builds and independent native controls for all four
    pinned runners. Real v3 cockpit checks cover Xodus only. Verified preview.9
    installations can update without reinstalling the aircraft or resetting
    renderer preferences and the original restore point.

The vendor executables and their authentication remain unchanged. Diagnostic
memory logging, APC and KernelBase experiments are excluded from the payload.
The issue and draft PR remain open for stability investigation. Flightdeck's
separate patch pin is not updated by publishing this experimental release.

Source and discussion: #11

Known issue and test feedback: #7

0.1.0-preview.9 — geometry lifetime and Fenix v3 runtime

Choose a tag to compare

@marselnenaj marselnenaj released this 22 Oct 17:40
  • All four overlays free Direct2D figure vertex types, backporting Wine
    4ae80e26e5 from M3rocto's PR #10. This fixes the per-geometry leak
    reported in issue #8; long-flight process memory behaviour remains unvalidated.
  • Nearly coincident Bézier control triangles have a subdivision limit;
    non-finite areas and invalid line-intersection parameters are rejected.
    The new stress test also found two cyclic triangulation walks, which now
    return an error through the normal cleanup path. Only d2d1.dll changes in
    each Wine overlay. These failures reproduce with synthetic paths; they are
    not a confirmed cause or fix for displays freezing in the simulator. See
    geometry lifetime and termination
    for the reproducible checks and the absolute path-unit tolerance.
  • The standalone installer prepares the pinned Microsoft .NET 10.0.13 x64
    Desktop Runtime, required by the Fenix v3 installer (issue #7), alongside
    .NET Framework 4.8. The runtime is also prepared when updating an existing
    Steam installation and checked before opening an official Fenix application;
    an incomplete installation prevents that launch. Downloads are checksum-verified and not included
    in the release. Runtime installation, host discovery and an own-code WPF
    window were checked in a separate CachyOS 11 profile; an actual v3 flight
    remains unvalidated.
  • Setup explicitly asks to sign in and install the A320 for the selected
    simulator inside the official installer, wait for aircraft installation to
    finish, then close it (issue #6).
  • Verified preview.8 installations are recognized as update sources. Existing
    aircraft, renderer preferences, sign-in and the original restore point are
    retained by the existing update flow.

0.1.0-preview.8 — GPU displays

Pre-release

Choose a tag to compare

@marselnenaj marselnenaj released this 20 Oct 18:22

0.1.0-preview.8 — 20 October 2026

  • Preview.8 adds GPU display transport for the pinned Xodus and Proton 11
    overlays. Wine records the shared texture's real adapter, and DXGI implements
    the owner query that previously returned E_NOTIMPL. Proton 11 also shares
    virtual fence state safely between processes instead of dereferencing a
    foreign pointer or returning physical Vulkan ticks.

  • Each GPU overlay carries fourteen matching Wine modules and DXGI built from
    its own runner's exact DXVK revision. D3D11 and VKD3D are retained. Complete
    source archives, recursive submodule pins and the DXVK licence are included.
    CachyOS Proton 10 retains the CPU path.

  • Existing automatic CPU settings migrate to GPU on capable overlays.
    configure --renderer cpu|gpu records a persistent preference, retained
    across later configuration and upgrades. Older and CPU-only variants cannot
    inherit or force-enable GPU support. Native DXGI is updated in an existing
    Windows profile as well as in the runner.

  • The Xodus GPU path has been checked in a running Fenix cockpit and with a
    controlled moving airspeed tape. Own-code resource and fence tests also cover
    multiple GPUs, separate processes, pixel transfer, handle lifetime and
    Proton 11's virtual values. Full flights, NVIDIA and GPU weather radar remain
    unvalidated. See GPU displays for the precise scope.

  • The guided setup shows what a running step has finished, what it is doing
    now and for how long: an activity bar, the completed sub-steps and the
    elapsed time, instead of only the latest message. How long the rest takes is
    not known, so the bar shows activity, not a percentage.

Download the Linux installer ZIP below and run ./install.sh. Existing supported installations update in place; configure --renderer cpu keeps a persistent CPU fallback. Current Flightdeck launchers need a Flightdeck update containing the new integration and pins.