We’re excited to launch Litchi Hub, the next-generation successor to Mission Hub - now in beta!
Packed with exciting new features and a fresh design, Litchi Hub makes flight planning smarter, faster, and more collaborative than ever.
So far, it’s great!
I do miss seeing the distances between all waypoints. It only shows adjacent distances when a waypoint is selected.
My guess, it was changed to unclutter the screen a bit. Could that possibly be something users can turn off or on?
Batch Edit Turn Radius Bug Report:
Batch editing curved turn radius only affects first waypoint selected.
Steps to reproduce:
Create new mission (drone type does not appear to be important)
Add five waypoints
Set path mode to curved turns in global settings
Turn Batch Editing mode on
Select the three interior waypoints
Change the “turn radius” under “Advanced”
The “turn radius” of only the first waypoint selected is altered.
Expected result: Turn radius of all selected waypoints should be modified.
Opinion: A global “turn radius” option should be available. When there are many waypoints, it becomes impractical to have to select them all to change each ones turn radius.
Opinion: In addition to the plus and minus signs and the numerical input, a slider is preferred for changing this value.
Feature Request:
When changing the heading at a waypoint, the waypoint icon should dynamically show the heading as the heading value is being altered.
Steps to reproduce:
Create a waypoint mission
Select a waypoint
Change its heading mode to “transition”
Move the angle slider and notice that the corresponding icon only changes on a “mouse up” event.
Expected result: The waypoint icon should change as the value of the heading angle slider is changed. In JavaScript terms, the icon should be modified “onChange” instead of “onMouseUp”.
Show minimum mission height when using the “Smooth Curves” path mode with a “DJI Fly” drone (such as the Mini 4 Pro).
Explanation:
When a flight path is created that passes through its control points (waypoints) and those control points (waypoints) are of varying heights, it is possible for the flight path to have a lower altitude than any of the waypoints. This characteristic of splines that pass through its control points is not obvious to many people. Consider a four-waypoint path using “Smooth Curves” where the waypoint heights are specified to be at heights 50, 10, 10, 50. In order for the flight path to pass through all four waypoints, it will be necessary for the path to be less than 10 units high between waypoints 2 and 3. There have been reports of people crashing their drone because they were unaware of this and the DJI Fly app did not warn them about this.
Recommendations:
Display the minimum path height somewhere on the map when its height is less than that of the lowest waypoint.
Highlight any path segment between two waypoints where the path segment height is less than that of the lowest of those two waypoints.
We agree that some safety features would be ideal and will consider it. For now you can check the 3D preview which should help a lot to prevent such issues.
There is already a 25% default turn radius when adding new waypoints. We could add a global flight setting for that, would you prefer a percentage or a set radius in meters?
I have only had a chance to take a brief look at the new Hub and am planning on exploring it more in the next few days.
So far this is what I like and don’t like.
Likes:
• new improved saved mission management
• 3D view of missions
• ability to preview mission
Don’t Like:
• couldn’t find the wrench tools anywhere (move, rotate, scale). I use these all the time.
• autosave - seems to autosave changes to missions so if I goof up and want to re-start there is no undo (couldn’t find it).
I am not experiencing a 25% default turn radius. Instead, when I go to the advanced settings for a waypoint, I see 0.7 feet as the turn radius. This is for waypoints that are 100+ feet apart.
It probably makes more sense to provide the global turn radius setting as a percent. If it were in meters or feet, the global setting could easily be outside the valid range for waypoints that are close together.
The global “Heading Mode” (was “Path Mode”) options include: Follow Path, Locked, Manual, and Point of Interest. If one wishes to create a mission that transitions from specified headings at each waypoint, one must manually change the path mode of each and every waypoint. While this works, it is cumbersome.
It would make creating such a mission easier if there was another global “Path Mode” option of “Transition” or “Custom” (previously called “Custom” in the former hub). When selected, every new waypoint would default to the “Transition” heading mode in the waypoint editor panel.
When you add a new waypoint (say WP 4) while path mode is set to Curved Turns, the turn radius of the previous waypoint (WP 3) is adjusted automatically. It is set to 25% of the available space (the shortest distance between segments 2-3 and 3-4) for the turn taking into consideration the previous turn radius (at WP 2) which itself may limit the available space.
I assume you meant Heading Mode.
The reason we don’t show Transition mode as a global flight setting is because you would have to set a per-waypoint heading angle anyway for it to be any useful. However it may be that it is still useful to reduce the number of clicks. We will consider adding it.
