Release notes

Changes to Markhor, recorded build by build.

Every build, as it shipped. See the milestones for the work ahead. Markhor is in active development and is not yet available outside Lechuza.

Beta 0.3.4

Beta 0.3.4 Release

Arming and flight modes follow your aircraft, more ways to connect, recording that keeps going, and one plain voice across the app.

Beta 0.3.4 ships as build 365. It completes the 0.3 series.

Added5

  • Connect more aircraft: flight controllers on their own USB port, any baud rate you type, and UDP send-to for a router, MAVProxy, or a Herelink or SIYI link. A parameter download on a slow link keeps going as long as values keep arriving.
  • The Telemetry link setting: Auto lowers the telemetry rates while the link is losing data and raises them again once it's clean, never above the rates Markhor used before; Narrow keeps them low on any link. After an outage the rates are asked for once more. A stream the aircraft refuses is no longer reported as silent, and one it accepted that stays silent is.
  • A flight controller that reboots in flight raises a critical alert with a tone. An aircraft that never had a GPS fix no longer shows GPS FIX LOST, and a battery swapped without a reboot is checked again.
  • Recording keeps going when the capture card drops out, changes size or fails: a new clip starts for the same flight, with one warning and one line when it's recording again.
  • Shutting down, restarting or signing out of Windows while an aircraft is armed asks first. If port 8000 is taken, Markhor moves to a free port. On a small or scaled screen the window fits, and under 680 pixels tall Free Flight goes compact, keeping E-STOP, LINK, ALT, BATT and STOP. Picture-in-picture video takes the video's shape. If Markhor still can't start, the start-up screen names the program on its port, another program answering there, or a ground station that keeps crashing.

Changed5

  • ARM and the flight modes follow your aircraft. STABILIZE and the other modes that don't need a position arm without a GPS fix; GPS and home are needed only where the mode or a fence uses them. The MODE menu lists your flight controller's own modes, then SAFETY and MORE…, and Free Flight no longer offers AUTO. TAKEOFF after a landing switches to GUIDED before it arms.
  • The vibration caution now starts at 30 m/s², and a new install picks metric or imperial units from your Windows region. Settings saved by this version open read-only in 0.3.3 and older, which say so.
  • Every aircraft goes by its own name everywhere, never Eagle One, and Markhor no longer puts a made-up place on the map where a home or a position is missing.
  • Cameras: a sight-in saved on a camera two aircraft share gives this aircraft its own copy, and Import's Replace it never changes another aircraft's camera. Set up camera offers No camera, and Standard or Fisheye for a camera you type in. No camera chosen shows only where a camera matters.
  • One voice across the app: no tips or explainers, a greyed control is just greyed, and a message says what happened and what it means for the flight. It says aircraft and ground station throughout. The Vehicle menu is now Aircraft, Drone display is Aircraft display, Help ▸ Changelog is What's New, and Home no longer shows coming-soon tiles.

Fixed4

  • Check for updates on startup is off by default, and starting Markhor makes no update request.
  • Flight Logs' delete names the flight and starts on Cancel.
  • A refused connection says so in one sentence.
  • The Attitude and Velocity cards stay blank until the aircraft first reports, and one damaged camera no longer hides all the others.
Beta 0.3.2

Beta 0.3.2 Release

Click the video to see where a spot is on the ground, and sight in the camera so the map can be corrected.

Beta 0.3.2 ships as build 363.

Added7

  • Click a spot on the video to see where it is on the ground. The point shows on the main map and the small map with its coordinates and distance from the aircraft, and stays drawn on the live picture. Like the camera footprint, it is dashed when Markhor can't vouch for it, and when it can't place the point the video says why, such as Waiting for pose or No ground.
  • Sight in your camera on each power-up. Hover over your takeoff spot with the camera looking down, press Sight in on the video and click the spot. Markhor measures how far the camera's pointing is off, and once the check passes it corrects the camera footprint and clicked points for this power-up. Clicking the spot in more than one still, from different places in the hover, makes the fit stronger. Not in picture says the spot isn't in view, such as with an upside-down gimbal.
  • Sight in on a point you choose instead of the takeoff spot: right-click the map, choose SIGHT-IN POINT, then pick Map point in the sight-in.
  • A fixed camera's passed sight-in is saved with its camera setup, so later flights start corrected. Changing the camera's lens or its mount clears it.
  • Fleet ▸ Cameras sets each aircraft's camera mount: a gimbal, or a fixed camera with its tilt up or down, roll and yaw.
  • When the camera's mount can't be used, the footprint and clicked points say why, such as Camera tilt not set, Camera mount type not supported, or a gimbal range that's reversed.
  • Recordings keep each sight-in and the camera's check, so a recorded flight can be reviewed later.
Beta 0.3.1

Beta 0.3.1 Release

The camera's view on the map, a name for each aircraft, and a camera profile for each one.

Beta 0.3.1 ships as build 362.

The camera outline is drawn dashed on every real aircraft for now. The lens values and video delay are typical rather than measured.

Added4

  • The map shows where your camera is looking. A camera outline is drawn on the ground on the main map and the small map, using the gimbal's angle and the camera's lens. It is dashed when the app cannot vouch for it and hidden when it cannot place it. The map's corner says why. Turn it off in Layers ▸ Camera footprint.
  • The app knows which aircraft is connected. Each flight controller gets a name, shown in the ARM confirmation, TELEMETRY and the parameters window. Rename it in Fleet ▸ Aircraft. Confirming ARM arms only the aircraft it named.
  • Fleet ▸ Cameras binds a camera to each aircraft. Pick the Walksnail Moonlight from the lens library, type a camera's field of view or import a camera profile. Each recording remembers the camera it was made with.
  • Recordings keep where the camera was and where it pointed for every frame, for reviewing a flight later.

Changed2

  • The aircraft's marker, its pillar and the trail's head move smoothly between telemetry updates, and follow mode follows them.
  • Altitude alerts have a caution and a warning. The warning repeats every 10 seconds while you stay above it.

Fixed2

  • Alerts you did not see while flying are kept for you after landing, and the HUD's lamp shows them.
  • A signal lost history mark stays after the link comes back, so a short drop is not missed.
Beta 0.3.0

Beta 0.3.0 Release

A map that survives graphics crashes, the capture card in its best mode, and frame times recorded for every flight.

Beta 0.3.0 ships as build 361.

Before release, every automated check run on the released code passed. We also ran the app on a test machine with a simulated camera and a simulated aircraft.

We then field tested the released build on our own aircraft on November 9. The Cam Link 4K capture card delivered 1920 × 1080 video at 60 fps. The flight records confirmed the clock used for incoming frames, measured the radio link’s rates and losses, and recorded how the computer and flight controller clocks relate to each other, including UTC. They also captured the flight controller’s hardware identity and firmware version, and measured map and video performance with the laptop on AC power and using its RTX 5060.

Added2

  • When the map uses software graphics, the app says so. Software graphics makes the map slow and puts more work on the CPU.
  • Recordings keep the time of every frame, and the flight records keep the flight controller's clock and firmware version so a flight can be lined up with its video.

Changed3

  • The map draws on your computer's dedicated graphics card where it has one. Settings ▸ Appearance ▸ GPU chooses High performance, Power saving or Windows decides, and shows which card the map is drawing on.
  • Capture cards open in their best mode, such as 1920 × 1080 at 60 fps, instead of the mode nearest 640 × 480 at 30 fps. The video panel shows the camera, its size and frame rate, and says when it delivered less than that.
  • The app now runs on Electron 45 with Chromium 156.

Fixed4

  • The map rebuilds itself if the graphics card resets or the map loses its drawing surface, while the aircraft link and commands keep working. If it keeps failing, it says Map unavailable and offers Restart map and Reload window. The picture in picture, Review and simulator maps do the same.
  • The map no longer redraws faster than it needs to, which made picture in picture video stutter on laptops with built in graphics. Settings ▸ Appearance sets a frame rate cap, with its own setting on battery.
  • If your saved camera is not plugged in, the app no longer opens a different camera in its place.
  • The REC indicator no longer disappears during a flight while recording continues, and a recording's length no longer counts the time it took to finish saving.
Beta 0.2.6

Beta 0.2.6 Release

Reworked offline maps, your own map sources and files, and fixes for returning to a flight after a crash.

Beta 0.2.6 ships as build 360.

Added5

  • Add your own maps in the Maps window. Paste an XYZ, TMS, ArcGIS, WMS or WMTS address, or a quantized mesh terrain server. The app checks it and fills in its name, credit and coverage. Use it as the base map or as an overlay with its own opacity. Addresses and keys are stored encrypted on your computer, and an export leaves keys out unless you choose to include them.
  • Save your own map sources for offline use after allowing it for each source.
  • Open MBTiles, GeoPackage and PMTiles map files from New pack in the Maps window.
  • Make a map pack by drawing its area and dragging its handles, or start from the current view or a point with 2, 5 or 12 km around it. The size and download time update as you go. The 12 km option makes a pair of packs, with a wide area and a sharper center.
  • Offline maps only, on the Basemap button, draws your saved maps alone. Basemap also holds hillshade, contours and pack outlines.

Changed4

  • The Offline window is now the Maps window, with your maps listed beside one pane. Each pack shows its place, size, date and source, and Go to flies the map there.
  • Every pack set to show on the map now draws at once, up to 16, with sharper packs on top and each pack's name and state outlined on the map.
  • Map pack downloads keep going through a reload or a locked screen. Each row shows its speed and time remaining, a busy map server slows a download instead of stopping it, and every stop gives its reason, such as a full disk or a lost connection.
  • Range Rings were removed in Beta 0.2.5, along with their setting and their Layers row.

Fixed13

  • After a crash or reload with an armed aircraft connected, the app returns to the flight view on its own and keeps watching for signal loss on every screen. A signal loss already under way at restart is shown, and the restart sends no failsafe command.
  • If a FLY TO is not confirmed during signal loss and the aircraft holds in GUIDED with no target, the app says so and tells you to press RTL.
  • Refused RTL, LAND and mode changes keep their own reason, subject to the LAND reply limit below.
  • Without internet, the map says which pack it is drawing from, or that no pack covers the view, and offers Go to. When the connection returns, streaming resumes on its own.
  • Without internet, Sign out warns that you cannot sign back in or fly until you reconnect, and Home location search says it needs internet. A computer clock that jumps ahead no longer locks the app for up to 24 hours of app use between online checks.
  • A damaged or locked flight database no longer stops the app from starting. The app opens with a warning instead.
  • Launching with the computer clock far ahead no longer deletes flight videos and logs.
  • Feedback bundles follow Include precise location for every position they hold, including the fly-to target and the launch site.
  • Deleting a map pack during a flight no longer freezes STOP and RTL.
  • An imported mark with a color the map cannot read no longer stops the map.
  • North up keeps the view in place over high ground.
  • A coordinate typed with minus zero degrees, such as minus 0° 7′ 30″, keeps its minus sign.
  • The video panel's FULLSCREEN button and the Copy buttons work.

Known issues4

  • On laptops with two graphics chips, the app can use the slower built-in chip, lowering the map's frame rate and making camera video stutter. In Windows Settings ▸ System ▸ Display ▸ Graphics, set Markhor to High performance, then restart it.
  • If a command reply does not name its recipient, a refused LAND after another command was interrupted can show an unknown reason for up to 30 seconds.
  • A terrain height reading can be up to about 60 m too low on a mesh that samples only its corners until the authoritative terrain sample arrives.
  • A known timing issue affecting SIGNAL LOST remains open. It failed one simulation check during this release.
Beta 0.2.5

Beta 0.2.5 Release

A rebuilt map toolbar you can customize, a new CONFIG menu and a cleaner map.

Beta 0.2.5 ships as build 359.

Added3

  • CONFIG sits between FILE and VEHICLE, with Settings… moved from FILE and a new Customize toolbar… entry. Ctrl+, still opens Settings.
  • In Customize toolbar, drag buttons between the toolbar and the list to add, remove or reorder them, create groups and add window buttons such as Layers, up to 16 in all. The editor opens in the center of the screen and grows with the toolbar. Reset to default restores the seven standard buttons.
  • Basemap explains when a map needs internet.

Changed5

  • The rebuilt map toolbar has seven larger buttons by default, with a look that matches the windows. Follow, Go to aircraft, North up, My location, Go to coordinate, Saved views and Basemap are included. Pickers open immediately beside their button, and buttons that do not fit move into More.
  • Hover over or focus a toolbar button to see its name and key. Disabled buttons explain why they cannot run, and Ctrl+K shows the reason too.
  • Measuring, drawing and dropping pins are hidden until a later release. Saved marks still appear and open with a double-click. Live air traffic is hidden too.
  • Drone Display no longer shows the Ground Dot sliders or wedge-size control, which had no effect. Its glyph switches follow Layers. A glyph previously turned off there appears again after this update; click once to turn it off.
  • Deep diagnostics start off on a fresh install. Existing installs keep their setting.

Fixed5

  • North up and Go to coordinate no longer run late after full-screen video.
  • F no longer turns Follow on without an aircraft position.
  • Go to coordinate no longer moves the camera after its box has closed.
  • Switching the theme no longer changes Satellite's labels.
  • The update check stays quiet when a managed network produces proxy or certificate errors.

Known issues1

  • On laptops with two graphics chips, the app can use the slower built-in chip, lowering the map's frame rate and making camera video stutter. In Windows Settings ▸ System ▸ Display ▸ Graphics, set Markhor to High performance, then restart it.
Beta 0.2.4

Beta 0.2.4 Release

Steadier connections and commands, fewer sign-in interruptions and a clearer PARAMETERS window.

Beta 0.2.4 ships as build 358.

Added4

  • Aircraft using MAVLink 1 still connect. A notice appears once to explain what is missing and how to enable MAVLink 2. In Mission Planner, set the telemetry port's SERIALn_PROTOCOL to 2 and reboot the aircraft.
  • PARAMETERS shows a download progress bar and an estimated time remaining. The same aircraft's table stays available after DISCONNECT. One chip for each family, such as SERVO or BATT, replaces the long list, and search accepts several words together, such as batt fs.
  • In PARAMETERS, click to select a row, then double-click or press Enter to edit it. Ctrl+C copies NAME,value.
  • PARAMETERS keeps a changed edit from being silently discarded. A confirmed write shows ✓ confirmed, and ↻ reads that value again. The window also docks into the right bar.

Changed3

  • With a SiK radio, LINK shows the fade margin at the weaker end in dB instead of a percentage. It shows caution below 18 dB and critical below 10 dB. The tooltip gives both ends in dBm.
  • A refused ARM or mode change produces one notice with the reason instead of two.
  • Beta builds collect more detailed diagnostics on this computer. They are shared only through a feedback bundle you create. Turn them off in Settings ▸ Diagnostics ▸ Deep diagnostics. Feedback bundles leave out the map area you viewed unless you include precise location.

Fixed5

  • Fixed connection failures reported as exhausted all baud rates and failures to reconnect after a dropped link. MAVLink 2 is used from the start of the connection, and the aircraft's own battery state is received again.
  • When a radio reply is lost, mode changes, including those used by fly-to, and ARM, DISARM and TAKEOFF check the aircraft's reported state before saying the command failed.
  • After DISCONNECT and CONNECT to the same aircraft, the first fly-to keeps your SPD setting within the aircraft's own speed limit. If you have not set SPD, a slower cruise speed from the aircraft's profile takes priority, and the fly-to explains that choice.
  • After connecting, the map waits for the aircraft's first position before framing it, avoiding the move to a black screen. Follow, Go to aircraft and Pin at aircraft also wait for that position, and the aircraft is not drawn before it arrives.
  • A connected aircraft prevents sign-out, including one already underway, until DISCONNECT. Offline map packs remain available until then. A lost reply on a weak link no longer signs out every device.

Known issues1

  • On laptops with two graphics chips, the app can use the slower built-in chip, lowering the map's frame rate and making camera video stutter. In Windows Settings ▸ System ▸ Display ▸ Graphics, set Markhor to High performance, then restart it.
Beta 0.2.3

Beta 0.2.3 Release

Arrange windows around the map, dock them into side bars and save your layout.

Beta 0.2.3 ships as build 357.

We checked four preview builds. The last two passed every check run, and simulator flight tests were also completed.

Added5

  • Windows float over the map and both side bars; the last one clicked stays on top. WINDOW opens, places and closes windows, including closing them all. Minimized windows become top-bar chips. F10 walks the menus; F6 moves between the map, windows and bars.
  • Drop a window onto a side bar's tab strip to dock it; Float brings it back out. MISSION stays first on the left. Drag a bar's inner edge to widen it; double-click to reset.
  • The top-bar layout picker saves named arrangements and switches between them. Reset to BASE clears the arrangement. Each restart starts from BASE.
  • Windows snap to edges and each other; hold Shift to place freely. Double-click a title to roll up; drag a maximized title to restore its size.
  • Report a Problem is available in HELP.

Changed4

  • While disarmed, a maximized window fills the screen; ARM and TAKEOFF wait until you restore it. While armed, it stops above the command bar.
  • While armed, new cautions and warnings bring ALERTS above windows until ACK is pressed. STOP stays above windows, and E-STOP remains pressable under Settings, the palette and dialogs.
  • Escape closes the top item first, one at a time; pinned windows stay. Single-letter flight shortcuts are ignored in title bars, tabs and windows.
  • On small screens, several banners fold into one notice row.

Fixed1

  • The simulator's crash screen covers open windows. Drawing an offline pack's box cannot trigger flight keys. Update-check messages clear after 15 seconds.
Beta 0.2.2

Beta 0.2.2 Release

Get around the map with new view controls, coordinate search and saved views.

Beta 0.2.2 ships as build 356.

Added5

  • The VIEW menu on the map's tool rail turns the map north, flies to the aircraft or goes to the home you set in Settings. Press N to turn the map north.
  • Follow keeps the aircraft in place on screen as it flies. Zooming and tilting keep following, and dragging the map stops it. Press F to turn it on or off.
  • Pin at aircraft drops a library mark where the aircraft is, at any zoom.
  • Go to coordinate accepts decimal degrees, degrees minutes seconds, degrees and decimal minutes, UTM or MGRS. It flies the map to the position and briefly pulses at the point. Mark here keeps it in the library. Press Ctrl+G to open it.
  • Saved views keep the map's view under a name on this computer, to open, rename or delete later. Resetting all settings keeps them.

Changed3

  • When you connect with the map zoomed out to the whole globe, it flies to the aircraft automatically.
  • Home location in Settings accepts one position in the same coordinate formats as Go to coordinate and explains why a position cannot be read.
  • Electron, Mantine and other app components are updated.

Fixed2

  • Replay keeps the same camera tilt and zoom limits as the flight screen.
  • The map's tool rail and its panels stay inside the map and above the command bar, even in a small window.
Beta 0.2.1

Beta 0.2.1 Release

Flight control fixes, clearer alerts and updated app components.

Beta 0.2 users can install this update in-app as build 355.

Testing

Automated checks and 82 simulated flights on ArduCopter 4.6.3 passed. This release supports one aircraft at a time.

Changed5

  • Changing altitude is refused while the aircraft is on the ground, so take off first. During return to launch, landing and automatic flight the altitude SET button is greyed and says why before you press it.
  • Set Home is refused while the aircraft is armed, from the map menu and the command bar alike. A home you set from Markhor is sent again just before you arm, so it matches the aircraft's settled height.
  • When no speed is set, a fly to tells you it will fly at the aircraft's own speed. A target below the ground always asks you to confirm and says how far below the ground it ends.
  • Clicking away from a speed or altitude you typed but did not send puts back the value last sent, as Escape does.
  • Electron, CesiumJS and React are updated, with every known security advisory in the shipped code cleared. The licence text of every bundled package now ships with the app.

Fixed3

  • The flight mode list is readable in the dark theme, and the ARM button keeps its width when it turns to DISARM, so the command bar no longer shifts.
  • The IMU clipping alert no longer flickers. It raises at 10 clips in 10 seconds and clears after 10 seconds without one, and says so while it settles.
  • When the aircraft is back inside its fence, Markhor says Fence breach cleared. A fence breach alert stays up when the flight screen reopens, and RECONNECT on a quiet link no longer stops the parameter download.

Known issues3

  • AUTO appears in the mode list, but Command cannot show or clear a mission already on the aircraft.
  • After a lost link, the trail can draw the outage as a solid line instead of a gap.
  • If the answer to a sign in refresh is lost twice in a row, the account is signed out on every device. Sign in again.
Beta 0.2

Beta 0.2 Release

Clearer flight controls, more useful battery information and improvements to the everyday workspace.

This release brings together changes first delivered in Beta 0.1.1 build 352 and the subsequent work on flight controls, connection handling and the workspace. Access remains by personal invitation.

Testing and limits for Beta 0.2

Build 352 was checked with automated tests and ArduCopter simulation. It was not checked in the installed app or flown on hardware. Subsequent changes have automated and simulation evidence for individual fixes; validation of the final combined release is still pending.

Build 353 was checked in the installed app on October 20. Bench testing and a real flight for Beta 0.2 have not yet been completed. The last recorded hardware flight used Beta 0.1.1 build 351 on October 17, with an ArduCopter 4.6.3 quadcopter and a SiK serial radio. That flight does not validate the changes in this release.

STOP, change altitude and return to launch have not yet been flown on hardware. TCP has simulation coverage and UDP has automated test coverage only. Helicopters and smart battery cell reporting remain simulation tested.

This release supports one aircraft at a time. Downloaded offline map and terrain packs are available to accounts with the feature enabled, but their use in the field has not been verified. See Compatibility for the current platform and testing limits.

Added3

  • Press S while the guided flight STOP button is available to request the same stop action from the keyboard. The shortcut also works while a command bar number box has focus.
  • The POWER card shows the aircraft's own low battery action and threshold, read from its settings. This information is available during a live connection.
  • After an autopilot restart on a live link, Command shows a restart notice and the connection status identifies the restart.

Changed8

  • Repeated STOP presses share the same request instead of sending another burst. When a fresh mode reading shows the aircraft is outside GUIDED, the request is refused without sending a command.
  • ARM and DISARM are unavailable while the aircraft is flying. Emergency stop remains separate.
  • The guided flight warning explains where the straight path passes below the selected terrain clearance. It does not provide terrain following or collision protection.
  • Guided speed carries across a reconnect to the same aircraft, and the speed box shows when a value has not been sent.
  • Menus are organized under File, Vehicle, Tools and Help. Settings uses plainer wording, and Graphics is now called Appearance.
  • Coordinates can be shown in MGRS.
  • Map pack downloads pause with a reason and a RESUME option when a network interruption prevents them from continuing.
  • The general failsafe summary has been removed from the Command screen. Its return on an aircraft page is planned for a later release; the POWER card retains the aircraft's low battery action.

Fixed7

  • A prearm warning clears when the aircraft reports it is ready, instead of keeping ARM unavailable for up to 90 seconds.
  • SET HOME HERE keeps the aircraft's own height reference and refuses the command when the required position, terrain or home readings are missing.
  • FLY TO HERE is unavailable on the ground, and TAKEOFF ends any earlier guided target.
  • Change altitude is refused during return to launch, landing and automatic flight, and when the aircraft's position is stale.
  • Flight confirmation dialogs appear above floating windows and Settings. Emergency stop stays visible in fullscreen video.
  • Quitting with an armed aircraft or a held vehicle connection does not install a waiting update.
  • Floating windows and their minimized controls stay above the command bar.

Known issues3

  • During flight, SET HOME HERE in the map's right click menu can look unavailable but still moves home, which is where return to launch goes. Avoid it while the aircraft is in the air.
  • Without internet, an imagery error can appear even while a downloaded offline pack is displaying the map. Hide the banners under the title bar can hide this notice.
  • At the minimum window size, the last map tool can sit behind the command bar and the Layers panel can run off screen.
Beta 0.1.1

Beta 0.1.1 Release

Clearer battery alerts, simpler flight controls and new display options for screen recordings.

Correction, October 21, 2026: Battery alerts remain latched until disarm, rather than landing. The imagery issue below concerns a downloaded offline pack, rather than the temporary imagery cache. These descriptions are corrected; the release date and original testing record are unchanged.

Testing this release

Testing included automated checks, simulation and an October 17 flight with an ArduCopter 4.6.3 quadcopter, without internet at the field. That flight checked battery and vibration alerts, recorded motor outputs, aircraft identification, guided speed and restart recovery over a live radio link.

The guided flight overlay, both recording display options and LAND confirmation after upgrading were also checked in the installed app.

Helicopters, smart battery cell reporting, the combined TAKEOFF and LAND control, ground station ID settings and rejection of unsupported aircraft have only been tested in simulation. Hardware testing of STOP, change altitude and return to launch remains incomplete. This release supports one aircraft at a time.

Added3

  • Hide my location on screen in Graphics settings shows coordinates in whole degrees. The map and entry boxes still reveal your location, and logs, saved data and commands keep precise coordinates.
  • Hide the banners under the title bar keeps notices from shifting the workspace. Crash and restart notices stay visible, and missing terrain is still reported in the alert panel.
  • Set the ground station ID in Failsafes settings. An alert warns if the aircraft expects a different ID.

Changed7

  • Battery alerts now use volts per cell, with caution and critical levels for each battery chemistry in your vehicle profile. Low readings must last 10 seconds, and once armed, alerts stay until disarm. When a smart battery reports individual cells, alerts use the lowest reading. A cell count that does not match the pack at rest is flagged rather than used to estimate cell voltage.
  • Connection checks accept ArduCopter multirotors and helicopters, with a warning for firmware older than 4.5. Planes, rovers, boats and PX4 aircraft are rejected with an explanation. Telemetry now handles multiple batteries and two GPS receivers.
  • TAKEOFF and LAND share one button in Command. The confirmation shows takeoff height above home. Heights at or below the aircraft's current height are rejected without sending a command.
  • Step arrows adjust altitude, speed and takeoff height without sending a command. Press SET or TAKEOFF to apply the value. In Graphics settings, the altitude control is hidden by default and the speed control can also be hidden.
  • At 1024 by 680, emergency stop, DISCONNECT and the HUD battery reading stay visible. The other command controls wrap onto a second row.
  • LAND now asks for confirmation, including after upgrading. Turn off Confirm before landing in Failsafes settings to skip it.
  • Guided flight checks and arrival estimates fall back to the aircraft's climb, descent and cruise speeds when the vehicle profile has none.

Fixed8

  • The guided flight chip, STOP button and SET HOME banner now sit below the HUD instead of behind it.
  • Vibration alerts no longer flicker near the threshold. They show when readings are settling before clearing.
  • An alert explains when a link loss prevents sending the selected failsafe action. The command is not sent later.
  • Disconnecting from a lost link clears its reconnect alert and stops its alarms repeating.
  • Flight telemetry logs record motor outputs and RC channels again.
  • Fixed unusually high pack voltage readings from smart batteries.
  • Full parameter downloads work more reliably on slow radio links and are blocked while armed.
  • Quick ArduCopter 4.5 restarts now trigger a fresh request for telemetry.

Known issues5

  • A cleared prearm warning can stay red and block ARM for up to 90 seconds. Wait for it to clear. Restarting the aircraft restarts that wait.
  • SET HOME HERE uses terrain elevation, which can differ from the aircraft's altitude by a few meters. With the aircraft on the ground beside you, use SET HOME at its position instead.
  • After an autopilot restart on a live link, telemetry usually recovers within seconds without disconnecting. Recovery appears in the logs window but not on the main screen.
  • Without internet, an imagery error can appear even while a downloaded offline pack is displaying the map. To hide it, turn on Hide the banners under the title bar.
  • At the minimum window size, the last map tool can sit behind the command bar and the Layers panel can run off screen.
Beta 0.1

Beta 0.1 Release

The first release brings aircraft connection, live telemetry, terrain and flight controls into one workspace.

Beta 0.1 marks the first release of Markhor for Windows. This closed beta establishes the core flight workspace, with access by personal invitation only.

Included in this release

  • Aircraft connection over serial radio, UDP or TCP, with support focused on ArduPilot and testing on ArduCopter.
  • Live attitude, altitude, speed, battery and link information alongside the aircraft on a 3D terrain map.
  • Flight controls for arming, takeoff, guided flight, landing and return to launch.
  • Guided speed selection with visible saved, sent, applied and unconfirmed states.
  • An alert panel for aircraft alarms, prearm checks and connection status, with routine autopilot messages kept in a separate log.
  • Map pins, drawings and labels, plus distance and area measurement.

Testing and scope

Guided speed has been checked in simulation and selected real flights. Speed retention after STOP and recovery from telemetry stalls and autopilot restarts have been tested in simulation. Hardware validation of STOP, change altitude and return to launch remains incomplete.

This release supports one aircraft at a time. PX4 support, waypoint missions and survey missions are outside the 0.1 scope. See compatibility for platform limits and the roadmap for planned work.

Scope correction, October 21, 2026: This note originally excluded downloadable offline map packs from the 0.1 scope. Map imagery and terrain packs were included for accounts with the feature enabled. They are separate from the temporary imagery cache; field use of downloaded packs has not been verified.