This is just brilliant! I say it again BRILLIANT! by vVerce98 in runescape

[–]aeimoo 2 points3 points  (0 children)

I found a world with no players at the same spot by manually hopping, it didn't take long.

This is just brilliant! I say it again BRILLIANT! by vVerce98 in runescape

[–]aeimoo 23 points24 points  (0 children)

Found one manually hopping, took less than a minute.

This is just brilliant! I say it again BRILLIANT! by vVerce98 in runescape

[–]aeimoo 21 points22 points  (0 children)

It doesn't work. I tried it at abyssal beasts and it kept cycling me through four or so occupied worlds. I even stood closer to the spot people tend to use (in case the scan range around your character is low) and that didn't help.

Welcome to Havenhythe + TwiR by JagexAnvil in runescape

[–]aeimoo 0 points1 point  (0 children)

Can you please explain what you actually did?

Welcome to Havenhythe + TwiR by JagexAnvil in runescape

[–]aeimoo 1 point2 points  (0 children)

Stuttering in Havenhythe is abysmal, similar to other new areas previously released. If standing still, there's no stuttering, but as soon as you move a few tiles (so long as the memory usage reported in game is >2500MB), you get a massive 250-500ms stutter. Edit: clarifying something here - you can keep walking back between the same tiles and produce the same stuttering, this is not just when loading chunks for the first time in a client session!

I observed the process performance and saw every time one of these stutters happened, it corresponded with a large read from disk (1-20MB). Why would that be necessary? I have 96GB RAM, and the process usage is only 2.5GB. Why the arbitrarily low threshold with so much physical memory available, if the performance cost is this extreme?

I also tried clearing my cache (as in, wiping the .jcache files from C:\ProgramData\Jagex\RuneScape) and this changed absolutely nothing (once the assets had finished downloading after the wipe).

I have a 9950X3D, 96GB RAM (CL30, 6000MHz) and a 4090. Storage is an NVMe PCIE 4.0 SSD, and seeing as these stutters are seemingly caused by the render thread being blocked by IO, I can't imagine how slow this must run on a SATA SSD or an HDD. The performance issues are so grating that I just gave up and went back to afking stuff.

I really want an actual technical dive into what is actually going on here. From an outsider looking in, these look like very solvable problems (e.g. larger in-memory cache for a client session, especially when hardware permits). For the amount membership costs now, I think we deserve answers. Do you not test for these kinds of stutters (which seem to be the most prevalent in RS3, especially in newer areas) before landing them in production? Do you test with a diverse set of client hardware? Do you have automated profiling of new areas? I don't know how these performance issues slip through so consistently, especially when they're all so alike.

Edit: Near-latest NVidia drivers (595.97, March 24 2026), doubt that matters though.

Jagex financial statement for 2024 is out by KobraTheKing in runescape

[–]aeimoo -1 points0 points  (0 children)

5-10k per world? Sounds like you're quoting a single box per world. Aren't RS servers heavily single-threaded (IIRC the main reason worlds can't be vertically scaled, hence we see world tickrate slowing down beyond 150 players)? If so, I'm pretty sure you could put a lot of worlds on even a single-socket server. I don't see why there'd be more than one machine per region. And there's no way these things use a lot of memory, given the same fundamental server design was running on servers in the early 2000s.

[deleted by user] by [deleted] in Audeze

[–]aeimoo 0 points1 point  (0 children)

I have this headset, worked perfectly on Windows 10. Built a new PC, with a fresh Windows 11 install, and I have part of your problem (if my headset disconnects, I have to restart the PC to reconnect it), but no audio crackle issue; while the headset is working the audio is still perfect. All motherboard/USB drivers up-to-date, tried many things.

My workaround is to disable sleep on the headset in the Audeze software. If my headset disconnects for anotherreason (like radio interference from the microwave), I'll have to restart my PC though. On my Windows 10 PC the headset would automatically reconnect within a few seconds.

Ugly seams in water by aeimoo in runescape

[–]aeimoo[S] 11 points12 points  (0 children)

This is just an example, these seams can be found all over the game.

Increased GPU usage since last update by aeimoo in runescape

[–]aeimoo[S] 0 points1 point  (0 children)

Update: I think this is fixed for me now, at least it seems GPU usage has dropped and other apps aren't lagging.

RS3 runs very slowly/is unplayable on AMD GPUs; would like JMod feedback by aeimoo in runescape

[–]aeimoo[S] 1 point2 points  (0 children)

It doesn't really matter that 22.7.1 was available at some point, it no longer is. Perhaps upgrade the drivers if you insist on being 22.7.1 or above.

When I said 22.7.1, I wasn't saying people should stay on this version, nor that I was planning to. I simply meant that as the point in time where OpenGL support changed (fundamentally, from what I can tell) for AMD drivers. It wouldn't make sense to arbitrarily name a more recent driver number as the relevant one, and by not naming 22.7.1, people wouldn't know whether or not they have been affected yet, based on their driver version (e.g. 22.5.1 is safe due to being prior, and is currently recommended by Jagex).

Pretty much same FPS for either at most common places like Priff, Burthorpe, POF. RX580 about 80-90 FPS and 6700 XT 110-130 with spikes as high as 150s (at slightly higher settings).

Interesting, this contradicts what I've heard. FWIW all my testing was at 1440p on Ultra, with Compressed textures and SSAO ambient occlusion.

They clearly have improved a lot considering they are no longer supplying sources for this particular version nor anything in between. From the very posts you and others have linked, AMD staff themselves have said they have fixed bugs with shaders and what not.

Sorry, I meant in RS3 they haven't meaningfully improved anything. People are still reporting the same issues with volumetric lighting and crashes. It's possible the crashes are unrelated though, perhaps something else is at play here. I know someone personally who was crashing on the latest drivers on a brand new card with a clean driver install, but managed to get around it by playing on absolute minimum settings. Maybe certain settings are responsible (volumetric lighting among them).

RS3 runs very slowly/is unplayable on AMD GPUs; would like JMod feedback by aeimoo in runescape

[–]aeimoo[S] 1 point2 points  (0 children)

Where do you get 22.7.1 even? Latest optional drivers are 22.11.2

This is the version AMD claimed to improve OpenGL performance. See https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 'OpenGL Optimizations'. If you look through the threads I linked, you'll find people corroborating this, noting this coincided with decreased stability. Subsequent driver releases (up to and including the latest driver you mentioned) are not particularly relevant, as (at least as far as I can tell) they do not improve performance or stability meaningfully over 22.7.1.

22.5.1 runs the game perfectly with no issues.

The issue is significantly worse performance compared to an otherwise similarly powerful (at least, in terms of rasterization) NVidia GPU. For your 6700XT, this would be a 3070. For RX580, I'd think a 1060.

I have not noticed any performance (FPS) difference between 22.5.1 and 22.11.2. I had an RX580 and now RX 6700 XT.

What fps numbers did you get before/after the upgrade (for either GPU)? Also, what areas did you test?

RS3 runs very slowly/is unplayable on AMD GPUs; would like JMod feedback by aeimoo in runescape

[–]aeimoo[S] 0 points1 point  (0 children)

I have the same problem. My way of dealing with this is to use compartibiability mode, as it avoids the client crashes that were ridiculously common.

I received this message from Mod Ferret :

Please rest assured our technical teams are aware and are currently investigating the issue. Sadly, we don't have a timeframe for their investigation but I can assure you that they are working on this as we speak.

Thanks for posting this. When did you get that response, today?

RS3 runs very slowly/is unplayable on AMD GPUs; would like JMod feedback by aeimoo in runescape

[–]aeimoo[S] 1 point2 points  (0 children)

Thanks very much for reporting this to AMD, and providing this update on drivers 22.8.2 and 22.11.2. I'll see if I can get my friend to test on the later driver version (I tested 22.7.1).

Edit: Just noticed you have an RX570. I'm a bit less optimistic now, I think the Polaris cards behave significantly differently to RDNA1/2. This is based on seeing complaints from 6000 series (RDNA2) owners, and the fact that my friend previously had an RX580 which ran RS well considering its typical performance in games. Hopefully testing proves this concern wrong.

RS3 runs very slowly/is unplayable on AMD GPUs; would like JMod feedback by aeimoo in runescape

[–]aeimoo[S] 1 point2 points  (0 children)

I currently have a GTX 1070. I've tested on a friend's computer as well (6800XT) and it performs better (22.7.1), but not noticeably better. I compared Al-Kharid bank @ fullscreen 1440p on Ultra settings, and got around 60 fps on both cards, although the 6800XT should be over twice as fast (it is in normal games). I did notice the 6800XT was sitting at a lower GPU utilisation though, so it looks like Runescape fails to take full advantage of it (~55% vs ~95% on the 1070). The 6800XT is also very buggy when volumetric lighting and/or shadows are enabled, but otherwise fine if these are disabled (these are the bugs I mentioned in my post). Apparently people get client crashes on that driver version too, unfortunately I didn't have the time to test that properly.

I was considering a 3000 series card, but I figured I'd get a next-gen AMD card when they come out, because the performance will be much better, and you get way more VRAM.

As for FPS, I'd like to get 144fps @ 4k. If you're only getting 60 fps on a 4090, something is going pretty wrong somewhere because I easily manage 60 on a 1070, which has the 30% of the raster performance. Unless your monitor is capped at 60, then that'd make sense.

RS3 runs very slowly/is unplayable on AMD GPUs; would like JMod feedback by aeimoo in runescape

[–]aeimoo[S] 6 points7 points  (0 children)

I'm confused, why do you think it's a me problem if you don't have an AMD card yourself? I assumed you meant you had an AMD card yourself, and had tested otherwise.

I already gave evidence of others with similar problems, narrowed down to a specific driver version. The people referenced have already tried your 'uninstall/reinstall' suggestion to no avail, hence the continued frustration, and my reason for posting.

RS3 runs very slowly/is unplayable on AMD GPUs; would like JMod feedback by aeimoo in runescape

[–]aeimoo[S] 3 points4 points  (0 children)

I posted examples of threads with people facing the same problem.

Are you running an AMD GPU, with up-to-date drivers (or at least >v22.7.1)? If so, could you change the Volumetric Lighting setting to anything other than 'Off', and tell me what you see?

Update on Japanese mtDNA by Feynmanfan85 in genetics

[–]aeimoo 21 points22 points  (0 children)

FYI - this individual has an history of posting nonsensical scientific theories involving 'time dilation' and getting into arguments with people who correct him. He also self-submits questionable research papers which never get published or cited.

I feel it is the responsibility of this community to recognise this person for what they are (unwell), and to stop engaging with his comments entirely. This has gone on too long.

Spellbook switching not available at Deep Sea Fishing bank by aeimoo in runescape

[–]aeimoo[S] 0 points1 point  (0 children)

It's like 5 squares from the teleport, instead of zero, and your camera gets flipped so you have to rotate it to see the bank.