maholm
First Post
Reged: 03/14/07
Posts: 1
|
|
I am working on connecting a satellite simulator to Google Earth with the COM interface. It is really cool to see the ground path of the satellite in Google Earth.
I am using a periodic timer to call the set camera function (using the teleport mode), but when the camera is really close to the Earth the view starts jumping up and down. Despite the fact that the data being sent is stable in elevation. I can see the Eye alt going up and down (and this is with my simulator paused, so no of the parameters to the COM functions change).
I assume that this is a bug in in the COM interface. Does anyone have a good workaround?
Edited by maholm (03/14/07 10:11 AM)
|
luca63
Tourist
Reged: 04/02/06
Posts: 34
Loc: Italy - Rome
|
|
yes i get similar situation ...that bug makes impossible to use setcamera ...only workaround i found ...(unacceptable in my opinion) .... set terrain layer off 
--------------------
Luca Rocchi
http://www.googleearthairlines.com
http://www.musicdyne.com
|
TutorPilot
Tourist
Reged: 11/18/06
Posts: 4
|
|
Yes, I get the same thing in my flight simulator. There are two separate problems: (1) the transition from one camera view to another and (2) a random jitter.
The view transition is not so much a bug as a design flaw. GE has this fancy swooping transition that looks great in interactive mode, where it flies you from one place to another. The design error is that there is no way to turn it off. So to get from position A to position B, which may only be a few feet away, it will try to fly you on its own trajectory. It wouldn't be so bad for small distances except that the last step of the "flight" is to take the viewer down to ground level at the destination and climb back up to the specified viewing altitude. Sometimes, it never makes it up to the specified altitude. This really sucks, and makes the API unusable for all kinds of applications, and it is totally unnecessary. Just let us turn the @#$% thing off!!
While I am bitching, how about allowing us to specify a bank angle. The viewer is capable of it, you just can't specify it from the API. Geez, who designed this thing, an eight-year-old?
The random jitter looks like a true bug. The viewing position appears stable, but the picture displays this rapid (5-6 x per second) jitter.. It appears mostly at high altitudes.
For simulators of all kinds, we need to wait until GE releases a real production version of the API. Unfortunately, they only do "beta" releases, so that is not likely to happen in our lifetimes.
TutorPilot
|
luca63
Tourist
Reged: 04/02/06
Posts: 34
Loc: Italy - Rome
|
|
as someone said in another (or maybe this) thread the flickering appear even if you call setcameraparams twice using the same parameters ...
no one can convince me that to fix it more then an "IF" statement is needed....
something like if newpos=oldpos then donothing ! 
--------------------
Luca Rocchi
http://www.googleearthairlines.com
http://www.musicdyne.com
|
tobedetermined
First Post
Reged: 03/22/07
Posts: 1
|
|
Hi all,
I am writing a python script to read the position from the Google Earth client but for some reason when I turn the globe or move inside Google Earth while running the script, the speed at which the camera parameters are read out is slowed down to apprx. once per second, while if I am still in Google Earth, the refresh rate of the update is much faster. Does anybody have an idea whether this is a fixed problem (e.g. by the fact that I actively move in GE), or is there a way around such that I can read out the camera parameters at sub second resolution even while moving the virtual globe or manouvering around?
Thanks
|
Previous
Index
Next
Threaded
[Re: 
Edit
Reply
Quote
