[ZooL]

Nice plugin, and really useful but I have little problems, but I think its TF2items,

First, If the weapon is a Non-Stock weapon, the weapon is invisible on other clients, but wasn't years before D:

Second, with your plugin the weapons are hold on the right of the hand D:





Someone got a fix for these issues ? or is it my server causing this ?

[MasterOfTheXP]

Originally Posted by Skyrider I assume none of the examples within the StarterWeaponPack.zip works? [...] Also, if you use "plugin" within the weapon config file incorrectly [...] it crashes your client.

They all should be working...do the HL2 weapons work for you? What about some other weapons which only use TF2Attributes, like the Denied Burial on Soldier?

I'd love to see that full client-crashing plugin config (or just the one crashing attribute) so I can figure out what's up. I've never really seen an attribute crash clients before...

[MasterOfTheXP]

I double-posted by accident, sorry!

Originally Posted by ZooL If the weapon is a Non-Stock weapon, the weapon is invisible on other clients, but wasn't years before D:

Indeed.

Second, with your plugin the weapons are hold on the right of the hand D:

That's a known "bug" which I shall add to the OP now.

Basically, the HL2 weapons are attached to the viewmodel in a way that isn't via bonemerging (because those models obviously weren't made to be attached to TF2 viewmodels) and unfortunately, having a different viewmodel_fov positions the weapon differently, even with the exact same coordinates in the viewmodel.

I've been meaning to see if I can math my way out of that one, but forgot to try doing that before putting out the beta Anyone else who feels like they can is more than welcome to try doing so.

[ZooL]

Originally Posted by MasterOfTheXP I double-posted by accident, sorry!Indeed.That's a known "bug" which I shall add to the OP now. Basically, the HL2 weapons are attached to the viewmodel in a way that isn't via bonemerging (because those models obviously weren't made to be attached to TF2 viewmodels) and unfortunately, having a different viewmodel_fov positions the weapon differently, even with the exact same coordinates in the viewmodel. I've been meaning to see if I can math my way out of that one, but forgot to try doing that before putting out the beta Anyone else who feels like they can is more than welcome to try doing so.

Oh so FOV is the problem D:

and about the invisible weaps, there's no solutions ???

[MasterOfTheXP]

Unless we can get Valve to be more lenient about custom models, nope.

Well, I wouldn't see it being too hard for them to at least allow the standard "unlockable" weapons to be visible, like, I dunno, Axtinguisher on Medic, if they just thought about it for a little bit.

[ZooL]

Originally Posted by MasterOfTheXP Unless we can get Valve to be more lenient about custom models, nope.

R.I.P. Visible custom weapons ...

[Oshizu]

There are still ways to get visible weps, it is quest up to you to discover
If you guys wouldn't be strict about such stuff i could share current progress

[404UserNotFound]

Originally Posted by Oshizu There are still ways to get visible weps, it is quest up to you to discover If you guys wouldn't be strict about such stuff i could share current progress

You're talking about that tool who uploaded that fixed visweps thing last month? I have that too. Decided I'd save a copy of it before he removed the download, luckily I got my hands on it.

[Drixevel]

Neat, this could be useful for a numerous number of things.

[ClassicGuzzi]

What about making a prop with the wep and parenting/attaching it to the player's weapon? (And maybe make that prop invisible for that player?)