The only gotcha would be if indeed it applied to all points then the flight would not likely match reality since when flying all points are relative to the home point as mentioned. Benefits would be a much closer terrain following which could be viewed as a plus since it would represent worst case - unless you're flying under somethingThat would be a nice option to turn on and off, just to see the difference.
I see that but when some waypoints are further from others I don't always see the segments or at least its a guess for me where I'm at or what waypoint I'm approaching. I'm using GE virtual flight on one screen and have the mission hub up on the other screen, regularly checking WP drone heading, gimbal angle & altitude, so my eye isn't always on the virtual flight path. I'm also trying to figure out why sometimes my flight path seems "off" from what I show on the mission hub.You can see the segments where they connect - that's your waypoints.
Thanks. And that's a good question!Just tried it out and it is fantastic! Thank you so much!
When I compared the actual footage with the virtual mission, I notice that the FOV in Google Earth is slightly wider, just wondering if the FOV setting is diagonal or horizontal. When I adjust it from 78 to 70, it matches perfectly with the actual footage.
It shouldn't be necessary to have Google Earth running before VLM - as long as .kml files are associated with Google Earth then GE should start up automatically. At least it does for me.Don't pretend to know why this would happen, but aside from rebooting, I would try having Google Earth already running.
VLM checks to see if Google Earth is installed before doing anything else. If GE is not installed in the normal way (ie standard entries in the registry) then this warning is given. However, it is only a warning - VLM will continue to run but GE may not!I got this error: 12/26/2017 11:27:11 PM - Warning - Google Earth Pro does not appear to be installed. Please Check.
What does it mean?
My Google Earth is in this directory: "C:\Program Files (x86)\Google\Google Earth Pro\client\googleearth.exe"
Sadly there are no parameters I can provide to Google Earth to control the smoothness - I use the parameter <gx:flyToMode> and the only options Google provide are "smooth" or "bounce". The smoothed VLM VirtualFlight will therefore not fly exactly along the smoothed 3DPath from Litchi - especially near large course changes. You can certainly help things along by inserting more waypoints near curves and not having large heading or gimbal changes between waypoints but I fear it will never be exact.I see that but when some waypoints are further from others I don't always see the segments or at least its a guess for me where I'm at or what waypoint I'm approaching. I'm using GE virtual flight on one screen and have the mission hub up on the other screen, regularly checking WP drone heading, gimbal angle & altitude, so my eye isn't always on the virtual flight path. I'm also trying to figure out why sometimes my flight path seems "off" from what I show on the mission hub.
Look at the two screen shots attached. The mission hub screenshot shows the path of the drone; however the Google Earth Virtual flight appears to show the drone around 50+ feet "off" or away from the path shown on the mission hub (frame posted is about 1/2 way between wp 3 & 4)... Is this because GE is showing the center of the screen of where the gimbal would be seeing? I've noticed this in several missions I've done virtual missions for. If I remember, when the drone is flying straight and heading is in line with flight it looks as expected... View attachment 27486 View attachment 27487
It appears there may be a way to position an icon - like their location markers.Is there any way to optionally show waypoints on the virtual mission? Some missions have 30+ waypoints and it would be nice to follow along on the mission hub site to verify height, camera angle, etc. as a waypoint approaches.
I extracted the flight path and replaced the altitudes with the relative heights as specified at the waypoints. Then changed the altitude mode to relativeToGround and loaded. The paths match perfectly near as I can tell. Just an FYIThe altitudes in the Litchi csv file are all relative to the Home Point and Google Earth does not know anything about this - so somehow we have to tell GE the reference height..
I remember futzing with GE awhile back, doing what... don't remember, but somehow I turned on altitude numbers above each waypoint.It appears there may be a way to position an icon - like their location markers.
It would be on the ground tho and not much use if you were looking straight ahead.