His fps has nothing to do with the servers or connection to the servers. It is entirely about local client performance, and with Classic the bottleneck probably is single threaded cpu performance.
I did a lot of WoW benchmarking. Even on high end Intel i7 or AMD Threadripper FPS can drop significantly with increasing number of players. On a 1.12 client all it took is having 2 raid groups in FOV waiting for a world buff. With modern 1.13 it’s better but still amount of players you see impacts performance and that’s a part of the game infrastructure, not your local hardware (and it’s Classic, those players can’t create modern particle effects that could clog the GPU).
60-90 FPS empty, 30 FPS with people in FOV it’s what usually happens in such cases.
Framerates are always, and I mean always, about local client performance. Sure the other players are creating the scene for your computer to render but the speed that it is able to render it is purely local.
Wow is multi-threading, if it’s not then your settings are wrong. Mine uses all my CPUs but the first 4 mainly. Make sure it’s set to use the correct graphics card, Intel HD is not a graphics card, in the same way a bicycle isn’t a Harley Davidson. Basically Intel HD sucks.
Classic 2019 is not at all the same as Classic 2004, only a fool would think that. Classic 2019 is based on patch 7.5 from memory.
My FPS shot up, it more than doubled, when I went from a HD7770 to a GTX1050Ti
You get a few numbers for each player and your machine does the rest. It gives location in 3D (X, Y, Z and direction), race details and a number for each bit of armour, probably 3-4 bytes at most. Maybe 0.5 kilobytes at most per player. Oh and it doesn’t sync, it sends your info and receives other peoples, it streams.
It has to sync with the server and the server must calculate position, direction, action, appearance and so forth of every player you see. The client has all the assets but it needs the data from the server to draw it. That’s why you can get low resource usage with low framerate - local system is waiting on server response.
And on top of that Blizzard consistency system that check if player state is valid (a.k.a cheating/local client alterations detection).
That is just not how this works. Yes, the client needs updates from the server but those updates being infrequent manifests as network latency and not as lower fps. For example when I was going through my 20 second lag journey in Diremaul my fps was well over 60 the whole way through while I couldn’t see any updates from other players.
have u checked ur cpu usage at the same time and ur memory usage ?
1 Like
This^
People say that RAM doesnt affect your fps but this is actually not true. I have an avarage laptop which lacks of RAM ( 4 GB ). Windows 10 consumes almost half of it +add wow.exe it goes like 80-90% memory usage. I bought another 8 GB of ram and hey, Fps increased with 30 and its super sustainable (regardless if i face people in capitals or open world).
I have no idea what it’s called in windows, but in Linux we have a powergovenor, that lets you tweak how much power/battery the system uses - be sure to set that to performance mode before launching wow.
I know people who game on Linux laptops uses launcher scripts to handle this, there migth be something like it on windows.
Also in your taskmanager find and kill the process named something like wowvoiceproxy.exe - nobody uses ingame voice chat, and the thing eats up cpu and launches a copy every time you re-launch the game with out closing the previous instance.
It looks like your CPU have 4 cores and 25% of CPU corresponds to exactly one core fully loaded.
Your best bet is to upgrade to something like 7700K and keep it cooled, so it’ll boost to high frequencies. Or 9900K if you can afford it. May be even high-end AMD Ryzens, those are really good lately.
This is it guys.
If you wanna run the game as good as possible, get a extremely fast (high GHz) CPU, Intel or AMD Ryzen. The game is also much more CPU intensive than Vanilla was, I don’t know why.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.