but it's cog related.

You know when you have weapon cog, with a 1 second sleep in the middle and you don't hold the key down long enough, it stops the fire message.
What I'm talking about is if you use the call fuction to call a user defined message with a sleep in the fire message, you WILL have all sorts of problems. I don't know why or how it does this, but I wish I knew this before I started modifying my FD-31c burst fire section.

------------------
The Sniper Missions. Current project, The Sniper Missions

The Magician Saber System.

Couldnt in the fire message you start another module which fired the second 2 shots. Or doesnt that work?

I'm talking about when the fire delay is greater then the total sleep time.

------------------
The Sniper Missions. Current project, The Sniper Missions

The Magician Saber System.

Part of the evilness of Sleep. Try using Timers.

I' ve had similar problems. I also tried to implement a burst fire mode with 0.1 seconds between each shot, but I failed. The two things I tried were having a new message called in the fire message (was very buggy) and having an integer that stores the number of shots fired (firing was done in the fire message), then firing the rest of the shots in the deactivated message. But that didn't work as expected, too. It shouldn't be that hard, but I no longer need burst firemode anyway.

------------------
"Häb Pfrässe, süsch chlepfts!" - The coolest language in the world (besides Cherokee)

I did use timers. What I did was put the burst(s) in a 0 second timer and have it be done there. Works perfectly.

------------------
The Sniper Missions. Current project, The Sniper Missions

The Magician Saber System.

Wait, a zero second timer? did you have timers with a sleep message at the beginning? Doesn't that kind of defeat the purpose of a timer in the first place?

*whacks head in hole in wall that has been carved out by whacking head there*

Using the timers to escape the fire message, but still use it. In the cog with the timers, there is no sleep() in the fire message. That is really the only bug free way (except making it a semi-auto or single shot instead of auto) to do this.

------------------
The Sniper Missions. Current project, The Sniper Missions

The Magician Saber System.

Quite clever, I must say.

------------------
"Häb Pfrässe, süsch chlepfts!" - The coolest language in the world (besides Cherokee)

Thank you. But its nothing really. Unlike my friendly AI cogs. Now those toke something more.

------------------
The Sniper Missions. Current project, The Sniper Missions

The Magician Saber System.

[This message has been edited by Descent_pilot (edited November 17, 2002).]

I think because Sleep(); delays EVERYTHING in the cog, including other delays.

Not true. Sleep only pauses the current message. Other messages can be called in the cog and run during the sleep.


Timers > Sleeps.

Actually I think I've encountered instances when sleep affects other messages. I'm not certain its as simple as Sleep delay in activated only halts activated.

Maybe I'll find time to test this later.

I can't believe I'm saying this... GBK is correct, sleep only affects the current message.

------------------
The Sniper Missions. Current project, The Sniper Missions

The Magician Saber System.

Get used to it.

------------------
I used to believe that we only want what we can't have. I was wrong. The truth is, the wonderful truth is, we only want what we think we can't have.

GBK oNline. Cogs, tuts, and total w00tage.

GBK is right. When I use sleep(); in some cogs I'll sometimes block subsequent messages from being processed until the first one is finished.

------------------
Sylvicolus JK homepage
If I have ever made any valuable discoveries, it has been owing more to
patient observation than to any other reason. -Isaac Newton

I prefer to stay away from sleeps for the most part because I've heard bad/mixed things about them. But I'll often use them in a prototype cog when I'm just trying to get something to work because they are so quick to implement.

Use sleep()s in a cutscene cog, or maybe something else, but the only thing I can think of that sleep is the only/best/cleanist way to go in a cog is cutscenes cogs.

------------------
The Sniper Missions. Current project, The Sniper Missions

The Magician Saber System.