Got the idea from ne_ruins mod, and blocked some models. Im not really sure how to setup a camera to simulate 1st person view.

http://i.imgur.com/p091p.jpg
http://i.imgur.com/qlPcq.jpg

One is just random, and another one based on this concept http://gamersblock.net/gamefluid/wp-content/uploads/2011/05/shotgun2a_001.jpg 

those are pretty cool man... should try to get them skinned and such.

for positioning, just grab one of the regular gun models and export it as a dxf file. then, in your editing software, just import the dxf and match your gun to it and then get rid of it when you've got the right position. 

something like this
http://i.imgur.com/MgS2q.jpg 

Time for an all-shotgun Quake with single- up to eight-barreled shotguns. 

pretty cool, relatively hi-poly for Quake though. Compare to vanilla shotguns. 

but wizmet never fails
http://i.imgur.com/HSHTZ.jpg 

tripple ss is ~760 poly 

i want one!!! 

I fight you for it!

That looks great. 

A scrag is only about 150 tris :) 

You don't make small maps with 200 r_speeds only because id's levels are like that. 

that tri-barrel looks great! i'm not a fan of the skin though. i'd rather see it match with the other guns (brown and blue metal).
nice mesh though! 

What my comment was trying to get at is:

If you want to use it together with the vanilla weapons, there will be a visible difference in polycount.

Maybe that is more understandable. 

I made a fuel chunk, and I'm a little surprised about it's behaviour. In Qmle it appears alright, but I'm doing something wrong I think. Although its returning state looks well damaged, I ment something like its last frame would participate on the first one.

So what in Qmle looks like:
http://members.home.nl/gimli/plug.gif
shouldn't behave like:
http://members.home.nl/gimli/plog.wmv

Maybe I'm not keen with qc.


$frame 1 2 3 4 5 6 7 8 9 10 11 12 13 14

void() plug_stand1 =[ $1, plug_stand2 ]{};
void() plug_stand2 =[ $2, plug_stand3 ]{};
void() plug_stand3 =[ $3, plug_stand4 ]{};
void() plug_stand4 =[ $4, plug_stand5 ]{};
void() plug_stand5 =[ $5, plug_stand6 ]{};
void() plug_stand6 =[ $6, plug_stand7 ]{};
void() plug_stand7 =[ $7, plug_stand8 ]{};
void() plug_stand8 =[ $8, plug_stand9 ]{};
void() plug_stand9 =[ $9, plug_stand10 ]{};
void() plug_stand10 =[ $10, plug_stand1 ]{};
//void() plug_stand11 =[ $11, plug_stand12 ]{};
//void() plug_stand12 =[ $12, plug_stand13 ]{};
//void() plug_stand13 =[ $13, plug_stand1 ]{};

void() info_plug =
{
precache_model ("progs/plug.mdl");
self.solid = SOLID_BBOX;
self.movetype = MOVETYPE_NONE;

setmodel (self, "progs/plug.mdl");

setsize (self, '16 16 16', '24 24 24');
self.think = plug_stand1;
self.nextthink = time + 0.1;
};
 

first, i noticed you aliased the frames to numbers.
the point of aliasing is to assign a name to a frame number, so in this case, you don't need to do anything at all:
void() plug_stand1 =[ $1, plug_stand2 ]{};
becomes:
void() plug_stand1 =[ 1, plug_stand2 ]{};

but on to your actual question, this is the frame interpolation happening.
to fix this, you will need to create an animation where the gears complete a full rotation in order to get around the problem. 

also, if you're just going to animate frames in a loop this way, you may find it easier to do this:

void() info_plug_think =
{
self.frame = self.frame + 1;
if (self.frame > 9)
self.frame = 0;
self.nextthink = time + 0.1;
};

void() info_plug =
{
precache_model ("progs/plug.mdl");
self.solid = SOLID_BBOX;
self.movetype = MOVETYPE_NONE;

setmodel (self, "progs/plug.mdl");

setsize (self, '16 16 16', '24 24 24');
self.think = info_plug_think;
self.nextthink = time + 0.1;
};


does the same thing without needing the big frame macros. 

if it's just going to loop forever with no state change or reaction to game events, then just make it a static entity and use a framegroup to cycle the frames. 

I aliased the frames to numbers, because I have also a waterfall static entity.
Earlier I encountered problems when I had two of them with only framenumbers.

The shorter script gave an error in proqcc.
*** r0ta.qc:10:info_plug redeclared

@metlslime- you said earlier on Inside 3D. Still I'm such a noob I would type staticentity in the console and ask myself how.
Qmle or FimG don't support framegroups.

Maybe I should take the oppertunity to leave it this way. Frame interpolation, learned something new. 

The shorter script gave an error in proqcc.
*** r0ta.qc:10:info_plug redeclared

This error message means that the function info_plug has more than one definition. Look through your code and remove the original one, leaving just the one necros wrote.

Also if you right click on an animation in Qme there's the option to "group frames for scene". This turns the animation into a framegroup. 

OK, so I downloaded QMe but I can't install it on Windows 7. The installer tells me it's not compatible with this version of windows and my dog is ugly and some other things.

I tried setting compatibility mode to Windows 95 but it sees through that ruse.

How do you install QMe on a modern computer? 

To know that as well...

I've heard that you can install it on an older machine, then just copy across the files. 

that must be it, because i have qme working on win7 here.

here's qme pre-installed: http://necros.slipgateconstruct.com/temp/qME.7z 

This is the recipe for what you want:

void() info_plug =
{
precache_model ("progs/plug.mdl");
setmodel (self, "progs/plug.mdl");
makestatic (self);
};

This will implicitly set it to frame "0", which, if you use a framegroup, will actually loop through all frames in the group on the client.

The only downside to this is that the object is not solid, but you can put a clip brush there if you want.

To make a framegroup in QME, right-click on the "scene" in the frame list, and choose "group frames for scene", The camcoreder icon will change and now be a camcorder with a tiny clock on it. This will now look like a single "frame" for quakec, and if it's the first thing in the file will be frame number 0. 

Thanks necros, that works! 

I had three scripts for models, but I'm surprised there are so many different ways to do it.

The second script indeed was my typo, as Preach suggested.
But the last one from metslime really does the job. Thanks!

I think my perception still tends to cinamatics than the maths of quakeframes.
I made an new animation with the weels turning round, but I remain with the outcome of a returning, blocking wheel.

Ah, my praxinosopic tention.