Floating Weapons - Is it Possible? Created 7 years ago2017-01-07 22:50:08 UTC by twitch1

Is there a way to make weapon entities float or even spin?

NVM, I think I figured it out. func_wall_toggle and a trigger. Wish there was an easier way though.

But can you make a model spin/rotate constant?

Spawn it on an invisible func_rotating?

Without mods its quite a struggle but if its a mod it could easily be animated or even coded

Thx guys. Yeah, not a mod, just vanilla HLDM. There are amxmodx server plugins that do what I need but I can't pack that up with a map release.

you can make a floating weapon with a trigger_push

W-models have a special flag for rotation inside model itself, but I don't remember if it works for GoldSource properly, or only for Xash3D. I can check this later, if needed. But, anyways, it's a model's property, not an entity's setting. So it will work for custom models only.

i guess entities of weapons are coded for not to use model sequence from w_ models. but you can include rotating versions of w_ models, you can use them with another entity.

for example make an animated rotating "w_9mmar" model, and name it "9mmar_rotating" and use it with a "cycler" entity. and add a trigger for equip.

http://twhl.info/tutorial.php?id=64

i found this, i guess this is about adding a model key that can be picked from the ground.

but sadly i dont have any idea about posibility of deactivating model entity after equipping.

@hfc : trigger_relay (KillTarget) or env_render

I remember some key values that do exactly this thing. It at least works in CS.

gravity: 0.0000000001
avelocity: 0 360 0

Set these with SmartEdit off.

holy shit, vluzacn himself with his secret knowledge. seems like hl has no boundries

wait what the hell vluzacn is a member here

To add to vluzacn's suggestion, this is effectively a list of all entity keyvalues that you can set manually: https://github.com/ValveSoftware/halflife/blob/5d761709a31ce1e71488f2668321de05f791b405/dlls/util.cpp#L200

This function handles them: https://github.com/ValveSoftware/halflife/blob/5d761709a31ce1e71488f2668321de05f791b405/dlls/util.cpp#L1986

The types under the "default:" label are not supported. So if it's a string, a number or a position/angle, you can set it.

Be careful though, not all keyvalues will be handled properly and some may be overridden by entities.

Vulcan's idea worked but map crashes when you try and pick up the weapon. Looks awesome... wish it worked

many years ago i found something similar by vluzacn, a "controller" key with some weird big integer value to use on cycler_sprites for models of characters, like the monster_hev_dead or something to make the torso and head centered because by default its all twisted to one side

@twitch1

i guess weapons cant picked when midair. they should hit ground for this.

i encountered several times,

same thing happens when a monster drops his gun to inside of a wall, the guns slowly falls and rotates in solid wall, if gun hits the ground after falling in that solid brush, then it is posible to pick up.

if i recall correct this thing also happens when monster drops his gun into his collision hull. you have to wait until dying sequence is over to get his weapon.

@Bruce:
The controller keyvalue is actually a list of 4 numbers, and controls the bone controllers of the entity's model. It's stored as an array of 4 bytes, which are unsigned 8 bit integers: https://github.com/ValveSoftware/halflife/blob/5d761709a31ce1e71488f2668321de05f791b405/engine/progdefs.h#L120

If you want to set such a value, you'll need to convert the decimal value to the unsigned integer representation first, then offset those so it's in the right position in the array. You'll probably have to compute and set the values for the other controllers as well, unless they're unused for the model.

@hfc:
That's because the Touch method for weapons is only set once it falls on the ground: https://github.com/ValveSoftware/halflife/blob/5d761709a31ce1e71488f2668321de05f791b405/dlls/weapons.cpp#L486

Would there be some way to have it touch the ground then be teleported/pushed/etc. to where it needs to go? Or would that just deactivate it again?