Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This happens because the engine uses FPS for damage calculation. Its a very old method. It would take a complete engine change to fix this issue, not exactly a simple task.
Also this game is console based, and most consoles even PS5/XBX still operate at 60 fps or lower.
In this case, it sounds like damage is caused by the speed of the projectile? Then fix that by scaling it with framerate instead. That means that not only is it doing more damage, but it's harder to get away from because it's faster. That's insane.
I've solved the problem for myself by setting my FPS at 30. But that's a really awful solution for the user.
Its not just damage taken/outbound affected its also physics. If you ran the new raid, the jumping platforms behave wildly at different fps's. At 30/60 behave as normal. At 120 still can be fine, but above that its either gonna toss ypu very fast, too high, or just drop you.
Keep in mind they are using a heavily modified version of the Halo Reach engine.