search

Kazu46Machi / earth-api-samples

Automatically exported from code.google.com/p/earth-api-samples
0 stars 0 forks source link

model disapears when its altitude increases #120

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. create a model @ (lat, lon, 0). 
2. move it step by step to (lat, lon, ++) and look at it (freq: 500ms)
3.

What is the expected output or behavior? What do you see instead?
The model flicks/disappears as the altitude grows

Which plugin version are you using?
4.3.9684.6498. it also happends with google earth application

Which browsers and operating systems are affected?
Windows 2000 Professionnal/ WINdows XP
Firefox 3.0.4

Please provide any additional information (code snippets/links) below.
see the attachment. note that I have removed my API KEY, you have to set it
in the demo.html file (replace <YOURKEY>)

note: the model may be long to load...

Original issue reported on code.google.com by dao.ho...@gmail.com on 12 Dec 2008 at 10:48

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by api.roman.public@gmail.com on 12 Dec 2008 at 6:22

GoogleCodeExporter commented 8 years ago 
you can check it live here : http://www.paraglidingearth.com/pgSim 
the model disappear/reappears often

Original comment by trujillo...@gmail.com on 22 Jan 2009 at 10:41

GoogleCodeExporter commented 8 years ago 
I have the same problem with my small plane. Over an altitude of 300m the plane 
often
disapears.

http://www.sea-seek.com/3d/San_Francisco_Bay
Use the left/down arrows to change the altitude of the plane.

Regards

André

Original comment by andre.bu...@gmail.com on 2 Feb 2009 at 1:37

GoogleCodeExporter commented 8 years ago 
any news on the problem ?
this really gives 'aerial' applications a bad rendering !
thanks for setting is up !

Original comment by trujillo...@gmail.com on 5 Apr 2009 at 9:32

GoogleCodeExporter commented 8 years ago 
I'm having the exact same issue, it is making the use of the API a non-option

Original comment by andreada...@gmail.com on 6 Apr 2009 at 7:34

GoogleCodeExporter commented 8 years ago 
The new release 5 of the plug-in didn't solve the problem...
www.sea-seek.com

André

Original comment by andre.bu...@gmail.com on 9 Apr 2009 at 8:38

GoogleCodeExporter commented 8 years ago 
Issue 218 has been merged into this issue.

Original comment by api.roman.public@gmail.com on 13 Apr 2009 at 5:23

GoogleCodeExporter commented 8 years ago

Original comment by api.roman.public@gmail.com on 22 May 2009 at 1:39

GoogleCodeExporter commented 8 years ago

Original comment by api.roman.public@gmail.com on 22 May 2009 at 1:56

GoogleCodeExporter commented 8 years ago

Original comment by api.roman.public@gmail.com on 22 May 2009 at 1:56

GoogleCodeExporter commented 8 years ago 
Related issue: http://code.google.com/p/kml-samples/issues/detail?id=283

Original comment by api.roman.public@gmail.com on 11 Jun 2009 at 9:53

GoogleCodeExporter commented 8 years ago 
Issue 275 has been merged into this issue.

Original comment by api.roman.public@gmail.com on 26 Jun 2009 at 10:18

GoogleCodeExporter commented 8 years ago 
Bulk edit.

Original comment by api.roman.public@gmail.com on 9 Aug 2009 at 1:02

GoogleCodeExporter commented 8 years ago 
Really really could do with this being an editable option, so we can specify 
the near
clipping plane. I'm trying to render planes in the air, and although it can be 
got
around by adjusting the scale of the object, it really isn't a good solution!

Original comment by ad...@rockitg.com on 2 Dec 2009 at 5:19

GoogleCodeExporter commented 8 years ago 
I have the same problem... any idea to fix this bug? Tks

Original comment by rfslo...@netcabo.pt on 9 Dec 2009 at 11:55

GoogleCodeExporter commented 8 years ago 
We are also struggling with this problem.  Until it is solved, GE is not an 
option for rendering our flying 
competition data, although we are left with few alternatives.  Some visibility 
from the developers about when this 
might get solved would really help up to choose where to focus our efforts.  
Please can we have an update?

Original comment by ricsea...@googlemail.com on 13 Dec 2009 at 12:52

GoogleCodeExporter commented 8 years ago 
Please can we have an update on this?

Original comment by ad...@rockitg.com on 18 Dec 2009 at 10:41

GoogleCodeExporter commented 8 years ago 
I've got the same problem.
How can i fix it ?

Thanks

Original comment by hollow...@gmail.com on 21 Dec 2009 at 6:52

GoogleCodeExporter commented 8 years ago 
I wonder what we have to do to raise the priority from "Medium" to "Critical"? 
It was reported over 12 months ago, accepted as a bug and has been starred by a 
score
of users.
I just hope that it's not a case of a bug in a piece of 3rd party software over 
which
GE has no control. 
Please tell me this is not the case.

Original comment by gpsanima...@gmail.com on 22 Dec 2009 at 10:56

GoogleCodeExporter commented 8 years ago 
Same problem. This issue really ruines the simulation. How can it be fixed??

Original comment by zivotd...@gmail.com on 10 Jan 2010 at 9:45

GoogleCodeExporter commented 8 years ago 
Hi there
I have the same problem as everybody here so far. However, as the effect 
depends on 
the altitude AND on the scale of the object, I decided to make the scale as a 
function of the objects current altitude. The scale is then in a range of 1 
(near 
ground) to 25 (at an altitude of 14000 meters). For showing airplanes this is a 
reasonable solution. Especially, if you watch airplanes from high above (>= 100 
km), 
the higher ones can be recognized very good, which helps a lot. However, I 
would 
also be really happy if the developers could finally solve the problem!!
Any feedbacks on this comment on this are welcome. Cheers, Albert

Original comment by albert.s...@gmail.com on 16 Jan 2010 at 7:27

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Has anyone found a work-around?  My application is for a gliding contest with
multiple gliders. I scale the models with altitude, but they still disappear 
quite
far away and increasing the scale even more doesn't make it realistic.  Is 
there a
way to make this a higher priority?

http://www.withonestone.com/tracker/tracker.html

Original comment by dbonni...@gmail.com on 28 Feb 2010 at 6:36

GoogleCodeExporter commented 8 years ago 
Surely this can’t be that hard to fix, it’s a known defect with a known 
solution. 
How about a date for a fix?.

Original comment by nutwoo...@gmail.com on 19 Apr 2010 at 8:59

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I know that it's policy for Google not to provide any information about future
features or releases, but this one has been around for 15 months!!!
Some feedback from the developers would be greatly appreciated.

Original comment by gpsanima...@gmail.com on 27 Apr 2010 at 5:00

GoogleCodeExporter commented 8 years ago 
I left my summer internship last year thinking that surely this would be fixed 
by the 
time I returned a year later. This bug report has been open for a year and a 
half now, 
and it's a major dealbreaker for anyone trying to do aerial or space 
visualizations. 
Google Earth could be an awesome tool for space animations and teaching 
tools--it's a 
shame nobody has found time in the last 16 months to fix this.

Original comment by snietf...@gmail.com on 3 Jun 2010 at 1:26

GoogleCodeExporter commented 8 years ago 
this should be a serious bug, maybe google limits this feature by design.

Original comment by youquan...@gmail.com on 8 Jun 2010 at 1:41

GoogleCodeExporter commented 8 years ago 
"maybe google limits this feature by design" 
problem is that we can just guess : at least we would appreciate having a 
feedback from google on it....
same comment here that about the linux port : the total silence from google 
about issues/enhancements is more frustrating than the issues themselves for 
coders....

Is anybody from google reading this issue reports page ?????

Can we hopep to have the issues worked on one day, or must we just work on 
hacks to avoid them ?? please let us know...

Original comment by trujillo...@gmail.com on 8 Jun 2010 at 2:13

GoogleCodeExporter commented 8 years ago 
Thanks for the comments.  Please note that this is not limited on purpose.  
I'll be updating this ticket again as soon as we have a fix in place.

Original comment by jli...@google.com on 8 Jun 2010 at 6:09

GoogleCodeExporter commented 8 years ago 
You have no idea how rewarding it is to finally receive a response from Google 
on this issue. After so long, to get a glimmer of hope that someone is working 
on it gives me great joy. 
I don't know how many of us 3D animators there are out there, but at least 20 
of us are hanging out for this to be fixed.
We applaud you for a fantastic product and wish you well for an early fix.

Original comment by gpsanima...@gmail.com on 8 Jun 2010 at 11:18

GoogleCodeExporter commented 8 years ago 
That great news! it'll be very helpful...
Thanks in advance for your effort.

Original comment by pablo...@gmail.com on 9 Jun 2010 at 9:35

GoogleCodeExporter commented 8 years ago 
thank you really for letting us know you are watching this :)
this is indeed good news ;)

Original comment by trujillo...@gmail.com on 9 Jun 2010 at 11:08

GoogleCodeExporter commented 8 years ago 
Good to hear that Google will address this issue, I am also in a great need for 
this to be fixed!

Original comment by o...@unifis.no on 16 Jun 2010 at 10:16

GoogleCodeExporter commented 8 years ago 
Download the latest version 5.2  You will find it is fixed. Not sure why it is 
still open here

Original comment by vandint...@gmail.com on 16 Jun 2010 at 10:33

GoogleCodeExporter commented 8 years ago 
It does appear to be sorted but you need 5.2.1, 5.2.0 doesn't work. Hurray for 
peer pressure.

Original comment by nutwoo...@gmail.com on 16 Jun 2010 at 12:34

GoogleCodeExporter commented 8 years ago 
sweeeeeeeeeeeet  !!!!!!!
after months of silence from google, 12 days have been enough to fix the issue 
after reaction !!
congratulations and huge thanks for that !!!

now, let s hope the linux port will be as efficiently worked on ;)

Original comment by trujillo...@gmail.com on 16 Jun 2010 at 2:09

GoogleCodeExporter commented 8 years ago 
Lo and behold! It works!! And thank you very much for the tip to use version 
5.2.1 (I had 5.2.0)

Original comment by o...@unifis.no on 16 Jun 2010 at 2:50

GoogleCodeExporter commented 8 years ago 
Fixed in 5.2.1.1329

Original comment by jli...@google.com on 16 Jun 2010 at 3:16

GoogleCodeExporter commented 8 years ago 
Incredible but true!!

Now I can see high-altitude aircraft, as well as their behavior has become much 
more smooth and fluid!

Finally, Google Earth is the right tool for our distributed real-time displays.

Thank you very much!

Original comment by pablo...@gmail.com on 16 Jun 2010 at 3:50

GoogleCodeExporter commented 8 years ago 
Unfortunately this bug is NOT fixed for objects at satellite altitudes.  GPS 
orbit lines are clipped in the distance (see file):

Also see:

http://code.google.com/p/earth-api-samples/issues/detail?id=353

v5.2.1.1329 (beta), Mac OS X

Original comment by john.co...@gmail.com on 16 Jun 2010 at 4:15

Attachments:

GoogleCodeExporter commented 8 years ago 
Correct, issue #353 is still open.  Please feel free to follow that issue 
directly for followups.

Original comment by jli...@google.com on 16 Jun 2010 at 8:36