RuneScape: Dragonwilds Performance & Controls

The most detailed performance walkthrough in the sources behind this page is a video by Kephren, published on 15 April 2025, titled "RuneScape Dragonwilds - Best PC Settings to BOOST FPS & Visibility Instantly". It works through four layers in a fixed order: Windows 11, then the NVIDIA or AMD control panel, then the game’s own graphics menu, and finally a configuration file where he says you "unlock your FPS and more graphics settings". He presents the whole thing as his own setup rather than as guidance from Jagex or from a hardware vendor.

The date deserves attention. April 2025 is seventeen months before 1.0, before the game had console versions, and before the Fellhollow update that most of the stutter reports further down this page are about. Treat each item as something to test on your own machine rather than a documented fix.

He starts with Windows 11 on the argument that you should free resources the game cannot use, then changes these settings:

After Windows he works through the graphics driver’s own controls. On NVIDIA that means the app overlay, one 3D setting, the power mode, the shader cache and finally the display configuration:

• NVIDIA overlay — off. He says it can cause stuttering and costs frames.
• Low Latency Mode — On.
• Power management mode — Normal. He reports better boost clocks than Maximum performance, which is the same conclusion he reached for the Windows power plan.
• Shader cache size — raised from the 4 GB driver default. He suggests starting at 10 GB and going to 100 GB if there is disk space, and calls the change a "game changer" for stutter because the game recompiles shaders less often.
• Resolution and refresh rate — the monitor’s native resolution and its real refresh rate. He notes that panels often sit at 60 Hz until the value is changed manually.
• G-Sync — optional, and off in his own setup. He unlocks his frame rate deliberately to hold input lag down, and says to turn G-Sync on if screen tearing bothers you.
• GPU overclock — pointed at as a separate video rather than demonstrated here. He says his own overclock gives him 12% more FPS.

The AMD route is different, and two of his recommendations there are things to avoid rather than things to enable:

• FreeSync — on, where the monitor supports it, so the GPU and the panel stay synchronised.
• Game profile — a custom profile rather than one of the presets, with the discrete GPU selected by hand. He flags this as a trap on laptops and on desktops that also have integrated graphics.
• FSR 4 — forced on where the card supports it, including in games that ship with FSR 3.
• Fluid Motion Frames — an option for games that have no FSR and no frame generation. He puts the gain at around 30%, warns that it adds input lag, and says not to use it for competitive games.
• Anti-Lag — advised against outright.
• Radeon Boost — also advised against.
• Radeon Chill — his recommended way to cap frame rate. Take the monitor’s refresh rate, subtract three and lock there: his 170 Hz panel becomes 167, and a 240 Hz panel becomes 237. The point is to stay inside the FreeSync range.
• GPU utilisation — he argues for holding the GPU around 97–98% rather than 100%, because a saturated GPU costs input lag, and notes that on some games the cap has to go lower to get there.
• Image Sharpening — 60 to 70% for games with no in-game sharpness slider and no FSR.
• Shader cache reset — the last resort for unexplained random stutter. The game rebuilds its shaders on the next launch, which takes time, and he compares the symptom to the reports he has seen in other games.

When he opens the game’s own settings, the first thing he notes is how little is there: "currently you don’t have any graphic parameters. So, you pretty much have basic stuff and the upscaling technique." That is the reason the video ends in a configuration file rather than in the menu — the fine-grained values he recommends later are not exposed in the interface he is recording.

What he does change in the menu:

The last stage of the video is a file edit, because the values he wants are not in the menu. He gives the path out loud, and warns that you will need hidden files visible to find it:

The block he points at is the one holding the individual graphics parameters. His recommended values, in the order he reads them out:

The trick he attaches to the edit is making the file read-only once it is saved. His reasoning is that the game overwrites the file when you change a setting in the menu, and pushes a fresh one with updates, so anything you hand-tune is liable to disappear. He also says the opposite move is needed eventually: after a patch that ships new graphics settings, remove the read-only flag and pick up the new defaults.

The clearest performance evidence in the sources behind this page is not a benchmark. It is a support thread on r/RSDragonwilds titled "How’s your game performance after the update?", and it is useful because Jagex staff replied inside it. The opening post describes the problem the whole thread circles: "My game is stuttering really badly after the update… I don’t think it’s a problem with my PC because it was running smoothly before, and also changing the graphics all the way down to Low makes no discernible change in performance from my previous settings."

Comment timestamps in the cached thread read as nine months old on the day the page was retrieved, which places the discussion in December 2025 — the window of the Fellhollow update. Two Jagex moderators worked the thread, and their replies are the only official performance guidance in any source used here.

One player had already narrowed it down before the moderators answered, and their reasoning matches what Jagex later said: "it only happens when playing in a player-created (hosted) world. Public worlds run smoothly, and the issue follows the specific world/server save rather than my connection or client." The same player added that they had to start a new world to escape it — which is exactly what the Technical Director went on to recommend as a test.

The rest of the thread is a stack of individual reports. They are worth reading for the pattern rather than for the numbers, because none of them was measured under controlled conditions and each is one person’s machine:

A second thread on the Steam forums, posted on 15 February 2026 and titled simply "Performance", carries the same shape. Its opening post reads: "Constant stutters on a HIGH END PC. Meanwhile my wife with a mid range PC runs it perfectly fine. The lower I drop my settings, the worse the game runs. This makes so much sense." That is a separate player, on a separate date, reporting the same inversion.

Controller support is the part of this page with the widest gap between how much Jagex has said and how little is actually written down. The storefront position is unambiguous: the Steam listing for app 1374490 carries Partial Controller Support among its categories, alongside Single-player, Multi-player, Co-op, Online Co-op and Steam Cloud. "Partial" is Valve’s own category name, and no source used here explains which parts of the game still want a keyboard, so read the label as the storefront’s wording rather than a breakdown.

Jagex has been unusually candid about why controller support was hard. Rick Turek, the game’s creative director, told Variety in an interview published on 7 July 2026 that the port itself was the easy part:

• "The development’s been straightforward, but there’s a lot of work that we have to do on the UX, the user experience, because while we’ve been developing with controller in mind, there is an expectation from a console player around the experience on a controller."
• He argued there was no clear model to copy: "There isn’t, I don’t believe, a best-in-class survival game on a controller that has really nailed it with the types of features." He held up Minecraft as the counter-example — "quite simple, in terms of its control features" — and called Dragonwilds "quite an interface-heavy game" by comparison.
• "As soon as you start putting that on controller, a lot of the work has been less about trying to do the port to console, because we have Unreal — it’s more been about the user experience and how we make the controller feel great."

Robert Galassi-Fox, a Jagex product director, gave Variety the player-side reason in the same interview, saying early research asked how many people preferred playing on controller sticks and that the answer "is not a small amount of people", which is why the team was "being quite specific… about it feeling good on the controller first" as early as Alpha.

The official channel’s own retrospective, published on 14 September 2026, lists controller work among the improvements shipped during early access: "We’ve improved controller support, made movement and jumping more responsive, and continued refining combat to give you greater control in every fight."

What none of that gives you is a button map. The only control-specific details in any source used here are hands-on reports from players on and around launch day, and they are worth reading as a warning rather than a reference:

This is the part of the page where the storefront and the patch notes overlap with the settings discussion, because platform capability is what decides who you can play with and what carries over. The Steam listing is the most concrete source available, since it is machine-readable rather than prose:

Crossplay is the headline capability, and it comes from Jagex directly. The official channel’s retrospective, published 14 September 2026, states it in the plainest terms: "The complete 1.0 experience, including everything we’ve delivered throughout early access, will be available on PlayStation 5, Xbox, Nintendo Switch 2, and of course on PC. With cross-play available across all platforms, adventurers can explore, build and battle together wherever they choose to play." The same video marks the milestone this represents — "For the first time in our 25 year history" — which Variety put in print as the first-ever RuneScape game to come to consoles in the franchise’s 25-year history.

The console launch itself was announced on 5 June 2026 by Mod Doom, naming PC, PlayStation 5 and Xbox Series X|S — with no mention of Nintendo. Switch 2 was added four days later, on 9 June 2026, by way of a Nintendo Direct, which is why the older official post reads as incomplete rather than wrong. The same announcement video adds two commercial details worth recording: the game was available day one for PlayStation Plus Extra and Premium members and for Xbox Game Pass members, and physical editions for PlayStation 5 and Xbox Series X followed on 5 November 2026.

Cross-save is the capability people assume comes with crossplay, and it does not. Jagex answered it directly in the FAQ attached to the PlayStation 5 announcement of 2 June 2026, under the heading "Will saves carry over?":

• "Not across platform. We’ve got Steam Cloud Save support, but your progress will not carry over to new platforms. You can crossplay your existing characters on Steam with other platforms when they launch, but won’t be able to transfer your saves from Early Access into the new platforms."
• A Jagex moderator on the official Discord, citing the same position, put the split in one sentence: "Just to be totally clear, you’ll be able to play with people on other platforms (cross play), but you won’t be able to use characters or worlds from other platforms (cross saves)."

The practical result is that buying on a second platform means starting there. Your Steam character cannot be moved onto a console, and a console character cannot be moved back, even though both can join the same world. Reports from players who found this out the hard way are consistent about the distinction, and the community has spent most of its energy on the difference between the two terms rather than on disputing either answer.

One mechanism is worth stating carefully. According to a post-launch creator guide published on 15 September 2026, the world creation screen offers a crossplay toggle you can switch on or off: "choose whether to toggle crossplay on or off when you’re creating a world. The game does have full crossplay as an option, however, meaning you can play with friends whichever platform they’re on." A professional guide updated the same day describes a host enabling crossplay when loading a multiplayer world and sharing an invite code. Both are post-launch descriptions of the interface rather than official documentation.

RuneScape: Dragonwilds has no official performance documentation in any source behind this page. There is no published benchmark, no minimum-spec test, no recommended-spec test, and no statement from Jagex about expected frame rates on any platform — PC, PlayStation 5, Xbox Series X|S or Switch 2. The only official performance statement of any kind is the pair of moderator replies about the December 2025 stutter, and those describe a bug rather than a target.

That leaves a page like this one with a choice between inventing figures and describing their absence. The list below is what the evidence does not support, written down so that nothing on this page can be mistaken for a measurement:

• No frame rates were measured here. Every FPS figure on this page is a sentence someone wrote about their own machine, quoted with their hardware attached. None was reproduced, and no two of them used the same settings, resolution or scene.
• The percentage gains are the creator’s, not Jagex’s. The 10–12% for DLSS Quality, the roughly 40% for frame generation, the 3–4% per shadow step, the 5–6% for reflections and post-process, and the 12% for a GPU overclock all come from one April 2025 video. He says them while demonstrating settings; the video shows no benchmark run for any of them.
• The settings advice predates the game’s current form. The optimisation video is from 15 April 2025 — seventeen months before 1.0, before console versions, and before at least two major updates. Whether GameUserSettings.ini still exposes the same parameters is unverified here.
• There is no console performance evidence at all. No source behind this page tests the game on PlayStation 5, Xbox Series X|S or Switch 2, compares quality modes, or reports a frame rate on any of them. The console hardware appears in this page only as platform capability, never as performance.
• Partial Controller Support is a capability label, not a verdict. It is Steam’s category wording. No source here explains which actions still need a keyboard, and no source rates how the controls feel on any platform.
• There is no verified button map. The controller and keyboard details on this page are launch-day player reports and one incidental mention of a single key in a third-party guide.
• No macOS or Linux build exists to assess. The storefront lists Windows only, so the question of how the game runs on either system does not arise from a product that is on sale.

If you take one item away from this page, make it the only one that comes from the people who make the game: the Product Director’s suggestion to open settings and click auto detect, on either the performance or quality branch, which he said may help fix stuttering. It is a single sentence in a community thread, and it is a more reliable starting point than any of the tuning lists above it, including the detailed ones.