imagiscope / EarthStudioTools

Blender Panel to import Google Earth Studio, KML Routes, and 3D Masking
Other
169 stars 29 forks source link

problems kml files rustas without sense #14

Open Serendipiaciencis opened 1 year ago

Serendipiaciencis commented 1 year ago

Hi, I'm new to this, I'm Spanish and I'm writing this translated text. I have done many tests but when trying to import the KML file in blender I get misconfigured, the first point is fine but the following points are very high, even setting the match proximity to 1000 m I can't get it to work well, I have even cut the routes in case they were very long, it has only worked well for me in a test starting the animation in GES in the first frame seeing the first point of the route and the last frame the last point of the route, but when doing the route that I want it does not work out, even putting in the animation in the GES in the first frame where the route begins. I still want something that is impossible since the animation begins by seeing the entire country, then it takes a flight to the first point of the route, and that is where my route would have to start. I have set many breadcrumbs or tracking points in GES. I'm not desperate I've been trying for more than 2 weeks. If someone wants to see my files to see where I have the problem I will be happy to send them to you. Thank you.

Serendipiaciencis commented 1 year ago

image

image

It goes up as if it were wrongly oriented, I don't know if it is seen in the images. image The JSON file is the same I use to import the animation as I use to import the KML file with the FOLLOW TERRAIN option. Since this "JSON" file has the tracking points as can be seen in the first image.

Gavinski98109 commented 1 year ago

I experienced the same issue.

The problem seems to be caused when using fast zooms. GES has a feature called "logarithmic altitude" to help render the quick transition from a global view to ground view. This seems to mess with the altitudes and scales them out of sync with the original altitude data.

To fix it, go in and turn this OFF:

Animation > Advanced > Logarithmic Altitude.

This fixed it for me.

imagiscope commented 1 year ago

The proximity is in meters from a potential trackpoint. The KML will have points along the path - that's what it's trying to match.

Make sure your trackpoints (that you added in GES) are in areas where a point on the KML file will be, usually when there is a corner or intersection.

Rob

On Sat, Nov 19, 2022, 10:37 a.m. Gavinski98109 @.***> wrote:

I am having the same problem. If I increase the "Match Proximity" number (+100) in Blender, it aligns the path, but it fails to adjust in altitude and match the track points.

— Reply to this email directly, view it on GitHub https://github.com/imagiscope/EarthStudioTools/issues/14#issuecomment-1320931372, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVJ672OWAX2IGGLG62E44LWJEF4DANCNFSM6AAAAAARTBVV5Y . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Gavinski98109 commented 1 year ago

Hi Rob,

I edited the original comment on GitHub after doing some troubleshooting. It looks like using the starting templates in GES (Zoom to, Orbit etc) with Logarithmic Altitude mess with the export. Once I turned that off, the KML and track points all worked perfectly.

BTW, your videos on YouTube are next level in terms of clarity and value. And I really appreciate the work you have done with the add-on.

Thank you!

Gavin

On Nov 21, 2022, at 2:39 PM, Rob @.***> wrote:



The proximity is in meters from a potential trackpoint. The KML will have points along the path - that's what it's trying to match.

Make sure your trackpoints (that you added in GES) are in areas where a point on the KML file will be, usually when there is a corner or intersection.

Rob

On Sat, Nov 19, 2022, 10:37 a.m. Gavinski98109 @.***> wrote:

I am having the same problem. If I increase the "Match Proximity" number (+100) in Blender, it aligns the path, but it fails to adjust in altitude and match the track points.

— Reply to this email directly, view it on GitHub https://github.com/imagiscope/EarthStudioTools/issues/14#issuecomment-1320931372, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVJ672OWAX2IGGLG62E44LWJEF4DANCNFSM6AAAAAARTBVV5Y . You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fimagiscope%2FEarthStudioTools%2Fissues%2F14%23issuecomment-1322747568&data=05%7C01%7C%7Cf88ba8ce9efc4f3b28ff08dacc1134ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638046671508200126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FUUbsypWNZQ%2BdLLedBQTGz%2BfA0710NkG0yG%2Fk3pULtw%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATDYTWYZ7GILZRX4LPMXUCTWJP2YZANCNFSM6AAAAAARTBVV5Y&data=05%7C01%7C%7Cf88ba8ce9efc4f3b28ff08dacc1134ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638046671508200126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=opHC6ORlU0qheYdlgm50k6s1mL2upk%2Fc3BNn%2F%2BQcOwc%3D&reserved=0. You are receiving this because you commented.Message ID: @.***>

imagiscope commented 1 year ago

Awesome, thanks for the update!

On Mon, Nov 21, 2022, 3:55 p.m. Gavinski98109 @.***> wrote:

Hi Rob,

I edited the original comment on GitHub after doing some troubleshooting. It looks like using the starting templates in GES (Zoom to, Orbit etc) with Logarithmic Altitude mess with the export. Once I turned that off, the KML and track points all worked perfectly.

BTW, your videos on YouTube are next level in terms of clarity and value. And I really appreciate the work you have done with the add-on.

Thank you!

Gavin

On Nov 21, 2022, at 2:39 PM, Rob @.***> wrote:



The proximity is in meters from a potential trackpoint. The KML will have points along the path - that's what it's trying to match.

Make sure your trackpoints (that you added in GES) are in areas where a point on the KML file will be, usually when there is a corner or intersection.

Rob

On Sat, Nov 19, 2022, 10:37 a.m. Gavinski98109 @.***> wrote:

I am having the same problem. If I increase the "Match Proximity" number (+100) in Blender, it aligns the path, but it fails to adjust in altitude and match the track points.

— Reply to this email directly, view it on GitHub < https://github.com/imagiscope/EarthStudioTools/issues/14#issuecomment-1320931372>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AOVJ672OWAX2IGGLG62E44LWJEF4DANCNFSM6AAAAAARTBVV5Y>

. You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fimagiscope%2FEarthStudioTools%2Fissues%2F14%23issuecomment-1322747568&data=05%7C01%7C%7Cf88ba8ce9efc4f3b28ff08dacc1134ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638046671508200126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FUUbsypWNZQ%2BdLLedBQTGz%2BfA0710NkG0yG%2Fk3pULtw%3D&reserved=0>, or unsubscribe< https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATDYTWYZ7GILZRX4LPMXUCTWJP2YZANCNFSM6AAAAAARTBVV5Y&data=05%7C01%7C%7Cf88ba8ce9efc4f3b28ff08dacc1134ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638046671508200126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=opHC6ORlU0qheYdlgm50k6s1mL2upk%2Fc3BNn%2F%2BQcOwc%3D&reserved=0>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/imagiscope/EarthStudioTools/issues/14#issuecomment-1322764889, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVJ677JO5BEUBBKAEZEEOTWJP4VXANCNFSM6AAAAAARTBVV5Y . You are receiving this because you commented.Message ID: @.***>