Skip to content
UAVProg
Languageen
Simulator

Simulator

What the simulator models

What the flight model reproduces, what it leaves out, and what a clean simulator flight does and does not tell you about a real drone.

This is the page to read before you tell a class that the simulator “is” the drone, and the page to read before deciding whether this product suits your course.

Short version: the model is good enough that bad flying fails for real reasons, and it is not calibrated to any particular aircraft you might buy.

What it reproduces

The simulator uses a rigid-body physics model. Browser frame rate also depends on the device and network; it is not a guaranteed copy of the physics update rate. What acts on the aircraft:

What the model does
Mass and thrustEach airframe has a real mass and thrust-to-weight ratio. A heavier drone accelerates less for the same command.
Motor lagRotors take time to spool up — tens of milliseconds, and different per airframe. You cannot change thrust instantly, which is why abrupt programs overshoot.
DragThe drone is slowed by the air it moves through.
WindA genuine aerodynamic force, not a nudge: it depends on the drone’s speed relative to the air, and on which way the body is facing, so a broadside drone catches more than an edge-on one.
Thin airAir density falls with altitude, and thrust falls with it. Climb high enough and the drone stops being able to climb.
Ground and ceiling effectFlying close to the floor or under a roof changes the lift available, the way it does in reality.
Confined spacesIn a tight space the model reduces thrust authority and destabilises the aircraft, so a corridor is harder than open air.
BatteryA 1S lithium pack modelled from 4.2 V full to a 3.3 V cutoff, draining faster the harder the drone works. Voltage sags as it empties.
CollisionsSelectable per mission: bounce off, crash, or pass through.
Sensor noiseThe accelerometer, gyroscope and magnetometer all carry noise and a slowly wandering bias, so readings are never perfectly clean.

What a student can actually reach

The APEX category provides the basic flight commands and battery reading. A connected simulator also adds equipment categories from its live inventory: installed sensors, lights and a cargo hook, where present.

A sensor block chooses an installed device and field. Check readiness or wait for a valid sample before reading; a warming, stale or missing value is not automatically zero. The list in the actual session determines what is available, not the list of every sensor the simulator can model.

Simulator navigation blocks use absolute north/east coordinates and positive altitude in metres. They wait for arrival but do not avoid obstacles. Weather and equipment can be set by the world, aircraft or lesson; their existence is not a promise that a student can change them from a block.

Blocks explains the student-facing commands, including the four APEX commands that only print a message in the simulator.

Lessons can narrow it further

A lesson can lock capabilities for the flight it sets up — a restricted world, a particular airframe, certain controls disabled. So “can the simulator do X” is partly a per-lesson question rather than one global answer.

What it does not do

DOING REAL WORK bad flying fails for real reasons Mass and thrust-to-weight Motor spool-up lag Aerodynamic drag Wind, direction-aware Air thinning with altitude Ground and ceiling effect Battery drain and sag Collisions, sensor noise THERE, BUT SIMPLIFIED right in shape, not in number Hover wobble is partly added by the controller, not purely a result of the physics The battery is a model of a pack, not a measurement of the one in your cupboard Wind is OFF unless a mission turns it on NOT THERE AT ALL do not teach these from the sim Satellite positioning, and losing it The radio link, and losing that Rain, cold, turbulence Damage, wear, a bent prop
The middle column is the one that catches people out: those things are present and behave plausibly, but their numbers are chosen to teach rather than measured from an aircraft.

There is no satellite positioning in the model at all. The simulated drone always knows exactly where it is. Everything a real pilot learns about GPS — that it drifts, that it is poor near buildings, that losing it changes how the aircraft behaves — cannot be taught here, because from the drone’s point of view it never happens.

There is no radio link. Programs run without the possibility of losing contact, so failsafe behaviour is not something a student meets.

Weather is wind and nothing else. No rain, no temperature effects on the pack, no turbulence beyond what wind and confined spaces produce.

Nothing wears out or breaks. Props stay true, motors stay matched, and the battery is new every time.

So what does a clean simulator flight tell you?

It tells you the program is right. The order of operations, the geometry, the timing, whether the student thought about how long a movement takes. That is the thing the course is teaching, and the simulator tests it honestly.

It does not tell you the flight would work outdoors. A real first flight adds wind you did not choose, a surface that is not flat, positioning that wanders, and a battery that is not new. Students who go on to the hardware track should expect their first real flight to be harder than their last simulated one, and that is the correct expectation to set.

Is that enough to teach with?

For a programming course, yes, comfortably — and the reason is worth stating positively rather than as a concession.

A student who writes a program that ignores how long a movement takes will see it overshoot, because motor lag is real here. A student who flies a heavy airframe with a light-airframe program will see it sink. A student who plans a route without thinking about the battery will run out. Those failures are the lesson, and they arrive as physics rather than as a mark.

What it will not do is stand in for flight training. See What UAVProg is for where that line sits in the product as a whole.