Model attachments?

[MDave]

[MauveBib]

[MDave]

[Urre]

[MDave]

[Urre]

Surely.

Spawn two entities, one for player, another for weapon. In the player's postthink code, do a setorigin on the weapon model to the players origin, and after that make it have the same .angles and same .frame as the player.

Now the tricky part:

All weapons must have the same amount of frames as the playermodel, with the weapon positioned to the players hand, properly aligned and everything, each frame. That takes a little work, but if you're familiar with QME, it shouldn't be hard at all.

This makes the weapon follow the player around, and look as if the player is holding it properly no matter the animation.

[Urre]

[Dr. Shadowborg]

[MDave]

[daemon]

an alternative that i've been messing with is to load up your player model in QME and map the offset and angles of where the weapon would be for each frame straight into qc. tedious, but you don't have to animate your weapons. you'll also have to give the weapon an avelocity to interpolate it if you desire smooth animation. once this is done, you can make as many single frame weapons as you want to attach to the player w/o having to do much work.

[ShoTro]

[daemon]

[ShoTro]

[jim]

I have some questions about them too. I've made my models use a lot different attachments and some attachments have attachments too. One character model has total: 4 attachments and 6 subattachments (attachments having attachments). So seeing one character like this brings 11 entities to the screen at once...

Are they going to eat a lot performance?

[leileilol]