Hoverball Simulation with Thrusters, GPS , Numpad Inputs and E-Gate

[Xtensity]

Originally Posted by Aspras

Its not a second , watch the video i made , if the update rate was a second then the value of delta would only change every 1 second , and that delta changes a lot faster than once per second.

Well then its simply every time it changes, so?

[Aspras]

So i am pretty sure that time period is 0.1 seconds so Delta is the change of a value ( either negative or positive) per 0.1 second.

[Aspras]

Added In-Game Numpad Tutorial with video , and in depth explanation of how code works.

[Gunski]

Thanks, helped me a lot!

[Ergzay]

Delta is the change since the last execution of the delta from what I can tell. So if you don't use an interval() controlling it then it will be based on whatever rate the gyroscope outputs at (which will vary as if you are moving little enough the gyroscope isn't changing then your chip won't trigger either).

[Pyro-Fire]

thruster hovering isnt exactly new, it may be uncommon, but definately not new.

[Starcitsura]

Not to pick apart your code, but it is overly complicated for the simple task at hand.
None of this is more so true then your keypad. For your 21 lines of code, I was able to do the same, with more functionality. (can handle more then 4 digits)

N@ Numpad
I@ Input Reset
O@ Value
Input -> Value = Value * 10 + ( Input -1);
Reset -> Value = 0;

All buttons are not toggled. Button 1 = (0,2), Button 2 = (0,3), Button 3 = (0,4), ... Button 9 = (0,10), Button 0 = (0,1) and of course, Reset = (0,1);

The only problem this has is with large numbers. It stops doing math correctly which I suspect is a limitation of the lua.

Edit: Forgot to mention how to wire it up... Reset goes to Reset, Buttons 1-5 to one add chip, the first add chip and buttons 6-0 to another add chip, and then that final add chip is wired to Input
(1) (2) (3) (4) (5) -> ADD1 (6) (7) (8) (9) (0) -> INPUT