I have been thinking about this and figured it required a few properties such as:
- x
- y
- prevx
- prevy
- momentum
- avgx
- avgy
These properties might help and I am working on this right now.
would they all be based on a coordinate system?
Yes
I am still trying to figure out how to delay coordinate points.
But why would you need to delay them though?
To compare prevx or prevy with the current x or y.
I will leave it at that
Happy testing
1 Like
I did it. you want screenshots? I still have some bugs, but most of its done
I used trigger delays.
what about u?
@CustomCoaster
I DID IT!
this was all it took. YEah, this can predict movements
starts to vibe to phonk music
lol so basically, this is not a very accuratte system. due to some delays, and ticks (broad casts and such are gonna need like a frame or two to process, and so do the caluclations) so it is about 2-3 coordinate planes off. But cmon, this is the first gkc ai!
TWO WORLD RECORDS FOR ME!!!
lol I’m gonna publish it.
6 Likes
could you show us a gif?
How did you implement trigger delays with the coordinates though?
I finished my design!
What each overlay does:
- Top left: Where you are
- Top right: Prediction accuracy (Not very accurate)
- Bottom right: Momentum
I’ll be working with trigonometry to create a more accurate prediction.
I will probably make a guide on this, and ask me if you have any questions.
3 Likes
ok,so I probably have a +97% accuracy on mine.
HOW ARE U DOING TRIG!!!
ok, lemme just tell u how to do it.
set old x = x
then move.
set new x= x (after u moved, so like, with a 1 sec delay)
then find the difference. add that to current position.
shouldn’t be that hard…
how is umm, momentum supposed to be factored into this?
like, why we need momentum. there isn’t momentum in gkc
1 Like
What do you mean?
Also, I found there was a bug, so the accuracy was offset.
ohh!
ok, can u explain ur setup?
my stetup goes like this :
Set old x to X
set old y to y
wait 1 second
set new x to X (after the 1 second, which we will be assuming that the player is moving)
set new y to y
then find difference between old and new
add that to current position times the amount of time left.
1 Like
Mine works about the same as yours does.
- Set old x and y to current x and y
- wait 0.2 second
- Find momentum by solving for difference between old coords and current coords
- Create prediction by using momentum
- Check if prediction is true
- Solve for percentage between correct predictions and total predictions
2 Likes
OH! thats cool!
(my favorite saying : Great minds think alike)
lol i call momentum “change in x/y” instead of momentum
i dont really solve for percentage.
though my coords are rarely 100% correct.
i think processing speed and stuff will make it slow down for a second or two, so it might lag out and deliver worse results.
1 Like
Epik!
1 Like
Cool! You finally got it done!
That’s AMAZING! I might try that out!
It could use some work, though, but for now, this is amazing!
1 Like
turns on advertising voice
it comes with a a 98-100% accuracy rate!
anyways, @Apollo came up with the same system too! just later than mine, but we have the same concept.
Great job Apollo!
4 Likes