Skip to content

Installation and Prerequisites

Jump to bottom
g95237-del edited this page Jul 21, 2026 · 1 revision

Installation And Prerequisites

Running A Built Release

  • Windows 10 or later, x64.
  • .NET 8 Desktop Runtime unless the release is explicitly marked self-contained.
  • A DXGI-compatible graphics adapter and output.
  • EDI when testing or using exported scripts.

The game window must be visible and non-minimized. Borderless and ordinary windowed modes are the intended capture modes. Exclusive fullscreen, protected content, HDR/10-bit output, rotated displays, and monitor changes are unsupported or require restarting capture.

Building The Studio

Install the .NET 8 SDK, then run from the repository root:

dotnet restore GTracker.slnx
dotnet build GTracker.slnx --configuration Release
dotnet test GTracker.slnx --configuration Release
dotnet run --project src\GTracker.App\GTracker.App.csproj --configuration Release

Generated plugins may require an older .NET Framework targeting pack selected from the inspected Unity player. Mono .NET 3.5 players are detected but are not supported by the current generated HTTP client.

EDI

The default API URL is:

http://127.0.0.1:5000/Edi

Use a standalone, known-compatible EDI folder containing Edi.exe. The Studio can merge it beside a game while preserving the destination Gallery folder. It does not verify EDI's version or freshness.

The URL field is embedded into Plugin.cs during initial scaffold generation and is not stored in the Studio project. Changing the field later does not update an existing generated plugin.

Close EDI and the game before installation. Source/destination nesting and reparse points are rejected.

BepInEx

The Studio includes BepInEx 6 nightly be.785 packages for:

  • Unity Mono x64.
  • Unity IL2CPP x64.

Automatic provisioning supports x64 games only. It verifies the packaged archive hash, installs the runtime-matching package, launches the game, waits for initialization, and closes the game. Initialization requires disk logging with the Message level and reports an error if an existing BepInEx.cfg disables it. IL2CPP initialization can take substantially longer because interop assemblies must be generated.

Existing BepInEx 5 Mono installations can be inspected and used by generated projects, but the packaged automatic installer installs BepInEx 6.

EDI Integration Studio

Clone this wiki locally