InsideQC Forums

the problem with that is the wrapping of textures if the vwep model is too large. the method of assigning other models to one single player model via code is easier in my opinion(and more CLEAN). not only that, but it would be more annoying if an engine ...

how I did my vweps were basically in these steps. 1. load the player model. 2. import the vwep model(make sure all objects are attached). 3. make sure the model has the right scale size. 4. begin positioning. 5. after you're done ...

... take a bit to do. I noticed this player model holds the gun the whole time, if there will be effort into a real mod..I will most definitely make a vwep for it!

yeah, I've been busy with irl stuff. I still want vwep to be more vastly used in the quake community

... else...? Can't remember... Presumably I could do different visual weapons this way depending on the player's current weapon. You'd then have a vwep system that could be color moded with different effects for Quad, etc. Anyway, if I could dig up the mod maybe that would help someone..?

... weapon and not the player... hell even use client colors to change the colormap if you wanted. If you're playing first-person, then combine that vwep feature with .viewmodelforclient on a second model. Then you can do the same effects on the player's view weapon, and it looks damn cool. A bright ...

... .nodrawtoclient. Then you can make the model invisible to the user when he's in first person view. For standard quake, the player will see the vwep. Maybe that won't be bad if the weapon and view_ofs are positioned properly, though. Edit: Though you also have to worry about the effects of lag ...