yes, FALSE is the same as MOVE_NORMAL, but let's be more explicit about the trace...

[xonotic/xonotic-data.pk3dir.git] / physicsNoQWBunny-XPM.cfg

diff --git a/physicsNoQWBunny-XPM.cfg b/physicsNoQWBunny-XPM.cfg
index db9c6179c0b4f8c5a471ff0c3d912761f0b53dc1..1beaeda7e893a0bf7d79f15d2fd004e48e4388f4 100644 (file)
--- a/physicsNoQWBunny-XPM.cfg
+++ b/physicsNoQWBunny-XPM.cfg
@@ -1,27 +1,27 @@
-// Nexrun tweaked to suit CPM
+// 2.0-2.4.2 physics minus QW-bunnyhopping-bug, faster onground accel, CPMA air control
 sv_gravity 800
 sv_maxspeed 320
-// CPMA: 320
+
 sv_maxairspeed 320
-// CPMA: 320
+
 sv_stopspeed 100
 sv_accelerate 15
-sv_airaccelerate 1
+sv_airaccelerate 2
 sv_friction 8
 edgefriction 1
 sv_stepheight 34
-// CPMA: 18
-sv_jumpvelocity 270
+
+sv_jumpvelocity 300
 sv_wateraccelerate 4
 sv_waterfriction 1
 sv_airaccel_sideways_friction 0
-sv_airaccel_qw -0.9146875
-// CPMA: 1
-sv_airstopaccelerate 6.5625 // matches strafe-stopping speed
-sv_airstrafeaccelerate 14
-sv_maxairstrafespeed 150
-sv_airstrafeaccel_qw -0.987
-sv_aircontrol 100
+sv_airaccel_qw -0.937
+
+sv_airstopaccelerate 3
+sv_airstrafeaccelerate 24
+sv_maxairstrafespeed 100
+sv_airstrafeaccel_qw -0.979
+sv_aircontrol 125
 sv_aircontrol_penalty 100
 sv_aircontrol_power 2.5
 sv_airspeedlimit_nonqw 0