RuneScape, which is a long-running fantasy world people play online together, is changing how it draws itself. The game's news post of 4 September 2026 says a voluntary open beta of its Vulkan renderer starts on Windows on Monday 7 September, and you switch it on yourself from the Graphics Mode setting.

The post is signed by the RuneTek team, which is the name it gives the group that builds the game's engine. It never says how long the beta runs.

When does the RuneScape Vulkan beta start?

Monday 7 September, on Windows, and taking part is your choice. The post describes this as the first step of what it calls a staggered rollout, chosen because shipping a new rendering backend is high risk. A rendering backend is the part of a game that turns the world into the picture on your screen.

The beta is there to collect data. The post says it will give the team a lot of information about remaining crash, visual and performance issues, and that only once the team is happy those are resolved will it start offering the Vulkan version as the default through the launcher.

How do I switch RuneScape to Vulkan?

Four steps, from the post's own instructions.

1. At startup, open the options menu. Click the options button in the bottom left corner, or use the RuneScape then Options shortcut on the menu bar at the login screen.
2. Find the Graphics Mode setting.
3. Switch it to "Vulkan".
4. Restart the client, so the launcher can download the new program file.

Our guess is that the last step is the one people will miss. The post says you have to restart the client after making the change so that the launcher can download the new executable, which is the program file it runs.

What is Vulkan, and what does it replace?

The game currently uses OpenGL, which is the older of the two ways it can talk to your graphics chip. Vulkan is a newer one, built by the Khronos Group, and the post says it works across platforms rather than being tied to one.

The post's own comparison is a car. OpenGL is the automatic and Vulkan is the manual: both get you there, but the manual gives more control over gear changes and fuel economy. In practice that means the engineers get to decide more of what the graphics chip does, and have to be more precise about it.

Vulkan arrived around 2016. OpenGL's last major update was version 4.6 in 2017, and the post says it has essentially been put out to pasture.

What will I actually notice?

Less than the headline suggests, at first, and the post says so itself. For launch it says the goal is for Vulkan to be at least as good as, or better than, OpenGL on stability and raw performance. Parity is the floor it sets.

The most immediate change the post says you may notice is streaming performance, and it means the technical kind rather than the Twitch kind. Streaming here is the game loading the world in and out around you as you move. Better streaming means faster loading and less stuttering when you run across the map.

The post ties that to threads. Multi-threading is a computer spreading work across several parts of its processor at once instead of queueing it all through one. It says OpenGL's threading model is not up to snuff, that for the most part this is behind certain stuttering issues that have somewhat plagued the game over the years, and that Vulkan is built for multi-threading from the ground up.

Why now?

Because the old road is closing. The post says OpenGL is no longer actively developed and is essentially deprecated, that many platforms are stuck on older versions of it, and that Apple and other platforms have warned developers they may remove OpenGL support altogether in future operating system versions. It says vendors such as Nvidia and AMD are already winding support down in various ways.

There is a second reason, and it is about the team's own resources. The post says waiting this long let the OpenGL work mature to the point where very little engineering time goes into it, and that this is what lets it support two renderers in the live game at once without a significant hit to those resources.

Timeline: one real date, and four promises with none

This is the part worth keeping. The post narrates a full rollout in prose, but it commits to exactly one day. Everything else is an order of events with no calendar attached to it. Our reading is that this is the honest way to write it, and also the reason not to plan around any row below the first one.

Step	Platform	What the post dates
Voluntary open beta	Windows	Monday 7 September
Vulkan becomes the default renderer	Desktop, through the launcher	No date. Conditional on the team being happy that crash, visual and performance issues are resolved
Rollout reaches mobile	Android first	No date. Stated as after desktop
Rollout reaches Apple devices	OSX and iOS	No date. Stated as after Android
OpenGL becomes the fallback	Any device without Vulkan	No date. Stated as happening once Vulkan is the default

Four of the five rows are sequenced against each other and pinned to nothing. That is not a complaint. Our reading is that this is what a staggered rollout looks like when a team will not promise a date it might miss, and we would rather have this than four dates that slip.

What happens to OpenGL, and to Mac and phones?

OpenGL does not disappear immediately. The post says that once Vulkan becomes the default renderer, OpenGL mode becomes the compatibility mode, or the fallback for a device that cannot run Vulkan. On minimum specification devices it hedges: it says those should theoretically guarantee Vulkan 1.1 support, and we are keeping the hedge because the post did.

Apple is the awkward one. The post says Apple does not officially support Vulkan and uses its own low-level graphics interface called Metal instead. The bridge is an open source translation layer, which is a piece of software that converts one set of graphics instructions into another, called Molten in the post's own spelling. It says Molten maps the Vulkan code into Metal code on the fly with little extra overhead, and that the Khronos Group maintains it, so future support is probably guaranteed.

Elsewhere, the post lists three places where Vulkan is already the preferred interface: SteamOS hardware, Android and Linux. It also says DX12 is Windows only, and that this game needs an interface that runs on more than one platform.

Our take

The sentence worth reading in this post is the one about stuttering. It says long time players will probably know those stuttering issues, it says the cause is for the most part OpenGL's threading model, and it says this should no longer be the case with Vulkan.

A beta whose stated floor is to match what you already have is a strange thing to advertise, and it is also the right thing to build. The lighting talk further down the post is years of maybes. The thing we would watch is the second row of that table. A default switch with no date is where a beta either lands or quietly stops being mentioned, and it is the row that decides whether any of the rest happens. When a date shows up, it goes on our cross-game calendar, which is where we track every dated event across the games we cover.