#6942 closed defect (wontfix)
Crash in multiplayer game after consistently lowering FPS.
Reported by: | Beedell, Roke, Julian Lockhart | Owned by: | |
---|---|---|---|
Priority: | Should Have | Milestone: | |
Component: | Core engine | Keywords: | |
Cc: | Patch: |
Description
Of note is that this was a multiplayer game. The FPS had slowly lowered as the game progressed, to 17 FPS at times, despite both participants having very capable GPUs (1 x XFX AMD Radeon RX 5700 and 1 x AMD Radeon 7900 XTX). I don't know why the FPS lowered to such an extent, but if this Reddit comment:
Put a Max unit cap on the game. This has been a known issue that an enormous number of units can crash the game.
...is to be believed, then it might have been because each of the 4 nations in the game had approximately 2 000 troops.
Attachments (5)
Change History (7)
by , 7 weeks ago
Attachment: | interestinglog.html added |
---|
by , 7 weeks ago
Attachment: | 0.0.26.zip added |
---|
by , 7 weeks ago
Attachment: | userreport_hwdetect.txt added |
---|
by , 7 weeks ago
Attachment: | system_info.txt added |
---|
by , 7 weeks ago
Attachment: | mainlog.7z added |
---|
comment:1 by , 7 weeks ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 7 weeks ago
Milestone: | Backlog |
---|
From the logs, I can see you played with unlimited popcap and at least one of the laptops was on Windows. If you did have 4000 units in the game, you're playing with more units than most team games that have usually 150-200 max pop so 8 * 200 = 1600 max units on screen.
Since you played on Windows, you're limited to 4GB of RAM since the application is 32bit. That many units is very likely to get out of memory errors.
We currently don't support this. I'm closing this ticket as won't fix, because it's unlikely we'll support that many units soon, and the only thing that will help a bit is #2611 which will allow you to use all your RAMS.
The JavaScript part of the game is single threaded, so this is probably why you got a huge performance loss in the end, because computing all the data took too much time.
In the future, you might also attach the replays. :)
Unrelated but from your interestinglog.html : WARNING: Wrong MSAA sample count: msaa16. That's because AMD gpus only support up to x8