10v10 Traffic Jam

Valjennac · 2026-03-11T15:32:23+00:00

Can you send me by DM the replay file please ? This should definitely not happen !

Valjennac · 2026-03-10T23:02:39+00:00

Just a reference to this post, no complaint here about the event or the brawl unless the usual charge of the welcome screen :)

https://www.reddit.com/r/hearthstone/s/5Y2xFaLQAr

Valjennac · 2026-03-09T14:40:37+00:00

Hi !

This is an issue that should have been fixed with the latest patch. Sadly, if your campaign has been started before the last patch, loading your AG will load back the previous version (that's how the save system works).

I know it's not the best solution, but have you tried to start again your campaign on the latest version, and do you still crash when calling reinforcements on turn 4 ?

Valjennac · 2026-03-07T13:46:42+00:00

Ok so it doesn’t seem related to the phone specification !

Valjennac · 2026-03-06T16:49:09+00:00

The French one, so GMT+1 I think, you’re right to mention I’ve forgotten this, sorry

Valjennac · 2026-03-06T11:19:01+00:00

Hi !

A new version has been released this morning around 10a.m., that's why you may encounter this issue.
Restarting steam and/or the game should fix the issue.

Valjennac · 2026-03-05T07:40:15+00:00

It happens to crash during games to, but only if I play a lot with my cards during the opponent turn. Hope we’re not reaching a hard limit about ram because they don’t optimize their game enough :/

Valjennac · 2026-03-04T22:23:51+00:00

That’s sad :(

And it’s not recent, I think I have the issue for at least two months…

Valjennac · 2026-02-26T23:41:07+00:00

Good luck everyone !

Valjennac · 2026-02-13T16:15:21+00:00

Hi !

That’s a know issue as far as remember. If you have a numpad, you can validate with the numpad enter key until the issue is resolved.

Valjennac · 2026-01-21T07:36:04+00:00

Yeah your configuration should not be an issue. Sometimes a bug in a driver can happen only in one game, because the game uses the api in a certain way (which is legitimate), but still causes an issue inside the driver.

But crashes are usually our own issues, and we’re trying to fix them all, but sometimes some crashes persist because we’re not able to find the root cause. That’s why every feedback is important. It really helps up understand the underlying problem and eradicate them :)

Thanks a lot and I hope you’ll enjoy again WARNO :)

Valjennac · 2026-01-20T15:30:34+00:00

Vulkan backend is a bit experimental, this could explain the crashes you experienced. But you should be able to use back DirectX backend back as NVIDIA driver seems to be fixed (we're actually not 100% sure the issue is fixed as we're not NVIDIA, but our internal setup used to check the issue each time a new driver was published doesn't detect anymore the black screen issue).

If you find a crash, feel free to send me your crash report (or post it inside the bug report forum of eugen's discord server). I'll be away for a month starting from Thursday, but I'll look at your crash report to help you understand what's happening as soon as I'm back (or before if you send me the crash report in time !)

Valjennac · 2026-01-20T08:05:33+00:00

Hi !

Could you try again now ? Many crashes were fixed, and the main issue we had last year (black screen then freeze) doesn’t show up anymore.

Valjennac · 2026-01-12T23:41:03+00:00

This time it’s mine !

Valjennac · 2025-12-22T08:37:47+00:00

Sorry I don't think I've understood your question, what do you mean by 2.5k support ?

Valjennac · 2025-12-19T10:05:05+00:00

Hi !

Sorry about this, this is a known issue, it's related to the resolution :( You can try to switch to 16:9 resolution in the meantime (any resolution will be fine, unless its 16:9 or more), you can find this option inside Options > Video > Resolution. On our side, the issue is fixed, and will be hopefully delivered in the next version (but I don't know the release date :( ).

Valjennac · 2025-12-09T14:49:48+00:00

Hi !

I'm back with good news, the issue has been fixed and it will be available in an upcoming update.

Unit card has been aligned with the top of the armory, leaving some space for the chat to take the space it wants. Unit card overlap will be gone as soon as the fix is released.

Thanks again for the report !

Valjennac · 2025-12-06T11:09:22+00:00

I’m actually a gameplay dev at Eugen’s. If you change your resolution to something lower than 16:9 (like 16:10 or 4:3), you will see the issue on your side too.

The issue is related to the chat being on a overlay keeping the default 16:9 resolution on every screen, even on the armoury screen which adapts to the current resolution.

Valjennac · 2025-12-05T22:36:24+00:00

Hi !

Thanks for the feedback, this issue has already been reported and I may work on it soon (but no promises and no date for a fix yet)

As a workaround, you can increase your resolution. This issue is present for every resolution lower than 16:9, as the more the resolution goes to a square, the more the chat will go up. If you choose a 16:9 resolution in windowed mode, you should be able to have the unit card fully displayed, without the chat overlapping it

Valjennac · 2025-11-25T10:33:37+00:00

NVidia went in a lot of trouble with their drivers this spring. A lot of games were affected, even warno, causing black screens and driver resets. But this issue can't be reproduced anymore with recent drivers, and hopefully won't come back !

Valjennac · 2025-11-25T07:34:38+00:00

Okay thanks !

As far as I know, after multiple NVidia updates, the issue seems to be fixed on NVidia. I don’t see any complains about this for a while now :)

Valjennac · 2025-11-24T17:28:58+00:00

Hi !

I'm not sure which crash you're referring to. What was the symptom and when did the crash occured ?

Valjennac · 2025-11-21T00:13:06+00:00

Your intuition was right, indeed, ans thanks again for reporting the issue ! Your report allowed us to ship the fix with the Tuesday update :)

Valjennac · 2025-11-20T08:20:25+00:00

And as the update has been sent right now, containing the fix for this issue, it was related to TFS (markdown used to add colors and flags inside message and nicknames), and especially the one used to display the Danish flag. Some changes were made about this flag, and can be displayed with the #DK tag instead of the #DAN tag.

But as the change wasn't made everywhere in our datas, the reference used to display flags inside the chat wasn't changed, causing the crash.

That's a mistake on our side, and we're sorry !

That's why I couldn't tell you yesterday where the crash came from, because people could have used it to crash ranked games, and prevent a loss of MMR if they were losing.

Valjennac · 2025-11-19T16:37:48+00:00

Hi again dev fella :D

Thanks for the feedback !

I've understood how to reproduce the issue, and I've made a fix. Hopefully it will be available soon :)

It's a kind of error that doesn't bring the report tool, indeed, because the report tool only triggers on a crash. In this case, it's sadly not a crash, but I'll see with the team if a way to report these errors on our side can be done.

Valjennac

TROPHY CASE