[pTu]

Hello

How can I use in plugin weapon or hat models?

If i want use custom or prop model use my code:

PHP Code:

    #define MDL_GIFT "models/props_halloween/halloween_gift.mdl"
    new ent = CreateEntityByName("prop_physics_override");
    SetEntityModel(ent,MDL_GIFT);
    DispatchKeyValue(ent, "StartDisabled", "false");
    DispatchSpawn(ent);
    TeleportEntity(ent, g_pos, NULL_VECTOR, NULL_VECTOR);
    //SetEntityMoveType(ent, MOVETYPE_NONE);
    //DispatchKeyValue(ent, "ExplodeRadius", "100");
    //DispatchKeyValue(ent, "ExplodeDamage", "300");
    //SetEntProp(ent, Prop_Data, "m_takedamage", 2);
    AcceptEntityInput(ent, "Disable"); 


I don't know how to use weapons or hat models from vpk.

[Powerlord]

Well, for one you can't really create a weapon or hat directly... you need TF2Items for that. And Valve makes items you don't own invisible.

I've never tried changing the model on an existing weapon or hat/misc, though.

[napalm00]

Originally Posted by Powerlord I've never tried changing the model on an existing weapon or hat/misc, though.

SetEntityModel won't work and neither iModelIndex, Valve patched it about two years ago still (after Kemsan released it here).

[asherkin]

Originally Posted by Powerlord Well, for one you can't really create a weapon or hat directly... you need TF2Items for that. And Valve makes items you don't own invisible. I've never tried changing the model on an existing weapon or hat/misc, though.

This thread is solely about using the models independently (as the example code shows, with a standard prop_physics_override), creating items has nothing to do with it.

[friagram]

iModelIndex does work, just not reliably.

Dont setentitymodel, dispatchkeyvalue model, and solid...
Also dispatchkeyvaluevector origin and angles, rather than teleportentity.

Disable input is not what you need..

You should do like... Activateentity, and mabye sent an inout to disable motion if you want the physprop to be stationary.