Patch 2.0.1.22498 - Low FPS/stuttering (+ workarounds)

Basically everyone agrees on that.

That said, technical issues will arise with any game, and threads about them should exist, but with any good team they would be getting responded to / addressed rather than ignored.

[quote="CaptainJack-11336, post:42, topic:34556]
technical issues will arise with any game [/quote]

That is factually wrong. There are enough games that did not have technical issues when they were released. Do not mistake gameplay / logic bugs for technical issues.

3 Likes

It is not factually wrong. Pretty much all computer software has had a bug in it at some point, whether it’s just not doing what it was intended to do, doesn’t like certain hardware, has slow performance, whatever. bugs are technical issues, and technical issues are bugs, whether you like it or not. You don’t get to redefine computer terminology.

All unintended behavior is a technical issue. You are just grasping at straws to make a negative reply towards me. I really don’t know why you’re attacking me, since I explicitly agreed with your post, but… you do you I guess?

Workarounds for Linux: https://www.reddit.com/r/WC3/comments/1j3m6gf/linux_more_stable_fps_no_stuttering/

Limiting to physical CPU cores only with taskset (instead of WINE_CPU_TOPOLOGY), Above 4G Decoding without rBAR / SAM and the launch argument -graphicsapi Direct3D12 helped a lot with the stuttering on my system.

Similarly, in some cases, performance can be increased by forcing the game to run on certain cores in Task Manager. Unfortunately there is no way to do this automatically for programs launched by a launcher like the battle.net app, it can only be done in task manager while the game is running.

If you have been experiencing a consistent, periodic stutter, there is a new update on the PTR that might improve this for you:

I can confirm the game runs much better on the 2.0.2 PTR and the hitching is gone. Jumped to 150 fps in some areas where i had 44 fps with 2.0.1

2 Likes

Yeah!!! Finally!!! After months waiting, now I can continue the campaign! :raised_hands:

1 Like

Problem description: Major and constant hitching in intervals of about five seconds.
Tried workarounds: Tested on Radeon dGPU (RX 7800 XT), Radeon iGPU (Ryzen 7600X), Geforce dGPU (RTX 5070); the first two on driver 24.12.1, the last on 572.83. Moved the game from NVME SSD to SATA SSD and verified the files. Updated chipset drivers and BIOS. Lowered graphical settings very low.
CPU: Ryzen 7600X
GPU: Geforce RTX 5070 (current)
GPU driver version: 572.83
RAM: 32 GB (F5-6000J3238F16G)
OS: Windows 11, build 26100.3624
Game display resolution: 3840x2160
Game style: Reforged

I have noticed that an upcoming patch is aimed to fix the issue, which I’m glad of. Still I thought it wouldn’t hurt to share confirmation on it.

3 Likes

I went from RTX 3070 which worked great and had over 200+ FPS to a RTX 5090. which gives me lik 100 fps.

I tried adding -graphicsapi Direct3D12 to the command line arg and changing CPU affine, trying different variations. Still the same. Feels ridiculous considering which GPU I use. I also verified that internal graphics are deactivated. Any other suggestions / ideas?

v2.0.1.22498

When I run game with ā€œclassicā€ settings everything is okay, but when I switch to Reforge I have 100fps and framedrops to 60-65 every 5 secodns :grimacing:

The funny moment I have split save between classic and reforged, on classic I have like 6 campanies completed and when I switch to reforged - only 5, how is this possible

I’m so applaused with this game, so I want to play old warcraft 3 instead, main menu is still laggy, game can crush after switching settings from classic to reforged :flushed:

Everything is having low usage, than in my experience only can be connected to the game optimizations: GPU usage 17%, CPU usage 15-25%, SSD usage 1%…

including argument was not the fix for me.

-graphicsapi Direct3D12

CPU: Ryzen 7 5800X
GPU: Geforce GTX 1080
GPU driver version: 560.94
RAM: 16 GB Patriot 2666mhz
OS: Windows 11 PRO, build 19045.5608
Game display resolution: 2560x1440
Game style: Reforged | Classic

So did the last patch actually fix anything, break more or did nothing?

Problem description: FPS drops from 160 to 40 constantly
Tried workarounds: -graphicsapi Direct3D12, CPU affinity
CPU: Ryzen 7 5700X3D
GPU: 4080 Super
GPU driver version: 566.36
RAM: 16 Gb 3600Mhz
OS: Windows 11 Pro, 26100.3476
Game display resolution: 3840x2160
Game style: Reforged and Classic

Well, it’s NOT possible to play the game, FPS constantly drops from 160 to 40, I was trying to play Story, but it’s hard. No matter the graphic settings, Reforged or Classic it stutters a lot. Especially when I move my camera.

I tried the fixes listed above, thank you all who participated, but all I can get is drops from 160 to 60fps. Without fixes it goes down to ~40 FPS. Still it’s not playable.

Just in case: I checked, no integrated gpu is in use only the main one.

Blizzard please fix that ASAP, I’ve finally decided to play WC3 multiplayer, but it’s impossible.

It’s fixed on PTR

1 Like

Thanks for you reply, checked on PTR, same drops to 40-50 FPS unfortunatelly

Well, you have a different issue then, because the issue that affected specific hardware was definitely fixed.

Problem description: FPS drops from 160 to 40 constantly
Tried workarounds: -graphicsapi Direct3D12, CPU affinity
CPU: Ryzen 7 7800X3D
GPU: 5080
GPU driver version: 572.83
RAM: 32 gb ddr5 6000 mhz
OS: Windows 11 Home H2
Game display resolution: 2560x1440p
Game style: Reforged and Classic

As if by magic, the patch out today fixed the problem and now my FPS is solidly locked to my monitor’s max refresh rate again! Almost like it was a poorly coded game patch causing the problem, not ā€œbad hardwareā€.

1 Like

The same post with the same gibe, just with the name removed. Just couldn’t help yourself.

Means more to you to point and laugh than it does to just report the problem is fixed for you.

I know, thats why I kept repeating ā€œits not an AMD issueā€ because… well, it isn’t. It’s a Warcraft III issue.