2009Scape Official Forums

Alright, try something for me. Can you launch the singleplayer server jar directly with java, and then independently, using the Launcher, connect to the "Local Server" profile with the correct Launcher-managed client?

concerning, as the singleplayer should just be going off the built-in plugin management system the launcher has. At least, that would be the expectation. It seems the implementer of singleplayer could simultaneously be shipping an old client and old plugins by default? Concerning.

Oh, launcher in the logs says it's using X11. Ah, interesting. Maybe you've somehow obtained an old copy of the client that ignores the FPS settings? It's not completely out of question. Also, just as a precaution, if you've installed any client plugins, go through and uninstall them all. Maybe one...

Sorry for my noob response, but how do I swap to an X11 desktop? I mean, wouldn't that have to be a different window manager or no? I know in the past installing multiple window managers can get messy so I want to avoid that. No difference between sd and hd, my system isn't tanking. Installing a di...

It's also worth mentioning that Minecraft's rendering works very differently to RuneScape's, Jagex had to do some very creative things to get native OpenGL, etc working in a web browser.

to me it definitely sounds like the issue you're having is explicitly tied to the client, does SD vs HD make any difference in the framerate? does quickly swapping over to an X11 desktop help with the issue? (Wayland still has limited support for some Java applications, and may really disagree with ...

If you're on linux, try setting the FPS cap in the launcher from 0 (auto) to 50 There is a bug in the JDK where on X11, people with multi monitor setups sometimes have a default debug response come up when you attempt to get the refresh rate. The automatic FPS detection code, then, would be setting ...

where did you obtain your copy of singleplayer? can you tell what version the launcher is?

The linux flatpak is a special case. It runs in a container, because it is a flatpak. There could be many unforeseen causes of performance issues there. The original poster of this thread explicitly mentioned that the problem does not affect a local build of the source, only the flatpak. So, your p...

The linux flatpak is a special case. It runs in a container, because it is a flatpak. There could be many unforeseen causes of performance issues there. The original poster of this thread explicitly mentioned that the problem does not affect a local build of the source, only the flatpak. So, your pr...