Burst fire mode

MWGemini · Nov 16, 2003

Hello everyone,

This is my first post to this particular forum, however, I used to frequent the mapping forums before my time was sucked away from me.

I have recently begun trying to teach myself uscript, and although I am learning, it is a much slower process than I had hoped for.

A former member of my team created code for an assault rifle for a tc/mod we are making, and I have been trying to fix the code for about the last week.

Thanks in great deal to Madnad, I have come extremely close to getting everything working. My only stopping point now is a fire mode.

The weapon in question has three fire modes, single shot, 5 round burst, and full auto. I have been unsuccessful in getting the burst mode to work properly. The closest I have come fires 5 bullets, but at such a high rate of speed that it is more like a shotgun than a automatic weapon. I believe this to be caused by the for loop in my ModeDoFire() function, but I have been unable to find a better way of doing it. I am currently trying to get a tick function to work, but I just don't know how to do what I am trying to do.

My current idea is to enable tick in ModeDoFire() and then fire the bullet in Tick() if deltatime is >= 0.15 (firerate), but I do not know how ot make the bullet fire there, and I'm not sure how MDF() and Tick() interact.

This weapon is supposed to fire 5 rounds per click, and i alreayd have bWaitForRelease = true.

If anyone can point me in the right direction, I would greatly appreciate it. I do not want anyone to write my code for me, but code examples of how to implement this would greatly help.

Thanks in advance to anyone who can help me.

Mike Winters

Kuhal · Nov 16, 2003

Without a doubt you should do the burst mode through the tick event. Definitely on the right track there however I have never made a weapon - just mutators and game type mods thus far

Cheers

Mr Evi1 · Nov 17, 2003

A Timer in the WeaponFire class would seem like a good idea. Easier than doing it in Tick.

MWGemini · Nov 18, 2003

Mr Evil- I wrote you an email regarding your reloading weapon code that you (I believe) posted to the Wiki. Have you made a decision regarding that yet? I'm holding off on re-writing my weapon code until I hear from you.

On a side note, is it 'legal' to have two timers running in a class? Right now, the code has a timer for reloading, and I have not yet tried adding a second timer to control the fire rate.

Thanks,

Mike

(v)adOnion · Nov 19, 2003

There is only one timer event per class. If you really want burst fire use states.

MWGemini · Nov 19, 2003

Yeah, I have heard that states would be ANOTHER way of doing what I am wanting to do, but I haven't been able to find much in the way of tutorials about what states are (which I already am a little familiar with) and more importantly, how to code them. Do you know of one/any?

Thanks,

Mike

SlayerDragon · Nov 19, 2003

MWGemini said:
Yeah, I have heard that states would be ANOTHER way of doing what I am wanting to do, but I haven't been able to find much in the way of tutorials about what states are (which I already am a little familiar with) and more importantly, how to code them. Do you know of one/any?

Thanks,

Mike

Using a state is really the only way to accomplish what you want. States allow latent functions - you can actually have time pass in states! $\o/$

I did this a while ago with some weapons I was working on. The Wiki has info on states.

http://wiki.beyondunreal.com/wiki/State

http://wiki.beyondunreal.com/wiki/UnrealScript_Language_Reference/States

(v)adOnion · Nov 20, 2003

In states you can use the sleep command - the rest is up to your imagination

MWGemini · Nov 20, 2003

Thanks guys, I will look into this hopefully tonight or tomorrow. The code I have now, I have a timer, but it doesn't seem to be delaying the shots at all, so I'm going to try my hand with states and see what I can do with that.

Mike

Tynan · Nov 20, 2003

Basic idea of what might work:

Code:

state BurstFiring
{
    ignores ModeDoFire;

    Begin:
    Fire();
    sleep(0.15);
    Fire();
    sleep(0.15);
    Fire();
    sleep(0.15);
    Fire();
    sleep(0.15);
    Fire();

    GoToState(none);
}

My exact syntax might be a bit off.

MWGemini · Nov 20, 2003

Well, this has not been a very productive evening for me. In the code I have tried, I have tried timers, states, and even multiple commands. Nothing has worked.

I have come ot the conclusion that something in weaponfire's event modedofire is causing all the bullets to be fired simultaneously, because when I have tried do this loop, the timer (or state code) is not called until after all bullets are fired, which is not what it should be doing.

Code:

class AR_Burst extends AR_Fire;

event ModeDoFire()
{
    local int i;
    for (i=1;i<=BurstLength;i++)
    {
        super.ModeDoFire();
        //GotoState('BurstPause');

        //log("FireRate = "@firerate * 4);
        SetTimer(FireRate * 4, false);
    }
}

state BurstPause
{
Begin:
Sleep ( FireRate  * 4 );
log(firerate * 4);
GotoState('');
}

function Timer()
{
log("Timer has been called");
}

defaultproperties
{
BurstLength=5
}

This code is an extension of ar_fire, which extends reloadinstfire, which extends instantfire, which extends (obviously) weaponfire. The ONLY classes that have an event modedofire in the list I just typed is weaponfire and ar_burst. AR_Fire does not override or extend the event modedofire, but just uses the default fire function defined in weaponfire.

I have tried asking several people on IRC as well, to no avail.

If anyone has an idea as to why this is happening, or how to override weaponfire's modedofire so that it WONT fire all bullets simultaneously, I would greatly appreciate it, because I have run out of ideas. As you can see from the code above, I would *LIKE* for the burstlegth to be altered via one variable, and used in a loop, but if that is not possible, then so be it.

Thanks,

Mike

EvilDrWong · Nov 20, 2003

Code:

class BurstFire extends InstantFire;

event ModeDoFire()
{
	GotoState('Burst');
}

state burst
{
Begin:
	Super.ModeDoFire();
	Sleep(variable);
	Super.ModeDoFire();
	Sleep(variable);
	Super.ModeDoFire();
	GotoState('');
}

if that doesnt work ill eat my hat.

MWGemini · Nov 20, 2003

Thank you, EvilDrWong, that worked. By taking that a step further, I was able to put a loop into the state and still have the burstlength be a variable.

Apparently my error was in looping in modedofire, when I should have been looping in state code. I'm not sure i understand why the results are so different for what is essentially the same code.

But I'm sure I'll figure it out eventually.

Thanks again to everyone who has helped me muddle through this one, and especially to Mr Evil, for allowing me to use his reloading weapon code.

Mike

NickR · Nov 21, 2003

EvilDrWong: You should put that on the wiki. Very handy and simple piece of code you have there. Even I didn't think about doing it like that.

Tynan · Nov 21, 2003

Sleep does not work outside of state code.

You cannot have latent functions in the normal code. They all have to execute instantaneously. Only state code can have time-based events.

NickR · Nov 23, 2003

Tynan said:
Sleep does not work outside of state code.

You cannot have latent functions in the normal code. They all have to execute instantaneously. Only state code can have time-based events.

Yeah that's true. But most of us knew that already.

Tynan · Nov 23, 2003

I wasn't sure Gemini had realized this. He said,

"I'm not sure i understand why the results are so different for what is essentially the same code."

MWGemini · Nov 23, 2003

Yeah, I'm still not sure I completely understand it, but if my understanding is correct, the code I had would execute all the super.moddofire commands in the loop before ever calling the state code because state code is treated differently.

Thanks for helping to clarify that for me, even though I probably still don't fully get it.

Mike

Wozzeck · Jun 1, 2004

Bumping this back up top.

Can't seem to use "Sleep" with UT2004, will not compile. Worked perfectly for UT2003. What's going on here?

[SAS]Solid Snake · Jun 2, 2004

Where are you trying to use it? The correct syntax for this is only inside states and not functions.

Code:

state mystate
{
  function my func()
  {
    Sleep(); // A
  }

Begin:
Sleep(); //B
}

A will produce and error, B is the correct way to use it.

Burst fire mode

Adrenaline Junkie

New Member

New Member

Adrenaline Junkie

chroot /

Adrenaline Junkie

LLLLLLLLLLLLLLLLLADIES

chroot /

Adrenaline Junkie

Person

Adrenaline Junkie

Every line of code elevates you

Adrenaline Junkie

New Member

Person

New Member

Person

Adrenaline Junkie

New Member

New Member