Skip to content

v0.11.0 — your modified games, grouped and version-checked

Choose a tag to compare

View all tags
@faisalkindi faisalkindi released this 04 Sep 08:16
· 6 commits to main since this release
v0.11.0
02e386f

Every game you have modified, in one place at the top — and a badge when it needs updating

The Games page now opens with an Installed by this tool section: every game this tool has set up, together, ahead of the store sections and no longer duplicated inside them. So the first thing you see is what you have modified.

A card whose files have fallen behind upstream gets an UPDATE badge, the section header counts them (3 need updating), and hovering names each one:

Out of date:
  OptiScaler v0.1.2-dlssnr → v0.2.0-dlssnr
  DLSS5-Feeder v0.12.0 → v0.13.1-beta.1

Only a component this tool placed and recorded is ever reported, so your own ReShade or a RenoDX mod you installed by hand can never show up as "out of date".

The bug this uncovered: OptiScaler was never being updated

step_opti returned early whenever OptiScaler was present, so a game set up weeks ago kept running that build through every reinstall. On my own machine four games were on 25,712,640 and 25,782,784-byte builds while v0.2.0 ships 25,872,384.

  • The OptiScaler manifest now records its release tag, and an install refreshes a copy this tool placed once upstream moves on.
  • A manifest with no tag — written before this version — is still recognised as ours: it is refreshed once and gains its tag. A folder with no manifest is somebody else's OptiScaler and is never touched.
  • DLSS5-Feeder gains the same kind of version marker.

If you have games set up from an earlier version, they will show OptiScaler unknown version → v0.2.0-dlssnr until you run Install once, which is exactly what it looks like: the version on disk cannot be known, and one install settles it.

dlss5oneclick.exe "<game folder>" --check prints the same list without opening the window.

Assets 3
Loading