Upscaled

A minecraft mod that adds Temporal Upscaling to minecraft

File Details

Upscaled NeoForge v0.1.0-alpha-4 for 26.2

  • R
  • Jul 13, 2026
  • 30.98 MB
  • 8
  • 26.2
  • NeoForge

File Name

upscaled-neoforge-0.1.0+26.2-alpha-4.jar

Supported Versions

  • 26.2

Curse Maven Snippet

NeoForge

implementation "curse.maven:upscaled-1608701:8424421"
Curse Maven does not yet support mods that have disabled 3rd party sharing

Learn more about Curse Maven

Upscaled 0.1.0+26.2-alpha-4

A platform release: Upscaled now runs on NeoForge as well as Fabric, and a dependency bug that could crash the Fabric version on minimal installations is fixed.

The mod has been restructured so that all upscaling code is shared between loaders; only a thin shim per loader differs. Pick the jar that matches your loader — the feature set is identical on both.

What's new

  • NeoForge support. A separate upscaled-neoforge jar runs on NeoForge (26.2 beta line, built against NeoForge 26.2.0.12-beta). Same features, same options, same config/upscaled.json, same bundled natives — DLSS and FSR 3 both work identically on either loader.
    • Known NeoForge issue: NeoForge's early loading screen creates the game window in OpenGL mode, which the experimental Vulkan renderer cannot use (GLFW error 65540 at startup). Until NeoForge addresses this, set earlyWindowControl = false in config/fml.toml.
  • Sodium settings integration on both loaders. The Upscaled tab in Sodium's video settings screen (added in alpha 1) now registers on NeoForge as well, through the same official Sodium Config API. Sodium remains optional on both loaders: without it, the options stay in the vanilla Options → Video Settings → Upscaled section.
  • Fabric API is now a declared dependency (Fabric version). Earlier alphas silently relied on Fabric API for asset loading and for access to a renderer internal: without it installed, options showed as raw translation keys and enabling upscaling crashed the game. The renderer access is now self-contained via the mod's own access widener, and the remaining requirement (fabric-resource-loader-v0) is declared properly, so the loader reports a clear error instead of crashing mid-render. NeoForge has no such dependency: the upscaled-neoforge jar is standalone.
  • Internal: multiloader project layout (common + fabric + neoforge). No user-facing changes on Fabric beyond the dependency fix.