Collision with player with PSK

#1 The psk does it's own 'on ground' physics checking. The box needs to be a 'platform' for the playable to be able to jump on it or it won't be detected as 'ground' the player can land on.

#2 I tried that but then the object loses all physics properties???

#3 You may well need to create a custom platform type or mess with the psk code. 'platforms' with physics properties is something that is on my list, but I haven't got to it yet so I'm afraid I can't really offer anymore advice than that at the moment.

#4 hmmm I'm wondering what the reason was to not just make the payer a regular physics object in the platformer kit. Seems weird to cut out all physics object interaction? I cant really see a reason why someone would have done this but I'm going to dig into that part of the code this weekend a bit so maybe I'll find out :S

#5 ActorComponent._updateOnGround() is a good place to start.

#6 So been looking into this more... And I still cant figure out why when applying a force to a platform it doesnt move at all :(

#7 In SolidPlatform::_OnRegister()

if (_platform.Physics != null)
    _platform.Physics.InverseMass = 0;

This sets the object as immovable.

#8 My guess is you are trying to create a block you can push around, and stand on, is that correct? I'm not sure thats a default behavior, you'd have to mess around a bit to get something to do that. Platformer physics is totally different then normal physics, but most of what the platformer physics does is ripped right out of normal physics operations, so the solution could be as simple as setting the OnCollisions for your box properly, maybe come up with a custom on collision, or extend the "solid platform" then set the type properly, perhaps? But I don't know, you'll have to mess around with it a bit.

#9 well I added a new variable to the solidPlatfor class called hasPhysics

and I wrapped the the stuff Duncan mentioned in an if statement

if (_hasPhysics == false)
            {
                _platform.Collision.CollidesWith = PlatformerData.PlatformTriggerObjectType;

                if (_platform.Physics != null)
                    _platform.Physics.InverseMass = 0;
            }

This seems to be putting me in the right direction. But it seems like the player still kicks it around like hollow ballons even if I crank up the mass. I guess its because the Actor class updated hte players position directly with the X and Y instead of moving it around by applying force to the actor?

Thats my guess anyways. Not 100% sure how to tackle that yet.

I really am digging torqueX though. After I get this and 2 more small things working I can start dominating the level editor :D

#10 Hmmm bit of a correction to my last post. Seems like objects that have the ResolveCollision set to rigid are the ones that dont seem to behave right when interacting with the player. The other ones seem to be acting more like expected? Now I'm confused haha maybe becauses it late :S

#11 Oh yeh and Will sorry I guess I didnt answer your question haha Yes I'm trying to make pushable boxes aswell as pillars that you can push over.

#12

_platform.Collision.CollidesWith = PlatformerData.PlatformTriggerObjectType;

That line of code is interesting.. I think you want to see if it collides with the player.. I think I have a solution for you. This might take some fiddling around to get it right.. I would do it by only modifying the player... Heres a snippet of code I use to check the normal of the collision... you can perhaps use something similar to this to tell if the colliding object how you want it to behave.

public virtual void ActorHitWall(ActorComponent actor, T2DCollisionInfo info, float dot) 
        {
            if (Math.Abs(info.Normal.X) > Math.Abs(info.Normal.Y))
            {
//possible some code here
//such as if "player hitting "B" " and to left. move block right, if player hitting B and to right, move block left, etc"  you can tell if you are left or right, if the normal.X is pos or neg.
}

              
        }

#13

Quote:
the player still kicks it around like hollow ballons

Try implementing your own resolve collision - in there you can take account of the object's 'weight' yourself. You can copy and modify the existing collision resolve functions as a starting point.