GAMMA Setup Tool

Native macOS tool for creating a Sikarugir .app wrapper around an existing S.T.A.L.K.E.R. G.A.M.M.A. installation.

GAMMA Setup Tool does not install G.A.M.M.A. itself. It expects G.A.M.M.A. to already be installed.

Flow Demonstration

Description

The tool auto-detects a stalker-gamma-cli installation and creates an .app wrapper that is ready to run. If you installed G.A.M.M.A. another way, you will be asked to select a folder that contains ModOrganizer.exe. Keep in mind that the tool does not perform any validation of the G.A.M.M.A. installation itself.

There are several options to tweak, but changing them is not required. You can just go through the flow with the defaults; that was the goal.

I have also tried to provide tips and additional info if you choose to change any default settings. Most of those notes are based on my personal experience running different X-Ray engine games on macOS, so your experience may vary. Feel free to correct anything that looks extremely stupid or plain wrong.

You can re-run the setup for an already-created wrapper as many times as you want. It is idempotent and will adjust the prefix according to your selected options. If you encounter problems or need help, ping me in the support thread. I am on and off Discord due to life stuff, but I will get back to you as soon as I can.

What It Does

The app reads your stalker-gamma-cli config and ModOrganizer.ini, then creates a native macOS app wrapper that launches G.A.M.M.A. through ModOrganizer.exe.

The guided flow handles:

• Environment checks for stalker-gamma-cli, Homebrew, Sikarugir, winetricks, Anomaly, GAMMA, and ModOrganizer files.
• Required winetricks dependencies.
• Wine prefix options + Optional fixes

How to Use

How to use

Use the latest GitHub release and download the app archive:

GAMMA.Setup.Tool.<version>.app.zip

Unzip it, then run:

GAMMA Setup Tool.app

macOS may require approving the app in System Settings because the release is not notarized.

Wine Display Resolution

The Display section is for choosing whether Wine should use its default display behavior or expose a specific resolution to Windows apps. This is mainly useful when using BetterDisplay or another HiDPI display mode where macOS may show a 1080p desktop while the backing pixel mode is larger.

The tool detects:

• the current macOS display mode, including HiDPI/backing resolution when available
• the current game resolution, read only for context, from the detected Anomaly path:

<anomalyPath>/appdata/user.ltx

anomalyPath is resolved from ModOrganizer.ini.

Forced is the default for new wrappers. It writes Wine's Retina mode and DPI settings so Wine presents the selected resolution as a plain Windows display.

Default Wine keeps the same Wine display behavior the wrapper used before this setting existed. If setup is re-run after using Forced, choosing Default Wine removes the Wine display keys managed by the setup tool.

For a BetterDisplay 1080p HiDPI desktop with the game also set to 1920 x 1080, use Forced with the detected 1920 x 1080 option.

The setup tool never writes user.ltx; change in-game resolution from the game itself.

For deeper technical notes on macOS scaling, Wine DPI behavior, and monitor geometry, see DPI awareness, monitor geometry.

Developer Notes

Build

Build the app:

swift build

Building from source requires Apple's Command Line Tools or Xcode.

SwiftPM writes build products under:

.build/

For UI iteration, build and immediately run the app target:

swift run GAMMASetupTool

Build artifacts, Swift module cache, and intermediates are kept under .build/ so repeat builds are faster. To remove them:

swift package clean

Source Layout

Swift GUI sources live in:

sources/GAMMASetupTool/

The app is split into:

• AppModel.swift: preflight state, setup execution, process streaming, and option serialization.
• Components.swift: reusable SwiftUI rows, tips, icons, and wizard step metadata.
• ContentView.swift: wizard layout and screens.
• GAMMASetupToolApp.swift: app entry point.
• sources/GAMMASetupCore/: shared setup engine models, path helpers, preflight logic, and installation services.
• sources/GAMMASetupEngine/: the setup backend launched by the GUI.

The Swift package builds both the GUI and the gamma-setup-engine backend.

Setup Engine Details

gamma-setup-engine performs these operations:

• Installs or verifies Homebrew tap sikarugir-app/sikarugir, Sikarugir Creator, and winetricks.
• Reads stalker-gamma-cli settings from ~/Library/Application Support/stalker-gamma/settings.json.
• Finds the active GAMMA profile and its ModOrganizer.exe.
• Reads <gammaPath>/ModOrganizer.ini to preserve the expected short Wine drive mapping.
• Creates a Sikarugir app wrapper.
• Downloads or reuses cached Sikarugir template and engine archives.
• Extracts the engine into the wrapper.
• Initializes the Sikarugir Wine prefix inside the wrapper.
• Enables D3DMetal by default, or DXMT/DXVK when selected.
• Keeps MoltenVK-CX, MSync, and ESync enabled.
• Applies mouse/raw-input compatibility overrides when selected, or restores Wine defaults when unchecked.
• Detects game resolution from <anomalyPath>/appdata/user.ltx for display context only.
• When a Wine display resolution is selected, writes Wine Retina/DPI compatibility settings.
• Sets the wrapper launch path to /mo2.bat.
• Creates a short Wine drive mapping for the detected macOS install location.
• Installs required Wine dependencies with winetricks: corefonts, vcrun2022, d3dcompiler_42, d3dcompiler_43, d3dcompiler_46, d3dcompiler_47, d3dx9, d3dx10, d3dx11_42, and d3dx11_43.
• Installs any extra winetricks verbs requested by the user.
• Applies DLL overrides for DirectX and Visual C++ runtime DLLs as native,builtin.
• Creates drive_c/mo2.bat, which sets ModOrganizer Qt rendering variables before starting ModOrganizer.exe.
• Marks the wrapper as managed by this tool.

Logs And Cache

Top-level setup logs are optional. Enable Save verbose log in the GUI to create a log in ~/:

gamma-setup-tool.YYYYMMDD-HHMMSS.log

Dry-run logs use:

gamma-setup-tool.dry-run.YYYYMMDD-HHMMSS.log

Logs are ignored by git.

Downloaded Sikarugir assets are cached in:

~/Library/Caches/stalker-gamma-sikarugir-setup

If Sikarugir Creator has already downloaded the template or engine, the setup engine reuses those local assets from:

~/Library/Application Support/Sikarugir

Generated build products, Swift module cache, and intermediate binaries are written to .build/, which is ignored by git.