Skip to content

Releases: SpecterArdy/VRCFaceTracking2

VRCFaceTracking Rebuild

16 Apr 00:38
@SpecterArdy SpecterArdy
2025.1
c263340

Choose a tag to compare

View all tags
VRCFaceTracking Rebuild Latest
Latest

Because who needs expired certs, broken installs, and Windows yelling at you when you just want your face to move?
This version skips .msix entirely because, let’s be real — nobody actually likes .msix.

Because who needs expired certs, broken installs, and Windows throwing tantrums when you just want your face to move?

This version ditches .msix entirely — because let’s be honest, nobody actually likes .msix.

▶️ Requires:
• .NET Desktop Runtime 9.0.4
• .NET Runtime 9.0.4

Why .msix Sucks for Most Real-World Users

  1. Certificate Drama
    .msix requires a valid code-signing certificate. If it’s self-signed or expired? Boom — instant install failure.

Users have to manually trust certs, deal with confusing errors like 0x80073CF0, or enable developer mode — none of which feels user-friendly.

  1. Windows Store-Centric Format
    It was designed for Microsoft Store deployment, not real-world GitHub/Itch.io/etc. distribution.

99% of users aren’t using sideloading and don’t want to mess with App Installer prompts.

  1. Strict Requirements
    Needs a manifest, AppX-compliant structure, and signed packages.

Doesn’t tolerate “loose” packaging. Missing one file or manifest typo = install dead in the water.

  1. Poor Compatibility
    .msix packages can’t be installed easily on older versions of Windows, or on stripped-down builds.

They’re also less portable than .msi or .zip — you can’t just drag/drop the app somewhere.

  1. No Benefit for Desktop-Only Tools
    If your app isn't using sandboxing, Store APIs, or UWP stuff — there's literally no gain using .msix over .msi or .exe.

It doesn’t reduce download size, make it easier to install, or improve UX in any meaningful way.

🤔 Why the Original Dev Might Have Used .msix
They probably used Visual Studio’s “Publish” wizard, which defaults to .msix when targeting UWP or WinUI.

It’s a “modern” packaging format that sounds good on paper (sandboxing, clean uninstalls, versioned deployment).

They may have intended future Microsoft Store submission, even if they never finished the pipeline.

Why .msi, .exe, or .zip is Better for Most Devs
No cert required (unless you want one).

Easily scripted with silent install options.

Works across Windows versions.

Devs can use tools like WiX Toolset, NSIS, Inno Setup, or even plain zips for full control.

More flexible and trusted by users who aren’t trying to run a corporate app store.

Full Changelog: https://github.com/SpecterArdy/VRCFaceTracking2/commits/2025.1

Assets 3
Loading