[Dragokas]

PHP Code:

        int entity = CreateEntityByName("prop_dynamic_override");
        
        if (entity != -1)
        {
            DispatchKeyValue(entity, "model", path_full_model);
            DispatchKeyValue(entity, "DefaultAnim", sAnimIdle);
            SetEntityMoveType(entity, MOVETYPE_NOCLIP);
            DispatchSpawn(entity);
            SetVariantString(sAnimDeploy);
            AcceptEntityInput(entity, "SetAnimation");
            ...
            SetVariantString("!activator"); 
            AcceptEntityInput(entity, "SetParent",client, entity, 0);
            SetVariantString("medkit");
            AcceptEntityInput(entity, "SetParentAttachment");
            ...
            TeleportEntity(entity, vOrigin, view_as<float>({0.0, 0.0, 90.0}), NULL_VECTOR);    
        } 


Parented to survivor.

Thanks.

[Lux]

A screenshot will help alot with showing the problem.

If it is what I think you mean that glow is clientsided if I remember right.

[Dragokas]

Sure, please.

[Silvers]

Afaik client side, not possible.

[Dragokas]

Thanks.

Even if I could control client side, I still dunno how to delimit glow between base model and parented model.

[kadet.89]

You could try prop_dynamic_ornament instead or use constraints. There is no constraint interface exposed to sp though, you would have to use Phys_constraint or Phys_keepupright:
https://developer.valvesoftware.com/...ys_keepupright
https://developer.valvesoftware.com/...hys_constraint
Or write an extension, see CreateFixedConstraint:
https://github.com/ValveSoftware/sou...cs_interface.h
That way excessive Phys_constraint / Phys_keepupright can be avoided

If you don't care about small lags, you could detach the model from the player and correct the position in playerthink hook. If you set the coordinates and the velocity to be equal to the players every gameframe, it should look like parented entity but without the glow effect

[Silvers]

Originally Posted by kadet.89 If you don't care about small lags, you could detach the model from the player and correct the position in playerthink hook. If you set the coordinates and the velocity to be equal to the players every gameframe, it should look like parented entity but without the glow effect

Maybe if you're a listen server without any clients. With client prediction and internet lag I highly doubt that would work smoothly, you would notice the prop isn't attached.

[Dragokas]

It was the way how original parachute plugin is created, and I didn't like that small lags, not smooth and more CPU consuming. Not our way.

kadet.89, thanks for ideas, I will look into them a bit later.

[kadet.89]

Well, you attach the parachute to the player, what if you do it vise-versa?
I did such a trick for vehicle mode. The only problem that the parachute model should have player-like hitboxes. And trace attack on these hitbohes should be forwarded to corresponding player hitboxes.

The easiest way is to create a prop_dynamic / prop_physics with invisible player model and attach everything to it, but it implies that 2 entities will be used for the parachute instead of one.

Here is an example of a player to "prop_physics" attachment : https://youtu.be/uL8gV_ayTyw?t=116 For CS:GO it's the same

[Dragokas]

Wait, what? Attach player to parashute? Newer tried Shouldn't it broke everything related to movement, or ...
I don't quite understand relationship.

Lux has successfull examples on using "prop_dynamic_ornament" and "commentary_dummy" for player model.

So, what is relation? Attach fake player model to parachute? Than what to attach to player?
Do you think 1 additional (invis) model in chain will broke glow inheritance?

BTW, nice mod =)