Please clarify image states....

#1 stateName[x]

// The name of "this current" state

stateTransitionOnTimeout[x]

// the name of the state to switch to when the timeoutvalue elapses

stateTransitionOnNoAmmo[x]

// when we run out of ammo, the name of the state to go to

stateTimeoutValue[x]

// how soon to go to the next state

stateFire[x]

// if the state is a "fire" state

stateRecoil[x]

// the amount of recoil if applied

stateAllowImageChange[x]

// does this state allow us to change images

stateSequence[x]

// the sequence number for this state

stateScript[x]

// the script function to call for this state if any

stateEmitter[x]

// any active emitter for this state?

stateEmitterTime[x]

// how long do we emit for?

(As well as any more available ones)

Also, I see this used a lot, and I'm not quite sure what its doing. Things break if I don't properly use it though...
%obj.setImageAmmo(%slot,false);

// it sets the amount of ammo you have for a given image (usually weapon).


And finally, sometimes I need a bit more control over which state I'm currently in. Is there a way to set myself directly to stateName[x] for the next pass?

// there's probably a function to set the current state number.. havent looked at it that recently.

Phil.

#2 Could you post this as a resource? That would be very helpful.

#3

Quote:
Also, I see this used a lot, and I'm not quite sure what its doing. Things break if I don't properly use it though...
%obj.setImageAmmo(%slot,false);

// it sets the amount of ammo you have for a given image (usually weapon).

Phil, that's not correct. What that function does is set the Ammo state to true or false, so you know if you have ammo or you don't. But it has nothing to do with the amount of ammo. Basically setting this to false would change the state to NoAmmo, thus disabling any firing... setting it back to true would enable changing to the fire state again.
If you have something like this:

stateTransitionOnNoAmmo[2]       = "NoAmmo";

Then if you do setImageAmmo(%slot, false); when it gets to state "2" it will change to the NoAmmo state.
Hope that helps.

#4 Thanks everyone!

#5 Hmm, one more question... Do the statenames correspond with the animation names?

#6 Nope

#7 I'd like to control the states, Do you know to change with a keymap for example, change to another state ?

I'm actually working on a weapon reload C++ based..

Do you have any ideas ?

#8 Is there away to know what an obkect is in? I ask because we want to use the fire button to cause the weapon to deploy when the button is first clicked and then to fire everytime after.

#9 Is there away to know what an obkect is in? I ask because we want to use the fire button to cause the weapon to deploy when the button is first clicked and then to fire everytime after.

#10 Posting the same question twice, two hours apart, is not a wise thing. You'll get your answer regardless of whether you post more than once or not.

I think you can do this just by creative state machine design. The point of the state machine system is to make it so you don't need to deal with problems like this. :)

#11 Sorry about the double post, I have no idea how it happened. I only wrote it once.

#12 Where can I find a good write up on just how the image states process works, how it is structured, etc?