#codebl

Whistling happily as I look up the contact information of work safety authorities so i can hand in my firms insane and careless breaches of basic safety.

The process for setting up hardware that can kill you is: "Whoever can do it. No knowledge or training required. The checklist for what to do is inside the heads of some people in the firm... Probably...maybe, and if those people randomly are near they will tell you what they think they remember they know"

I had a hardware setup that KILLS YOU if you touch the wrong parts. And it had been running FOR A MONTH before someone said "I... seem to remember us being told that the rules say you have to print and fill out a risk assessment and hang it on the safety rail?"

So I am slowly eating my way though the tutorial for GoDot. I already have some experience with moving things in space and calculating inputs for individual objects.... That is essentially half of robotics software. So in every frame, a function called _process is called. this function takes a number called "delta", which is the amount of time passed since last frame ins seconds (Usually close to 1/30 or 1/60). You add delta to the calculation of certain variables. The first example usually found is position, which is done like so:

position += velocity * delta

To me that was all good and obvious. But I found a lot of posts of people being confused when to multiply delta and when not to. And apparently doing it in wrong places is a quite common bug in GoDot games. Here is to figure it out! Think in term of units

Velocity is distance/time Position is distance

So you cannot add velocity to position. They are 2 different units. How to fix this? Remove the time component.

Since time is distance is divided by time, we simply multiply time onto it. You know what have the unit of time?

delta is time

Meaning it is obvious why you need delta in the line! :D position += velocity * delta