Virtual Litchi Mission

[bjk896]

In your Google control panel, check if your key has "API Restrictions" set to "Don't restrict key",

Yes I did check that and enabled the whole pack of API's in the suite to see what happened. That changed nothing so went back to the 'normal' restricted suite.

 

[bjk896]

I use VLM often and have my own Google Elevation API key. The VLM elevation profile is empty for me whether I am using my own key or using the shared key. I don't think I've seen that work in years.

Wes, that might suggest in some obscure way it is a Windows issue not a Google or VLM. I have always had the profile show when using the Litchi key. As soon as I drop my own key into it, it isnt there and ten seconds leter I revert to Litchi key, and I have it..
Do you use windows ? I cant even imagine at this point a connection.

 

[DJ Wes]

Do you use windows ? I cant even imagine at this point a connection.

Yes, Windows 11. I remember, it used to sometimes work but I can't say long ago that was. Now, it does not work for me with or without my API key.

 

[bjk896]

Yes, Windows 11. I remember, it used to sometimes work but I can't say long ago that was. Now, it does not work for me with or without my API key.

I too am Win 11 for whatever that might mean.
I find the Elevation profile gives me a first in level of elevation comfort, and a warning not to screw with gravity or big rocks/hills and relook safely at what I'm traversing or my Waypoint locations for what I want to do..
Is there another app or approach which will give me this same simple view ? Google Earth does to a point but without any level of security
Maybe Namirda can come in again and offer his wisdom ?

To add to RodPad's question about how often I plan a mission. I have a relatively light demand, say 1-3 missions a week and that involves a bit of adjustment and playing with the whole mission to get the video I want with the subsequent calls on the Elevation Key and GE. BUT the occasions when Namirda's key is over quota is probably 50% which means a lot of other fellas are using it too and sending it over limit. My going to my own key was to give me what I wanted when I wanted it - That might relieve the (small) load I had placed on the rest of the population.

 

[SkyAngel1]

Question about passwords for virtual Litchi Mission desktop.
I did forget my password so I used the reset password and received an email to reset it. When I did it still says I do not have the right password. Is this a bug or am I doing something wrong?

Update:
Figured it out, user error.

 

[RodPad]

@SkyAngel1,

I have spaced out a few times, had to look up my VLM password, I forgot again same as Litichi.
Is that related to your posts?

Rod ..

 

[SkyAngel1]

@SkyAngel1,

I have spaced out a few times, had to look up my VLM password, I forgot again same as Litichi.
Is that related to your posts?

Rod ..

Sounds about right

 

[namirda]

I wonder why I never get notified when there are new posts on this thread? Does it work for others?

Just noticed the recent comments about the API key. A month or so ago I started getting unwelcome charges from Google due to the default API key used in VLM. It seems Google have drastically reduced the number of API calls which can be made for free - I was not aware of the changes and so it caught me unawares. As a result I have had to reduce the quota on the default API by about 90% which explains why you are maybe seeing the "Quota Exceeded" message more regularly.

The elevation profile window works for me all the time and I am just using the default key.

I have just checked the settings for my account in console.cloud.google.com and I see that "Maps Javascript API" is enabled as well as the expected "Maps Elevation API". I have no recollection of enabling it - perhaps it is the default.

There is quite some javascript used in VLM and so maybe the "Maps Javascript API" is required - I don't use it explicitly but Google are not always transparent about these things. It might be worth enabling "Maps Javascript API" in your account to see if it makes any difference.

If that doesn't help then perhaps somebody could take a look in the developer console in your browser next time you have a problem with the elevation profile window.

Thanks

N

 

[DJ Wes]

I wonder why I never get notified when there are new posts on this thread? Does it work for others?

I receive notifications for posts to this thread. Check the top of the page and see if it says "Watch" or "Unwatch". Mine says "Unwatch" which means I am watching (receiving updates for this thread).

Just noticed the recent comments about the API key. A month or so ago I started getting unwelcome charges from Google due to the default API key used in VLM. It seems Google have drastically reduced the number of API calls which can be made for free - I was not aware of the changes and so it caught me unawares. As a result I have had to reduce the quota on the default API by about 90% which explains why you are maybe seeing the "Quota Exceeded" message more regularly.

Google has changed their pricing model. I use a number of their services. They used to give you $200 credit per month. Now, it is a number of SKUs that are free. For example, you can only have 5000 elevation calls per month before you are charged. I've had to greatly reduce the quotas that I had set up.

The elevation profile window works for me all the time and I am just using the default key.

For the past year or so mine has always said "No Profiles Available". I just figured it no longer works.

I have just checked the settings for my account in console.cloud.google.com and I see that "Maps Javascript API" is enabled as well as the expected "Maps Elevation API". I have no recollection of enabling it - perhaps it is the default.

I use thee Maps Javascript API for a different project with a different key. For the key that I use with Litchi utilities I only have Maps Elevation API enabled. I can try enabling the Javascript API and see if that makes a difference.

 

[DJ Wes]

There is quite some javascript used in VLM and so maybe the "Maps Javascript API" is required - I don't use it explicitly but Google are not always transparent about these things. It might be worth enabling "Maps Javascript API" in your account to see if it makes any difference.

I have tried setting my key to "unrestricted" so that it can use any API. No change.

If that doesn't help then perhaps somebody could take a look in the developer console in your browser next time you have a problem with the elevation profile window.

I've tried looking at the developer console (gear icon). I don't see any errors. Is there something specific to look at?

I also tried resetting VLM (ctrl-click). No change.

Whether "Altitudes" or "Heading and Gimbal Angles" is selected, the bottom window pane displays "No Profiles Available".