Poll: What should we do about it You do not have permission to vote in this poll. |
|||
Leave it as is | 0 | 0% | |
Completely remove it | 3 | 42.86% | |
Have it be the same just on interval, 3 sec | 0 | 0% | |
Have it be the same just on interval, 5 sec | 2 | 28.57% | |
Have it be the same just on interval, 10 sec | 0 | 0% | |
Have it be the same just on interval, 15 sec | 0 | 0% | |
Have it just on radar constant update | 0 | 0% | |
Have it just on radar 5 second update | 1 | 14.29% | |
Have it just on radar 10 second update | 1 | 14.29% | |
Have it just on radar 15 second update. | 0 | 0% | |
Total | 7 vote(s) | 100% |
* You voted for this item. | [Show Results] |
The "kill" indicator for flag
|
2014-08-05, 08:28 AM
(This post was last modified: 2014-08-05, 08:28 AM by Victor.)
|
|||
|
|||
RE: The "kill" indicator for flag
@ruler501, the current justification is that because you don't want the enemy to steal your flag easily, you put a GPS on it with instantaneous updates or a short interval. It wouldn't make sense to have long intervals.
But isn't 15 seconds (4/minute) a very long time? See the reciprocal behavior: period = 1/frequency instant: infinite 1 second: 60/min 2 seconds: 30/min 5 seconds: 12/min (this is what Call of Duty uses) 6 seconds: 10/min 10 seconds: 6/min 12 seconds: 5/min 15 seconds: 4/min As you can see, increasing the period slightly when it is small decreases the frequency by a lot, but then increasing the same amount later doesn't affect frequency as much. Best regards,
Victor //victorz.ca Code: Your antithesis compares favorably with any high magnitude of pwnage. (-you > |p|, you < -|p|) |
|||
« Next Oldest | Next Newest »
|