I don't want to sound like a spoiled brat requesting more food from developers but I recently came up with a cool idea/feature. I'm not sure how I would code it especially considering it would be rather complex (incredibly complex). I also understand that this is just an idea, I'm not expecting anything to come out of this.
This idea stemmed from the problem many spacebarrers and even nsbers have which is velocity; it can be quite difficult to gauge where you're going to land (esp when constantly pausing and playing).
But how could you make this accurate? But there are so many variables which play into velocity that change track-by-track, so how could you possibly begin to estimate a bike's velocity?
Let's say to check the velocity of the bike (when paused) you press a certain key (say,
Q) and it gives an outline of what would happen to the bike (potentially through "Player Trail" or a short animation) in the next 5 seconds regarding the track features of even simply air time (any more than 5 seconds would generate considerable lag I'd imagine).
Then there has to be a given. Given
x, the bike would land
y.
For instance,
x could represent releasing all keys (or holding up).
This is just an idea in fantasy land right now, and I don't think that it is very high priority amidst other updates that players might want, so again, I'm not expecting anything out of this.
Perhaps this would even be considered cheating, I don't know; but I think this would allow newer players to better understand bike physics as so many high ranking players have already.
Calculus you are such a gem to the community and you're doing good work out there.
Click to expand...
