Open Bug 2002392 Opened 2 months ago Updated 2 months ago

Red Alert 2: Chrono Divide suggests "Firefox should be avoided"

Categories

(Web Compatibility :: Site Reports, defect, P3)

Tracking

(Webcompat Priority:P3, Webcompat Score:3)

Webcompat Priority P3
Webcompat Score 3

People

(Reporter: jrmuizel, Unassigned)

References

(Depends on 2 open bugs, )

Details

(Keywords: webcompat:platform-bug, webcompat:site-report)

User Story

platform:windows,mac,linux,android
impact:unsupported-warning
configuration:general
affects:all
branch:release
user-impact-score:40

Under Game Requirements on the home page:
"Web browser: Latest Google Chrome, Mozilla Firefox, Microsoft Edge or Safari (for good performance, Firefox should be avoided)"

Severity: -- → S3
User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 3
Priority: -- → P3
Depends on: 2002391

From Discord:

El Presidente:
Hi and welcome! While I haven't touched Firefox in more than a year, I can tell you what I remember. First, frame rate was considerably worse for me with many units on screen compared to Chromium-based browsers. This was purely webgl/gpu related. Second, there would be drops with large armies being commanded, which would be induced by high CPU usage. The game loop is single-threaded btw. I remember profiling and everything would just take much much longer than it would in Chrome on the same replay file. It's true that my code isn't well optimized to begin with in terms of memory and data locality, but on Firefox performance simply degrades faster and worse than on Chrome. On Chrome you'd have to play Rekoool to begin having problems or maybe play on a mobile phone with a lower CPU frequency. On Firefox, I would notice issues even on desktop. Last, OPFS performance was abysmal at the time that I last tested it (10x slower than Chrome). You can try the test page at https://use-strict.github.io/file-system-access/example/test.html and see what I mean.

See Also: → 2002429
You need to log in before you can comment on or make changes to this bug.