v2.2.9-linux.4 — Community that says what's wrong, RenoDX kept current in your games

v2.2.9-linux.4 — Community that says what's wrong, RenoDX kept current in your games

What was wrong with Community and Chat

This release didn't break it, and neither did 2.2.9-linux.3: the community code is the same as upstream's. Run side by side against the server on 2026-10-07, 2.2.9-linux.2 and 2.2.9-linux.3 failed in exactly the same way.

The community service (5.rakanki.com) is run by the original project. Measured from a Linux PC that day:

• the connection opened in 12–16 ms;
• the server then took 16 s to send the chat, 31 s to send the game list, or never answered (45 s and 70 s waits);
• other requests came back 502 Bad Gateway through Cloudflare, which sits in front of it: most at about 30 s (game list 30.7 s, chat people 30.8 s), one at 12 s and one at 66 s.

The app waited 10 s, then said "Community service is unavailable. Check your connection and try again." It said this every time, even when the server was simply slow. Chat said "Start the conversation" when its messages had never loaded.

What's new

Community and Chat

• They wait for a slow server. A request now gets 35 s instead of 10 s, so a server that answers in 16–31 s gets through. Anything slower is reported as taking too long.

• They say what actually failed. There are three cases:

  • "The community server is taking too long to answer";
  • "The community server is having trouble right now (error 502)";
  • "check your connection", now used only when the server can't be reached at all.

  The first two add that the service is run by the original project and nothing on your PC needs fixing.

• They show what they last loaded. The last game list, GPU list and newest chat page are kept on your PC (community-last-good.json, up to 12 entries, a week at most).

  • When you open Community, the saved list appears at once, marked "Showing the results saved on …". Fresh results replace it when the server answers.
  • If the server fails, the saved list and messages stay on screen, with the reason.
  • Sending anything (reports, replies, messages) still needs the server.

• Chat shows its real state. It goes from "Loading messages…" to "The chat server is slow right now" after 8 s, then "Chat could not load" with the reason. It no longer shows an empty room. A line above saved messages says when they're from, and it clears when the server answers again.

• Every new message is in English and Arabic, the two languages these tabs carry.

RenoDX

• The newest builds. RenoDX DLSS5 8.5.0-rc10 and multipass SF 26.1003.2350, the newest on the project's release feed (RankFTW/rhi-repo) as of 2026-10-07.
• Games you already set up are brought up to date. About → Updates → RenoDX in your games lists each game's copy: current, older, newer, picked by you, or added by hand.
  • Update N games replaces only older builds this app put there, and only after you confirm with the game closed. Each new file is written beside the old one and SHA-256 checked before it takes its place.
  • These are left alone: a build added by hand, one picked on the Add-ons page, and one newer than the app's (no downgrades).
  • Restore still brings back each game's original files.
  • Builds you accept from the Updates panel are remembered, so a later release can bring those games forward too.
• The sidebar says "RenoDX is older in N games". This needs nothing from GitHub, so it shows even when GitHub can't be reached.
• New builds can't slip past the check. rhi-repo also mirrors NVIDIA's DLLs and Streamline, and a burst of those used to be able to push a new RenoDX off the 30 releases the check read.
  • The check now reads 100 releases.
  • It reads up to 4 pages when a RenoDX line isn't on the first page.
• The app keeps checking while it runs. It sits in the tray for days, and the add-on check kept in memory never expired, so a RenoDX released after start-up wasn't seen until a restart.
  • The check now expires after 6 h, or 30 min after a failed check.
  • The app looks again every hour.
• GitHub's hourly limit is reported in plain words. It allows 60 anonymous requests per connection. Instead of "GitHub answered 403", the panel now says the limit is used up and when it resets.

Add-ons page

• The built-in add-on is explained. The top of the page now reads: "Built in: RenoDX DLSS 5 8.5.0-rc10. It goes in with every RenoDX and Feeder install, so there is nothing to switch on for it."
  • It used to be listed as a nameless optional add-on with a switch. The app recognised builds only from a list last updated for RenoDX 4.7.
  • The app's own build is now recognised whatever it is, including one accepted from the Updates panel.
• Older RenoDX builds are named when you add them by hand. That covers 6.5.3 and multipass SF 26.0927, 26.0928 and 26.1003, which earlier releases shipped.

Verified

• Tests: npm test gives 391 tests, 389 pass, 0 fail, 2 skipped. 21 are new: 11 for Community and Chat, 10 for RenoDX in games.
• The app, run from source in an isolated home and config folder. It talked to a stand-in community server serving a real game-list answer from 5.rakanki.com, switched between three modes:
  • Answering: 24 games of 7,636, and chat messages.
  • 502 after one good load: the saved list (24 games) and saved chat stayed on screen, with "error 502" and the time they're from.
  • Never answering: the saved list showed at once with "Checking for newer results…", then the "taking too long" reason after 35 s.
  • First start with nothing saved, while the server was failing or not answering:
    • Community said it was slow after 9 s.
    • Chat went from "Loading messages…" (2 s) to "slow" (12 s) to "Chat could not load" (35 s).
    • Both recovered by themselves once the server answered again.
• RenoDX in games. The test used stand-in game folders: one with the real RenoDX 6.5.3, one with multipass SF 26.0928.0205, and one with a hand-made build.
  • Update 2 games replaced the first two with 8.5.0-rc10 (dcd93881…) and SF 26.1003.2350 (1310119c…).
  • The hand-made build stayed byte-identical, and no temporary files were left.
  • The sidebar read "RenoDX is older in 2 games" before the update.
• The Add-ons page showed the built-in line above, and no switch for the built-in build.

Good to know

• The community server isn't run by this fork. When it's down, these tabs now say so and show what they have. They can't make it answer.
• This is the first release that 2.2.9-linux.3 can install by itself (About → Updates). An rpm or deb install asks for your password through pkexec.
• Feeder, DLSS5VKLayer and OptiScaler still move with app releases. The panel shows their status and links to them.

File	SHA-256
DLSS5-Swapper-Linux-2.2.9-linux.4-x86_64.AppImage	4f0d1218940422d2d8f37f317061630fa7a3920e92b4af7e031efbedf679b2d9
DLSS5-Swapper-Linux-2.2.9-linux.4-amd64.deb	c73d26f9ac8bfe84e10e19b04924e1a5d0e1132ba31a7d927aec5098f1a16ff3
DLSS5-Swapper-Linux-2.2.9-linux.4-x86_64.rpm	a40d6af44e1582dc82deaaef676ceae91f4f45f0e79096640b9df329dd49804a