чтобы после исполнения от первого, потом его же со стороны , с замедлениями, что бы насладиться успеть сложностью этюдов =D и фигурки же такие смачные, и со стороные опережающие все эти фишки пиздец смачно выглядят же, особенно с плазмаганом, выщак же беЗподобный!!!
That may be altered physics or an edited demo. DF shows pmove_msec 50 in that demo (which is equivalent to sv_fps 20 - the default value in baseq3). But there's g_sync 1 and pmove_fixed 0, so pmove_msec is ignored. Why is it set after all? That is strange. Normally, repetitive obs on such big heights are impossible unless you alter physics.
It could be that he is finding a new OB height by losing the height slightly by use of crouch and strafe, perhaps? taping into the new OB height by altering the first OB height ever so slightly.. or maybe he just disabled the 1-time property of OB, so i.e. altered physics as you said.
Crouching and strafing mid-air doesn't affect your vertical velocity in any way. They can affect your vertical velocity only if you're under water or have "flight" power-up. Also crouching can make you avoid hitting the ceiling sometimes, but that's beyond the point. "disabled the 1-time property of OB" -- actually normal VOBs are always a little bit lower than the original falling height. Like by a fraction of a unit or so. This is because of rounding errors in every frame. You can't notice this bu a naked eye, because there's step-up ramping anyway that lets you land on the same platform where you started. In order to disable the 1-time property you have to alter physics. It is possible to adjust physics settings in such a way that there are no rounding errors in player's Z coordinate, and then the height of the VOB is equal to the starting height. And then you can bounce infinitely. But that's altering the physics, like I said.
![FreeStyle3 [df. ...]](/img/logo.svg){kind=logo}
