#1467

[Bug] Stalled airborne rebase can turn FL300 into 288 km altitude

OpenMihneaTeodorStoicaopened 3d ago

What happened

BeamNG.Earth 1.10.1-beta.dev.500, native Linux, BeamNG.drive 0.40. A 737 add-on held approximately 30,000 ft and 200 m/s on a long flight. The companion server remained active, but the client stayed on anchor 115 while the next anchor build took 9,182.57 s. When a newer origin committed, the aircraft jumped to roughly 287,669 m, air density/IAS went to zero, and the autopilot dropped out. No teleport, reset, or altitude command was issued at the jump.

EventWorld locationObservation
Anchor 115 (old)41.75000, -112.28000Committed at 23:15:32; aircraft subsequently held local Z ≈ 9,144 m
Anchor 11641.87000, -112.19000ready in 9182.57 s
Anchor 119 (new)55.65000, -98.28000Client committed a 19.704 deg rebase; immediately afterward terrain follow held at 287669 m above the ground ahead

Independent reproduction

This reproduces the legacy rigid altitude jump without a vehicle mod or BeamNG. Run from a checkout with LuaJIT:

LUA_PATH='./mod/beamng_earth/lua/ge/extensions/?.lua;;' luajit - <<'LUA'
local g = require('beamngEarth/geodesy')
local a, b = g.newAnchor(41.75, -112.28), g.newAnchor(55.65, -98.28)
local _, _, z = a:transformTo(b):apply(911790, 1673856, 9144)
print(z) -- about 287635 m
LUA

worldTransformTo on current main corrects the projected position but still preserves the already inflated geodetic height if the old origin remains in use this long. This is not a request to clamp every aircraft altitude or change the ordinary rebase transform. The underlying problem is a distance-driven rebase request that can occupy the only pending slot indefinitely, even after its terrain target is obsolete. Expected: expire an overdue rebase, retry near the current player position, and ignore any late response for the expired request. The reason anchor 116 took 9,182 s has not been isolated.

Activity

0

No activity yet.