Hello everyone, I would like to know your opinion about the problem I'm facing right now. I'm try to using GameMaker for make a simple game that will let user control a box where I will apply a "normal" force of gravity like on earth of 9.81m/s², for convenience I decide to use a scale of 1 mt equal to 32 pixel. 1 second is equivalent to 60 frame execution so based on this I will get a velocity increment of around 5.232 pixel per frame and offcurse that's a lot and result in my object just disappear from screen in 2 seconds.

I want to keep correct numbers just because I want then to implement the drag and lift force for this object but I'm already stopped from this simple limit. What's your suggestions ? Thank you for the patience, best regards.

Why is actual physics scale important? Does the game become more fun if you use 9.81 m/(s*s) than, say 8 m/(s*s) or 6 m/(s*s) ? EDIT: Note that what you compute and what you print doesn't have to be equal.

I would pick a value that is fun to play rather than trying to be realistic.

Tweaking the value is a good way to change the difficulty perhaps.

If you do want to stick to realism, I believe you have to rethink your pixel size. Pixel size of 0.03m isn't very useful at such velocity accelerations. (that is, the player likely doesn't care for positions less than 0.1 to 0.5m, would be my guess).

Well fun is not take into account if I have to write some drag and lift formula and expect certain behavior by my body with certain values and in opposite find totally different :) my object it's a 5 mt box and must be this size but not think I can scale down to 32px per 5 .....

Drag and lift based on speed so I would like to get at least some sort of normality on numbers.

Everything you've added is doing exactly what it should. So, your options are:

• make gravity less powerful
• change your rendering scale so that more of it fits on the screen
• scale your objects so that they're bigger and appear to respond more slowly

Hmm, you can also work in a continuous [m] unit space, and separately translate to pixels by some offset and scale factors. That would give you freedom in how to display things, at least more than having a fixed [px/m] scale.

Nonetheless, if you want to show the speed adequately, you'll need more space due to the high speeds. That means as far as I can see either means more pixels or a different scale.

Maybe have some sort of dynamic scale? At high speed give an overview, at low speeds provide more details?

Not sure what the problem is. You want your object to be on screen longer while having a static camera? Zoom out further? Why can the box fall off screen? Can you move the camera with the box? Please provide a better description of what you're trying to do and what your actual problem is.

Everything you've added is doing exactly what it should. So, your options are:

• make gravity less powerful
• change your rendering scale so that more of it fits on the screen
• scale your objects so that they're bigger and appear to respond more slowly

I guess the only solution usable could be the adapt gravity value on smaller value. I will try to fix the view on the screen too as suggested Mussi, thank you for the suggestions.

You have a math error. 9.81 m/s2 at 32 pixels/m and 60 frames/s is 0.0872 pixels/frame2, not 5.232.

Pay attention to the units - acceleration is in units of distance over time squared, which means that if there is a time unit conversion you have to apply it twice.

Please note that there is a very good chance that you'll find this corrected gravity too "floaty" - there's a reason most 2D games actually use gravity significantly stronger than Earth's.