UT99.org | Unreal Tournament Community

nogardilaref wrote: As Jack said it's probably something not reset properly in terms of physics, either the state or even the Velocity, so the player keeps "jumping" or "falling" on an immediate respawn.
So one thing which comes to mind is to simply reset the player Velocity to vect(0,0,0) on respawn. Perhaps there are other variables here at play which I am not remembering about, but this might do the trick.

sektor2111 wrote:nogardilaref mentioned that in this engine physics are flawed.

nogardilaref wrote:I guess everyone missed my post?

nogardilaref wrote: As Jack said it's probably something not reset properly in terms of physics, either the state or even the Velocity, so the player keeps "jumping" or "falling" on an immediate respawn.
So one thing which comes to mind is to simply reset the player Velocity to vect(0,0,0) on respawn. Perhaps there are other variables here at play which I am not remembering about, but this might do the trick.

Was this even tried and simply didn't work, or was it just overlooked?

sektor2111 wrote:How I would try to solve this ? By logging physics and velocity in a moment.
In this "modifyplayer" I would spawn a... sort of actor for 50 ms owned by player.
At end of life, actor will log velocity of owner and physics depending on environment... Else actor can live more or less time, telling what was going on with player.

By knowing that player has a sudden Z velocity, you can drop it to 0 zero on z axis = no more jumping.

JackGriffin wrote:Here's the base code for respawning players

Code: Select all

// Restart a player.
//
function bool RestartPlayer( pawn aPlayer ) 
{
    local NavigationPoint startSpot;
    local bool foundStart;

    if( bRestartLevel && Level.NetMode!=NM_DedicatedServer && Level.NetMode!=NM_ListenServer )
        return true;

    startSpot = FindPlayerStart(aPlayer, 255);
    if( startSpot == None )
    {
        log(" Player start not found!!!");
        return false;
    }   
    foundStart = aPlayer.SetLocation(startSpot.Location);
    if( foundStart )
    {
        startSpot.PlayTeleportEffect(aPlayer, true);
        aPlayer.SetRotation(startSpot.Rotation);
        aPlayer.ViewRotation = aPlayer.Rotation;
        aPlayer.Acceleration = vect(0,0,0);
        aPlayer.Velocity = vect(0,0,0);
        aPlayer.Health = aPlayer.Default.Health;
        aPlayer.SetCollision( true, true, true );
        aPlayer.ClientSetLocation( startSpot.Location, startSpot.Rotation );
        aPlayer.bHidden = false;
        aPlayer.DamageScaling = aPlayer.Default.DamageScaling;
        aPlayer.SoundDampening = aPlayer.Default.SoundDampening;
        AddDefaultInventory(aPlayer);
    }
    else
        log(startspot$" Player start not useable!!!");
    return foundStart;
}

Like I posted before I think they accounted for everything with the exception that the physics state isn't being reset. If you died in the air and didn't run the subroutine of Landed then your physics was never changed from PHYS_Falling. Respawning might carry an incorrect value for physics now, especially if the spawnpoint is raised some and the player doesn't teleport in touching anything. Since the spawning player is detached from the ground and in the falling state the engine may be confused and think he is actually jumping and apply the acceleration.

		aPlayer.SetPhysics(PHYS_None);

JackGriffin wrote:I've posted at OU and MasterKent responded. Can someone make a quick demo vid of the problem I can post there? I don't have anything BT installed at all. You don't need any production values or anything, just as simple a demonstration as you can toss together that shows the spawnjump bug.