Changing turret rate of fire Created 15 years ago2009-03-25 12:03:41 UTC by The Mad Carrot

So i want to slightly increase the rate of fire of the turret and maybe the sentry as well.

I searched through its entire sourcefile (turret.cpp) and changed some if not all numeric values (NextAttack or whatever), but non of those changed seem to affect the turret's rate of fire.

Anyone know where the rate of fire is defined?

You could do it by decompiling turret model, then open qc file and edit the event points on fire sequence.

You mean this:

$sequence "fire" "fire" fps 150 loop {
{ event 5001 0 "51" }
{ event 5001 10 "51" }
{ event 5001 20 "51" }
}

None of those values change the rate of fire.

Make fps highter and it will move and shoot faster.

Wouldn't it only seem as if it shot faster but infact the gun would still use some part of another code to actually shoot. Isn't the change in the qc file just for the animation ?

Changing the fps from 150 to 300 didn't increased the ROF.

Wouldn't it only seem as if it shot faster but infact the gun would still use some part of another code to actually shoot. Isn't the change in the qc file just for the animation ?

Well, i tried editting numeric values in both the qc file and the turret cpp source file, but none of those values seem to change the ROF ingame.

I don't get it.

The first thing i tried was changing the 0.6 value in the Shoot function to something higher, but noo... :/ I could've sworn that that defined the ROF... Guess not.

void CTurret::Shoot(Vector &vecSrc, Vector &vecDirToEnemy)
{

FireBullets( 1, vecSrc, vecDirToEnemy, TURRET_SPREAD, TURRET_RANGE, BULLET_MONSTER_12MM, 1 );
EMIT_SOUND(ENT(pev), CHAN_WEAPON, "turret/tu_fire1.wav", 1, 0.6);
pev->effects = pev->effects | EF_MUZZLEFLASH;

}

You're looking at the wrong function. Shoot() doesn't handle timing, it just fires a bullet and emits a sound (that 0.6 defines volume of the shot sound).

Haven't tested this, but I think the easiest/hackiest way to achieve what you need would be to change

pev->nextthink = gpGlobals->time + 0.1;

located at the top of

[blue]CBaseTurret::ActiveThink(void)[/blue]

in turret.cpp to

pev->nextthink = gpGlobals->time + 0.05;

or a smaller value. Nextthink defines how often ActiveThink is called, which handles shooting, targetting, etc.

Alright.
I changed it to:

pev->nextthink = gpGlobals->time + 0.05;

And guess what? No change in ROF ingame. Then i tried:

pev->nextthink = gpGlobals->time + 8.0;

And that did'nt do squat either.

Hmm.. was pretty sure that would work. D:
Maybe it is model-defined? Human grunt ROF is afaik.

I decompiled the turrent and editted the qc file.

Nothing.

If I recall correctly bullet creation is shared between the server and client. Although, even if you just change it server-side you should still receive damage faster but not be able to see the bullets. Hm.

Oh, and I haven't hade the time to look at the shocktrooper yet, I'm so goddamn busy, sry.

No rush, chickenfist, but if you find the time to work on it, go for it.

As for the turret ROF, what do i do now?

Well, I still think you have to decrease the delay between thinks.
Are you sure it doesn't reset the nextthink in SpinUpCall() ?
If that doesn't work you could always write your completely own turret code that constantly fires.

I have no idea.

Writing my own turret code is out of the question im affraid.

Which mod is this for? I don't have a turret.cpp in the HL SDK (as far as I can see, anyway!)

However, I looked through the func_tank.cpp file on the theory that the concept was the same, and found that m_fireRate variable is actually fed in from the map itself (ie, the func_tank entity has a "rate of fire" value.) Does the same apply for turrets?

Just thinking out loud; obviously I don't have a turret to play with...

Edit because ... well, just because!

D'oh! Of course turret.cpp is in the single-player code (which I've deleted from my working copy of the SDK!) As far as I can see, the rate of fire of the turret should be controlled by the pev->nextthink line that Daubster pointed out. However, changing that delay time won't change the animation speed... But if it's not working ... dunno.