f / TicksPerSecond

[Vasten100]

Hey ddnet, i tried some new tunezones and i recogniced that this here: (copied from Settings & Commands)
air_control_accel 1.5
ground_control_accel 100.0f / TicksPerSecond
and this here, somehow dont fits thogeter.

I think here is something wrong cause here:
air_control_speed 250.0f / TicksPerSecond
is / TicksPerSecond with _speed, and not with _accel (like in ground_control)
so I spwapped the parameters! and it works beter
tune_zone 1 air_control_speed 5
tune_zone 1 air_control_accel 3f / TicksPerSecond

I think you ask yourselfe why i edited the 1.5, thats simpe, cause if you are in air and move, then you have speed (ingame) 2, but normal you have 8 so i calculated and yeah... 5 is beter than 1.5
This Default settings are realy broken (I would change them): (copied from Settings & Commands)
tune_zone 2 air_control_speed 250.0f / TicksPerSecond
tune_zone 2 air_control_accel 1.5

this here are ok but not as fine as the normal tune, so i tried to improve them:
tune_zone 1 ground_control_speed 10
tune_zone 1 ground_control_accel 3f / TicksPerSecond

instead of this: (copied from Settings & Commands)
tune_zone 1 ground_control_speed 10
tune_zone 1 ground_control_accel 100f / TicksPerSecond

I dont realy understand for what this f / TicksPerSecond are, but they are somehow broken...

I would change the parameters to the bold marked text.

I hope its not too confuseing.

btw, testmap attached!

[deen]

Don't use the f and / TickPerSecond in the tunings. Just use a value, like 5. You can get the current values by typing tune_dump in F2.

[Vasten100]

then i would change them also in the Settings & Commands Section. or make a quote "do not use this" or so

[deen]

The Settings & Commands section is auto-created from the actual source code. Maybe I can fix something up.

Edit: Should be fixed now: http://ddnet.org/settingscommands/

[Vasten100]

nice, thank you.