InsideQC Forums

I was thinking.. maybe, before
Add a makevectors, using as paramater your hand bone angles. That should orient correctly your weapon

first of all, thanks for all these csqc models tutorials, really appreciated! For the VWEP part, I humbly think that the only correct method should be be the #1, because #2 is really unefficent: I mean, in this case, you'd have 2 skeletons doing the same thing! I think ...

Hi all. [EDIT: 'VWEP' is short for ''visible weapon'. It refers the weapon you see in *other* players hands. I'm not sure if it's the 'standard jargon', because I didn't see any definitions anywhere they have been discussed. More ...

https://www.youtube.com/watch?v=Uq-jIj058FU

No MOVETYPE_FOLLOW. No vwep or attacks besides the kick, though

Hello, I was trying to get the vwep (visible player weapon) models to work via qc. The engine I used is DarkPlaces, but the qc code does not need dpextensions. I think it will work with any engine, as it doesnt make use of viewmodelforclient ...

... a bunch of effects on. All available vid resolutions worked with proper graphics scaling and fov. Water refraction looks incredible with much less vwep smearing and fps cost than previous build. Reflections should suck fps down to 2 then die but does not. Not much fps hit. Only issue is items popping ...

Very cool. Can motion blur be off for vwep? Or is post-process?

... etc. Also, I think it was the first time QF's Q2 was compiled for 64 bits. Anyway, it looks like the tools aren't properly separating the vwep from the model. Also, not being able to specify paths just sounds bogus as that seems to have been one of the main points of Q2's format changes ...

The IQM pipeline experiment of making vweps along with the player model has proven to be a failure http://leileilol.mancubus.net/crap/chars8.gif Even worse when I can't define skin paths explicitly at any part of it, so I have to drag my PCX's ...

... mesh that does have a separate material/UV. Just wanted to see how it was handled by default. Typically that would be exported as a separate mdl (vwep), anyway. Blender simply plastered the UV on top of the 'primary' texture (determined by the first UV selected I suppose). It's easy to see how ...

... model. Vweps look weird because they're all on at the same time. This is what it looks like in Blender, and then in Quark after export. Only one vwep was selected for export, and it adopted the image from the first mesh. Normally it would be exported separately, anyway. http://qbism.com/chan/src/13444821388.jpg ...

... done multiple meshes in Wings3D and MS3D, but they were all mapped onto the same texture. Guessing that doesn't help for exporting a Q3 model + vwep. Regarding export of multiple meshes would CTRL-J work in Blender (join meshes)? So far I can't tell if it "really" combines them or ...

leileilol wrote:really overdone muzzleflashes

q1 is very jelly of q3 acurately-located muzzleflashes. Maybe can do w/ vwep mod.

it would be cool to see a mod which helps you find cordinants sorta like the one for the vwep mod.

Build 53 - runs faster, colored lights (.lits, models, vwep, dynamic) http://qbism.com/nexus/wp-content/uploads/2012/01/qbismS8_0053.zip http://qbism.com/nexus/wp-content/uploads/2012/01/qbS8-idmap-lit18.gif http://qbism.com/nexus/wp-content/uploads/2012/01/qbS8-idmap-lit04.gif ...