defrag.cfg | 2.5
thx for answer ilca but i don't know what the hell you are talking about .. i will try to copy PHYSICS_DOUBLE_JUMPS | PHYSICS_RAMP_JUMPS in
else if ($xp_promode == 1) { $xp_physics = 3;
thx for answer ilca but i don't know what the hell you are talking about .. i will try to copy PHYSICS_DOUBLE_JUMPS | PHYSICS_RAMP_JUMPS in
else if ($xp_promode == 1) { $xp_physics = 3;
should be like this:
$xp_physics = PHYSICS_CONTROL_FORWARD | PHYSICS_CONTROL_SIDEWARD | PHYSICS_RAMP_JUMPS | PHYSICS_DOUBLE_JUMPS;
or
$xp_physics = PHYSICS_CONTROL_FORWARD | PHYSICS_CONTROL_SIDEWARD | PHYSICS_CONTROL_STOP | PHYSICS_RAMP_JUMPS | PHYSICS_DOUBLE_JUMPS;
i'm not sure about PHYSICS_CONTROL_STOP flag, it's set in cmpa cfg, but it's not set in the original defrag.cfg: '3' means PHYSICS_CONTROL_FORWARD | PHYSICS_CONTROL_SIDEWARD.
Example : for pure rules on DeFRaG, /pmove_fixed must be set to "1" and /pmove_msec must be set to "8"./pmove_fixed - Typically the player physics advances by small time periods. When this command is enabled, all players will use fixed physics, the time between two periods of physics will be the same for all players. The length of time between two periods of player physics can be set with the variable /pmove_msec. Enable these commands to make all players physics independent of players framerate.
What is the link between \pmove_fixed "1" and allow overbounces?
The link? Well, overbounce is an physics-bug and it just works if when the fix is disabled. Haven't u left this place actually?
Btw what a problem to play in original defrag? Or to play in ql? Why to make this cfgs for e+?
why not? why u play railonly in e+?
New version 2.4:
Now compatible with 2.2b
thx mate.. wujuu..
thx ilca too for help
Btw what a problem to play in original defrag? Or to play in ql? Why to make this cfgs for e+?
qlive cfg??? instagib cfg??? e+ is based too in another mod excessive ovekill(mr.pants)
No, because i havent updated it yet