Encumbrance effect on combat running speed

[ScienceDiscoverer]

So, I couldn't find this info anywhere, so I tested it myself. Run between two trees on same map with 30.6 encumbrance and then 1.6 encumbrance and measured time with stopwatch. It turns out, each encumbrance point lowers speed by about 0.94%. Factoring in some errors in my experiment, it may very well be that each encumbrance point lowers speed by exactly 1%. This is quite interesting. Would be cool if this info was included in the tool-tip for encumbrance. To not leave players guessing.

[Passier Reis]

引用自 ScienceDiscoverer：

引用自 SpecialSnowflake：

We all talking about the same game build?

Well my original post was long ago, but I retested it on current build.

The beta build? Noted.

Thank you for your investigation. I agree that the devs should be more specific with the changes as well.

[ScienceDiscoverer]

引用自 ScienceDiscoverer：

The beta build? Noted.

Actually I'm not sure. I guess I didn't enable any beta settings anywhere, so I'm probably on release version of the game right now.

[Battenhall]

should update the starting post to reflect your most recent findings, great info to have.

[ScienceDiscoverer]

引用自 Varador：

should update the starting post to reflect your most recent findings, great info to have.

I kind of made haitus from the game, so mb in the future

[везнан]

引用自 ScienceDiscoverer：

I guess I would never receive an answer here... 0 info about this on the Internet too. So I had to use cheats to test it once and for all. Here is the results:

0 Athletics	| 70.3 E	| 22.5 s	| Tooltip: +0%
		| 0 E 		| 13 s
100 Athletics   | 70.3 E	| 24 s		| Tooltip: +6%
		| 0 E		| 9 s
161 Athletics	| 70.3 E	| 13 s		| Tooltip +10%
		| 0 E		| 9 s
318 Athletics	| 70.3 E	| 9 s		| Tooltip +20%
		| 0 E		| 9 s

Your test helped me prove something about the current code
this is the the formula for movement speed in the current version

public static float CalculateMaximumSpeedMultiplier(int athletics, float baseWeight, float totalEncumbrance)
		{
			return MathF.Min((200f + (float)athletics) / 300f * (baseWeight * 2f / (baseWeight * 2f + totalEncumbrance)), 1f);
		}

according to this, a 100 athletics naked build should have the same speed as a naked build of any higher athletics stat, which your test showed. and a naked build of 0 athletics should have about 2/3 the speed of a naked build with 100 athletics, which your test showed too.

[ScienceDiscoverer]

引用自 Vez'nan：

Your test helped me prove something about the current code
this is the the formula for movement speed in the current version

public static float CalculateMaximumSpeedMultiplier(int athletics, float baseWeight, float totalEncumbrance)
		{
			return MathF.Min((200f + (float)athletics) / 300f * (baseWeight * 2f / (baseWeight * 2f + totalEncumbrance)), 1f);
		}

according to this, a 100 athletics naked build should have the same speed as a naked build of any higher athletics stat, which your test showed. and a naked build of 0 athletics should have about 2/3 the speed of a naked build with 100 athletics, which your test showed too.

Nice, didn't expect this test to be so accurate