 |
Server Help
Community forums for Subgame, ASSS, and bots
|
| Author |
Message |
Goldeye
Novice
Gender:
Joined: Dec 15 2003
Posts: 57
Offline
|
 Posted: Sun Apr 02, 2006 4:22 pm Post subject: |
 |
 |
|
|
| Anonymous wrote: | | unless my math is totally rusty i dont think thats 100% accurate. the ball has some weird behaviors when its close to stopping. for some reason when the ball is fired diagonally the smaller velocity seems to reach 0 sooner than the other. it is hard to see with standard settings but it does happen at the very end. however in hz is really easy to see. im wondering if this happens because the values go too low for continuum and it converts them to 0? still kinda weird. |
In HZ, I just tested shooting 4 balls in a circle. One vertical, one horizontal, one 45 degrees and one around 10. They all ended up equidistant from the center.
Can conclude from this that the velocity vector magnitude is reduced, not the components.
What you see as weird is perfectly normal, that velocity component is so low that you don't notice it any more. Keep in mind that the ball is probably still moving at a subpixel level.
I will try to experiment with the position sometime soon, either finding a program to take screenshots of a moving ball at regular intervals or writing a module for recording start and end ball positions (and approximating the time) |
|
| Back to top |
|
 |
Mr Ekted
Movie Geek
Gender:
Joined: Feb 09 2004
Posts: 1379
Offline
|
| Posted: Sun Apr 02, 2006 5:01 pm Post subject: |
|
|
|
|
Yes, but even with sub-pixel movement, eventually the numbers trail off to zero in one axis before the other. For example, cos(80) = 0.173648, sin( = 0.984807. When velocity gets small enough, movement in the X direction will round to zero before the Y direction. However, this is a VERY tiny issue.
_________________
4,691 irradiated haggis! |
|
| Back to top |
|
|
Smong
Server Help Squatter
Joined: 1043048991
Posts: 0x91E
Offline
|
| Posted: Mon Apr 03, 2006 10:06 am Post subject: |
|
|
|
|
| Goldeye wrote: | | I will try to experiment with the position sometime soon, either finding a program to take screenshots of a moving ball at regular intervals or writing a module for recording start and end ball positions (and approximating the time) |
Not many people realise this but only the client knows the end position so a module wouldn't be able to do that directly.
What I suggest is use a ship with a known ball prox, fire a ball directly at it. Move the ship gradually further away from the fire point until it no longer picks up the ball - this will be where it stops. You can use the ball fire/pickup callback to time it.
To overcome the glitches in moving ships per pixel, you can decrease the ball prox gradually. When you have decreased it by 16 pixels, move the ship 1 tile further away and reset the ball prox.
_________________
ss news  |
|
| Back to top |
|
|
Guest
Offline
|
| Posted: Mon Apr 03, 2006 10:11 am Post subject: |
|
|
|
|
| Goldeye wrote: | [..]
What you see as weird is perfectly normal, that velocity component is so low that you don't notice it any more. Keep in mind that the ball is probably still moving at a subpixel level.
|
nah, the ball does a perfectly visible "curve" when a velocity reaches a certain value, and that definately isn't "normal" in vector math. it is really easy to see in hz. while not moving, shoot the ball at 181 degrees (or 21 continuum degrees.. anyway one pixel more than facing down/up/left/right) and the curve i'm talking about is really easy to spot. |
|
| Back to top |
|
|
Goldeye
Novice
Gender:
Joined: Dec 15 2003
Posts: 57
Offline
|
| Posted: Mon Apr 03, 2006 4:46 pm Post subject: |
|
|
|
|
| Anonymous wrote: | [..]
nah, the ball does a perfectly visible "curve" when a velocity reaches a certain value, and that definately isn't "normal" in vector math. it is really easy to see in hz. while not moving, shoot the ball at 181 degrees (or 21 continuum degrees.. anyway one pixel more than facing down/up/left/right) and the curve i'm talking about is really easy to spot. |
If this is true, how does the ball still land along the circular arc?
The trail does "curve", because the small component becomes too small to draw. However, it's seems to be a perfectly correct vector. |
|
| Back to top |
|
|
Goldeye
Novice
Gender:
Joined: Dec 15 2003
Posts: 57
Offline
|
| Posted: Mon Apr 03, 2006 4:53 pm Post subject: |
|
|
|
|
| Smong wrote: | [..]
Not many people realise this but only the client knows the end position so a module wouldn't be able to do that directly.
What I suggest is use a ship with a known ball prox, fire a ball directly at it. Move the ship gradually further away from the fire point until it no longer picks up the ball - this will be where it stops. You can use the ball fire/pickup callback to time it.
To overcome the glitches in moving ships per pixel, you can decrease the ball prox gradually. When you have decreased it by 16 pixels, move the ship 1 tile further away and reset the ball prox. |
Of course I realize that!  I would use a ship with 1 prox to get the position, and just guesstimate the time with a stopwatch or the like.
Getting a video of it would be the best way, either with constant fps or a reliable timer on the screen. |
|
| Back to top |
|
|
|
|
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
Software by php BB © php BB Group
Server Load: 219 page(s) served in previous 5 minutes. |
FAQ
Search
Memberlist
Usergroups
Statistics
Register
Profile
Login to check your private messages
Login
Insight into TM_Baw Plugin? 
