Stuttering on 5800x3d and 7900 xt on LOW settings

[Mr.Overrated]

Month 5, day 30, 3h in and there is constant stuttering on

• Every 2 seconds in exploration mode
  
• Every 4th-5th circle in minigame (wood cut and mining)
  
• Every end turn of my units in combat
  
• Every beginning turn of enemy in combat

I never buy early access games whether it be from big or small dev company. But if a company uses this method, the end product must be extremely better compared to one that does not use this. So what was the point of EA then? I am reading this was an issue during this period and still no update on fixes?

I am not expecting the game to be perfect. But what I am expecting is that for a comparatively low resource game (from a hardware standpoint), it should be seamless especially with the hardware I got.

Edit: 2024/04/13 - Upgraded my cpu to a 7800x3d and loaded my old save to try this again before the new DLC. Still stuttering on those 4 occasions. Not planning on creating a new save to test it out and see if its because I have 8+ members so take this with a grain of salit

[Floid]

Scase is KING of Narwhals님이 먼저 게시:

Floid님이 먼저 게시:

The cause is the memory leak. A memory leak in a nutshell is deviations in allocated & deallocated memory. Unfortunately there are many things that can lead to systemic memory leaks.

However one thing that should be noted is that more often than not, causes of memory leaks are usually foundational. Which means they can be hard to track down and fix.

But it also means that whatever is causing the memory leak is something that was instituted at the very early stages of development. Which means the devs have more than likely known of this issue predating the EA period - and to be aware of an systemic issue for the entire duration of an EA period - not fix it - and then proceed to still release into 1.0 - while already fully aware of a long running systemic foundational issue, is completely unacceptable.

I want to agree with you that it is a mem leak cause it REALLY acts like one, but i've also noticed the stutter happen damn near immediately. The game doesnt even run long enough for a leak.

Yeah that is a bit odd - though i've known certain types of mem leaks in the past, where say for example a particular broken backend process (such as garbage collection) will both gradually contribute to the accumulation of mem usage - whilst at the same time eating cpu cycles each time it ticks over, thus causing micro stuttering also.

Which is why it's fairly reasonable to assume that there is a similar dual process at play here with wartales. However if that is not the case, and the memory leak is not the cause of the micro stuttering, then that means there are two BIG issues Shiro has to solve, instead of just one lol, and god knows how long that's gonna take...

[Scase is KING of Narwhals]

Floid님이 먼저 게시:

Scase is KING of Narwhals님이 먼저 게시:

I want to agree with you that it is a mem leak cause it REALLY acts like one, but i've also noticed the stutter happen damn near immediately. The game doesnt even run long enough for a leak.

Yeah that is a bit odd - though i've known certain types of mem leaks in the past, where say for example a particular broken backend process (such as garbage collection) will both gradually contribute to the accumulation of mem usage - whilst at the same time eating cpu cycles each time it ticks over, thus causing micro stuttering also.

Which is why it's fairly reasonable to assume that there is a similar dual process at play here with wartales. However if that is not the case, and the memory leak is not the cause of the micro stuttering, then that means there are two BIG issues Shiro has to solve, instead of just one lol, and god knows how long that's gonna take...

Well, this one has been damn near 2 years. So I'm not holding my breath lol

[A boy named Sue]

*puts on a tinfoil hat*
What if it's a feature just to make mini-games harder and the dev forgot where he put the code?

[LlamaWithKatana]

SeenZ님이 먼저 게시:

Cthulhu: The Deep One님이 먼저 게시:

Its a known issue man. Try loading in opengl. They said they have a fix for it. I have the same issue. I had to stop playing cause it killed the minigame

As for the minigames, I found a way. They loop so you don't loose the minigame if you didn't click at all. So if you get some stuttering, you can wait few seconds until it stops before actually playing (all minigames "loop", aside of fishing). At least that's what I do. Hope it helps until it gets fixed.

As for OpenGL, it makes the stuttering worse for me. Also I would say reboot the game from time to time. I noticed the more I play, the more stuttering I get. Then I noticed a memory leak : when I launch the game, it only uses like 1.5 GB RAM. But the more I play, the more RAM it uses. After some hours, it uses all of my 32 GB RAM memory. So I close the game and launch it again and I have no stuttering (for a while at least).

A bit annoying indeed, but it allows me to play the game without much issues until this bug is fixed. ^^

OMG I thought I'm going crazy! Thanks. At least now I know I'm not insane!

[LlamaWithKatana]

BTW for everyone having memleak issue - ISLC might help but stutter won't go away.

[Knatternick]

Mr.Overrated님이 먼저 게시:

Month 5, day 30, 3h in and there is constant stuttering on

• Every 2 seconds in exploration mode
  
• Every 4th-5th circle in minigame (wood cut and mining)
  
• Every end turn of my units in combat
  
• Every beginning turn of enemy in combat

I never buy early access games whether it be from big or small dev company. But if a company uses this method, the end product must be extremely better compared to one that does not use this. So what was the point of EA then? I am reading this was an issue during this period and still no update on fixes?

I am not expecting the game to be perfect. But what I am expecting is that for a comparatively low resource game (from a hardware standpoint), it should be seamless especially with the hardware I got.

I have an ancient system and it stutters from time to time. Especially if you play for a long time. Think it's the RAM or SSD usage. Of course, the graphics card also plays a role, but no developer can test every system until it fits. There they depend on the players and you are in the wrong forum. Just report it as a technical problem.

[Mr.Overrated]

just an update, 4 months after this post stuttering is still on. I loaded an old save and there was a lot of stuttering compared to a new game. So its still true that the further you get the more stuttering is pronounced which sucks

[Miko]

+ 1
...same Problem here... sometimes unplayable...

[Mindeveler]

n3mes1s님이 먼저 게시:

Big companies dont launch early access games lol. That would be hilarious. The problem is today steam publishes everyting cuz for every single game that is published they get $$$. And for every single sell of that game they get $$$. So it doesnt matter if the game is good or bad, if its broken or not, its going to be published. This game has a lot of potential but because of the mini freezes problem it makes it almost unplayable reaching a point (patience is not one of my virtues anyways) and in this state it shouldnt be allowed to be published in steam to start with. But i tis. Like any other crap title you can find. Because it generates $$$.

But unfortunately new kid gamers of this generation dont really see it as a problem, cuz they are getting used to play crappy games in crappy conditions. They think having stutter and mini freezes is something normal to live with. These "gamers" are sadly destroying the videogaming industry since 2010.

n3mes1s님이 먼저 게시:

Yup i remember the good times when videogaming industry was all about love and dedication unlike today. The years 1990-2010. That time period was amazing. And i miss it so much.

Oh please. Don't you feel cold on your high horse, your ancientness?
1) If you do a research/poll regarding correlation between age and willingness to play bugged games, I bet you'll find out it's older generation that is prone to that (because it's exactly the kind of people who've been playing games since the days when PCs were crap, graphics were terrible, unofficial translation was bad, there were no patches without internet, games were hard and everything had to be earned etc. etc. and they're used to tolerating/overcoming all sorts of difficulties). And not that "pampered youth who needs instant gratification, easy victories and perfect conditions" like everyone's whining all the time.
You old relics can't even avoid mutually exclusive complaints in your everyday ♥♥♥♥♥♥♥♥ about bad modern generation. And how old are you anyway? 35?

2) You're mistaken if you believe older games weren't bugged.
I love Spellforce to death but its first part had critical bugs on release which made me unable to play it for years until I got internet (and patches thanks to it).
Settlers HoK and Empire Earth II refused to run on one of my PCs.
FONV was infamous for tons of bugs on release which weren't entirely fixed even in the end.
But sure, grass was greener, sun shined brighter etc.

3) Sure, in the past everyone worked for ideals alone, didn't need money and food.
And now everyone is a corrupt gold digger.

4) Nobody, literally nobody forces you to play early access games. It's 100% free choice.
Don't want to risk dealing with bugged mess? Just pretend the game didn't come out yet and ignore it until it's out of early access or until you watch enough reviews&letsplays on youtube to convince yourself it's in good enough state. That's what I usually do myself.
You're too impatient to wait? Well, that's your problem. Yours alone.
But some people either like the game enough to enjoy it or would simply love to help the devs with testing.
Thanks to those people, the games cost less 'cause testing is cheaper. Thanks to them, development takes less time. Maybe, thanks to them, those small indie games even come out in the first place because the devs don't run out of budget, time and motivation before the game is finished.
But instead of being thankful, you're acting like an arrogant ungrateful ass.

5) Stutters are bad, yes. I too would love to see them fixed among other things.
But tbf, sometimes devs just can't find the reason for certain bugs.
E.g. Eador MOTB is infamous for access violation errors that plagues the game since its release. And the devs never managed to fix those errors and even issued a public statement at some point that basically said "yeah, we tried, a lot, but we just don't know how to fix that, sorry". And one of its DLCs even starts with a warning about that error and suggestion that the player should refund the DLC if they don't want to deal with that error.


You don't get to decide what should be published and what shouldn't. Your arrogant highness is not The Emperor of the World who can tell others what to play and what not to play.
But in this world of open information you can always decide what to buy and when to buy it, Based on letsplay, reviews and some other sources. As simple as that.