OptiEditor

Caution

Close all games before editing an OptiScaler.ini file or replacing an OptiScaler DLL with OptiEditor. Editing settings or updating binaries while a game is running can corrupt the installation or crash the game.

OptiEditor is a Windows desktop utility for discovering, configuring, presetting, and locally updating existing OptiScaler installations.

Important

OptiEditor is an independent community project. It is not an official OptiScaler application and is not developed, distributed, or supported by the OptiScaler project.

The configuration editor currently supports OptiScaler 0.9.x and 0.10.x. The installed version family is detected from the OptiScaler binary FileVersion; users do not select the version manually.

Features

Installation discovery

• Add, remove, enable, and disable custom scan folders.
• Recursively search enabled folders for OptiScaler.ini.
• Automatically scan enabled folders when OptiEditor starts.
• Validate the OptiScaler proxy binary using Windows PE version metadata instead of trusting the filename alone.
• Detect supported proxy filenames in the same directory as OptiScaler.ini:
  • dxgi.dll
  • winmm.dll
  • version.dll
  • dbghelp.dll
  • d3d12.dll
  • wininet.dll
  • winhttp.dll
  • OptiScaler.asi
  • OptiScaler.dll
• Display the detected game name, executable, OptiScaler version, proxy filename, and installation folder.
• Search discovered installations, open their folders, copy INI paths, and rescan manually.
• Skip descending into reparse points (junctions or symlinks) while scanning to avoid infinite loops.

Version-aware configuration editor

• Separate setting schemas for OptiScaler 0.9.x and 0.10.x.
• Grouped controls for upscaling, frame generation, FSR, DLSS, overlay, image quality, shortcuts, output scaling, resolution, display, texture, and other supported settings.
• Dedicated controls for Auto/Enabled/Disabled values, enumerated options, numeric values, and shortcut keys.
• Shortcut key capture with editable raw values such as auto, -1, decimal virtual-key codes, and 0xNN.
• Show every setting defined in the installed version's schema, using its current OptiScaler.ini value when present or the setting's default when absent.
• Preserve unsupported or future values until the user explicitly changes them.
• Preserve comments, unknown lines, ordering, whitespace, encoding, BOM, and line endings.
• Detect external file changes before saving and refuse to overwrite a modified INI.
• Create a temporary OptiScaler.ini.optieditor.bak rollback copy during the INI replacement, removed automatically once the save succeeds.
• Revert individual settings, revert all changes, reload from disk, or reset supported Auto-capable settings to auto.
• Configure which editor settings are visible separately for OptiScaler 0.9 and 0.10.

Presets

• Built-in frame-pacing presets for both supported OptiScaler families.
• Create separate user presets for OptiScaler 0.9 and 0.10.
• Search, edit, duplicate, and delete user presets.
• Select a compatible discovered game and preview changes before applying a preset.
• Choose individual preset entries to apply.
• Apply preset values to the editor first; the INI is not written until Save is selected.
• Skip settings that are not present in the target INI.
• Preserve preset entries for settings hidden by the current Editor visibility configuration instead of dropping them when the preset is edited and re-saved.
• Report how many preset entries were skipped when applying a preset whose settings are hidden for the target installation.

OptiScaler Update

• Select a local OptiScaler binary as the replacement source.
• Accept a source file when its PE metadata identifies it as OptiScaler, contains a readable numeric version, and that version maps to a supported family (0.9.x or 0.10.x). Any other source, and any filename, is rejected.
• Display the source path, file version, product version, and file size.
• Select targets individually or by installed family: OptiScaler 0.9, OptiScaler 0.10, or All. Only the installations you actually selected are checked and updated.
• Search installations without clearing existing selections.
• Rescan selected installation directories immediately before replacement.
• Stage and verify the source with SHA-256 before modifying targets.
• Detect installation folders that contain more than one OptiScaler-identified proxy DLL and skip them instead of guessing which one to replace. The detected filenames are listed, and a single affected installation can be opened directly in Explorer for manual cleanup.
• Warn when a target's installed OptiScaler version family differs from the source's (0.9 ↔ 0.10) and require explicit confirmation before replacing it — once for a single target, or once for the whole batch when several differ. Declining cancels the entire run, not just the mismatched targets.
• Re-check each target's proxy DLL count and installed version family again immediately before writing to it, in case either changed after the checks above ran.
• Preserve each target's existing proxy filename. For example, a selected source named source.bin can replace an installed dxgi.dll while the final filename remains dxgi.dll.
• Process each installation independently so one failure does not stop the remaining targets.
• Skip locked files and report access, validation, and replacement failures per installation.
• Automatically restore the previous binary if a replacement cannot be verified after it is written.
• Rescan affected installations after replacement and refresh the shared installation catalog.

Warning

OptiScaler Update does not keep a persistent backup of the binary it replaces. Close the game before replacement. A replacement that fails verification is rolled back automatically, but once a replacement is reported successful, the previous file is gone for good.

OptiScaler Update permits upgrades, downgrades, and equal-version replacement within the same version family without a warning. Replacing across the 0.9 and 0.10 families is also permitted, but only after explicit confirmation, since OptiEditor does not migrate OptiScaler.ini between families — review your settings after a cross-family replacement. It replaces only the detected primary OptiScaler proxy binary and does not modify OptiScaler.ini or auxiliary libraries. Installations with multiple OptiScaler proxy DLLs are never auto-resolved; they must be cleaned up manually and rescanned before they can be updated.

OptiEditor updates

• Check for OptiEditor updates at application startup through Velopack.
• Automatically download, apply, and restart when an update is available.
• Continue opening the currently installed version if the update check fails.

Requirements

• Windows 10 version 1809, build 17763 or later, or Windows 11
• x64 Windows
• One or more existing OptiScaler installations to scan and edit

Installation

1. Open the OptiEditor Releases page.
2. Download and run the latest Velopack Setup executable.
3. Start OptiEditor and add the folders that contain your game installations.

Note

OptiEditor requires Windows App Runtime 2.3.1 x64, which is already installed on many Windows systems. If OptiEditor does not start, install it from the Microsoft Windows App SDK download page and try again.

The Setup package handles the required .NET Desktop Runtime. Windows App Runtime is not installed automatically by OptiEditor.

Basic usage

1. Open Folders and select Add Folder.
2. Enable the folders to scan and select Save Changes.
3. Select Scan Now, or restart OptiEditor to run the automatic startup scan.
4. Open Games and select Edit Settings for a detected installation.
5. Review changes and select Save to update OptiScaler.ini.
6. Use Presets to create reusable partial configurations or apply a built-in preset.
7. Use OptiScaler Update only when you intentionally want to replace installed OptiScaler proxy binaries.

Discovery rules

An installation is listed only when:

• OptiScaler.ini exists in the scanned directory.
• A supported proxy filename exists in that same directory.
• The proxy file's PE metadata identifies it as OptiScaler.
• Its numeric FileVersion maps to a supported editor family: 0.9.x or 0.10.x.

OptiEditor does not infer the version from the INI contents, directory name, or proxy filename. If multiple verified proxy binaries report conflicting versions, the installation is excluded from discovery until the conflict is resolved. OptiScaler Update applies its own, more specific check for this case: see OptiScaler Update.

Local data

OptiEditor stores its own configuration under:

%LocalAppData%\OptiEditor\

This includes scan folders, editor visibility settings, user presets, logs, and temporary update staging data. The current installation list is rebuilt from disk scans rather than treated as a permanent installation database.

Development

OptiEditor is built with:

• C# and .NET 10
• WinUI 3 / Windows App SDK
• CommunityToolkit.Mvvm
• Velopack

Build the solution for x64:

dotnet restore OptiEditor.sln
dotnet build OptiEditor.sln --configuration Release -p:Platform=x64

Run the Core test suite:

dotnet test tests/OptiEditor.Core.Tests/OptiEditor.Core.Tests.csproj --configuration Release

Important notes

• OptiEditor does not download or bundle OptiScaler binaries.
• OptiEditor does not migrate an INI between OptiScaler version families.
• Installing an unsupported future OptiScaler version may make that installation unavailable in the current editor until support is added.
• Always review changes before saving or replacing files.