Google Earth Jerky Movement

I have the latest version of Google Earth 6 (6.0.2.2074) and am extremely disappointed at the choppy / jerky movement I am seeing. I have a mid 2010 15" MacBook Pro Intel Core i7 2.66 GHz with NVIDIA GeForce GT 330M 512MB GPU. My internet speed should be adequate at 8MB.
I have tried downloading earlier versions of Google Earth, 4 and 5 but these have the same issue on my machine. I've tried disabling all of the layers and turning off effects in the Google preferences panel. I've also tried using a smaller window. The jerky / choppy movement is always present.
While Google Earth is very stable and so far has never quit on me - this glitch is very irksome.
Is this 'normal' for Google earth on a MacBook Pro?

The problem is not flash related.
I booted into my XP partition and found the performance to be exactly the same. So, it's either the case that the hardware of my MacBook isn't up to the job - or Google Earth just does not produce smooth flowing graphics.
I may take a trip to the Apple Store and try out Google Earth on some other 'desktop' Macs.

Similar Messages

Can't launch i movie or Google Earth since leopard installed.

Keep getting IMovie and Google Earth message "quit unexpectedly". Added Leopard and Ilife o8 since last night.
Also are all the updates being offerd by Apple because of Leppard.

Upgraded the OS? This is usually an installation issue. There is an easy fix. Do a forum search for ProKit.

Where did Google Earth go when I upgraded to the latest version of Firefox?

I clicked the popup that upgraded to the latest version of Firefox - and clicked to give it permission to make changes to my computer - and my Google Earth was no longer there. I restored my computer to before I had made the Firefox changes and my Google Earth was there but I got a blank page when I tried to open Firefox. Then I re-downloaded Firefox and Google Earth is gone. I would like to have both. If I have to do without one I would give up Firefox and use Internet Explorer until the problem gets fixed.

''andy_blunden [[#question-1057157|said]]''
<blockquote>
When I drag messages from the Inbox to another folder for archiving, they don't move. This problem has only arisen since I updated to the latest version of Thunderbird.
</blockquote>
I doubt it is a Norton Security problem. Maybe. I solved it by deleting the account and re-installing it.

[SOLVED] Google Earth doesn't work with xf86-video-ati

Hi all,
I'm having a problem with the open-source ATI drivers. I haven't had much luck finding out anything from anywhere else, so I'm hoping someone here can help.
Whenever I start Google Earth, the graphics run EXTREMELY slowly, almost as if it's running on a system with low memory. I'm running an Acer Extensa 4420 with an AMD Athlon 64 X2 dual-core 64-bit processor with 2GB of RAM. As mentioned before, I'm running on the open-source xf86-video-ati drivers, but this is the only app that gives me problems. GL screensavers run fine, and glxgears runs without any significant input. Running Google Earth in terminal also gives no output.
And I'm not sure if this is related, but closing Google Earth also crashes X.
Here's xorg.conf:
Section "Module"
Load "extmod"
Load "dbe"
Load "record"
#Free86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
# Load "type1"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"
Load "drm"
Load "synaptics"
EndSection
# Files section. This allows default font and rgb paths to be set
Section "Files"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
EndSection
# Server flags section.
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
Option "DontZap" "no"
# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
Option "AutoAddDevices" "False"
EndSection
# Input devices
# Core keyboard's InputDevice section
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "acer_laptop"
Option "XkbLayout" "us,de"
Option "XkbOptions" "grp:lwin_switch,grp_led:num,eurosign:e"
EndSection
# Core Pointer's InputDevice section
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
Section "InputDevice"
Identifier "Touchpad"
Driver "synaptics"
Option "AlwaysCore" "true" # send events to CorePointer
#Option "Device" "/dev/input/mice"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "SHMConfig" "false" # configurable at runtime? security risk
Option "LeftEdge" "1700" # x coord left
Option "RightEdge" "5300" # x coord right
Option "TopEdge" "1700" # y coord top
Option "BottomEdge" "4200" # y coord bottom
Option "FingerLow" "25" # pressure below this level triggers release
Option "FingerHigh" "30" # pressure above this level triggers touch
Option "MaxTapTime" "180" # max time in ms for detecting tap
Option "VertEdgeScroll" "true" # enable vertical scroll zone
Option "HorizEdgeScroll" "true" # enable horizontal scroll zone
Option "CornerCoasting" "true" # enable continuous scroll with finger in corner
Option "CoastingSpeed" "0.30" # corner coasting speed
Option "VertScrollDelta" "100" # edge-to-edge scroll distance of the vertical scroll
Option "HorizScrollDelta" "100" # edge-to-edge scroll distance of the horizontal scroll
Option "MinSpeed" "0.10" # speed factor for low pointer movement
Option "MaxSpeed" "0.60" # maximum speed factor for fast pointer movement
Option "AccelFactor" "0.0020" # acceleration factor for normal pointer movements
Option "VertTwoFingerScroll" "true" # vertical scroll anywhere with two fingers
Option "HorizTwoFingerScroll" "true" # horizontal scroll anywhere with two fingers
Option "TapButton1" "1"
Option "TapButton2" "2"
EndSection
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Acer Laptop"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5 - 57.0
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-90
EndSection
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "ATI Radeon"
Driver "radeon"
#VideoRam 262144
# Insert Clocks lines here if appropriate
Option "AGPMode" "4"
Option "ColorTiling" "on"
Option "AccelMethod" "EXA"
Option "EnablePageFlip" "on"
Option "AGPFastWrite" "yes"
Option "EXAVSync" "yes"
Option "ForceTVOut" "true"
Option "TVStandard" "ntsc"
EndSection
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "ATI Radeon"
Monitor "Acer Laptop"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1200x800"
ViewPort 0 0
EndSubsection
EndSection
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Touchpad" "SendCoreEvents"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "DRI"
Mode 0666
EndSection
Here's my drirc:
<driconf>
<device screen="0" driver="r300">
<application name="Default">
<option name="force_s3tc_enable" value="false" />
<option name="texture_coord_units" value="8" />
<option name="fthrottle_mode" value="2" />
<option name="disable_stencil_two_side" value="false" />
<option name="tcl_mode" value="3" />
<option name="texture_depth" value="0" />
<option name="fp_optimization" value="0" />
<option name="def_max_anisotropy" value="1.0" />
<option name="no_rast" value="false" />
<option name="command_buffer_size" value="8" />
<option name="round_mode" value="0" />
<option name="dither_mode" value="0" />
<option name="disable_lowimpact_fallback" value="true" />
<option name="texture_image_units" value="8" />
<option name="disable_s3tc" value="false" />
<option name="color_reduction" value="1" />
<option name="vblank_mode" value="1" />
</application>
<application name="Google Earth" executable="googleearth">
</application>
</device>
</driconf>
Last edited by coolpyrofreak (2009-07-03 05:56:18)

I had the same problem (slow googleearth) with ATI Technologies Inc Radeon Mobility U1 (IGP 320m).
This .drirc solves it. I don't have an xorg.conf.
- no need for the 'disable_lowimpact_fallback' option
- no need to turn off 'atmosphere'
cat .drirc
<driconf>
<device screen="0" driver="radeon">
<application name="Default">
<option name="force_s3tc_enable" value="false" />
<option name="no_rast" value="false" />
<option name="fthrottle_mode" value="2" />
<option name="tcl_mode" value="3" />
<option name="texture_depth" value="0" />
<option name="def_max_anisotropy" value="1.0" />
<option name="no_neg_lod_bias" value="false" />
<option name="texture_units" value="3" />
<option name="dither_mode" value="0" />
<option name="hyperz" value="true" />
<option name="round_mode" value="0" />
<option name="color_reduction" value="1" />
<option name="vblank_mode" value="0" />
<option name="allow_large_textures" value="1" />
</application>
</device>
</driconf>

New Google Earth does not run on my 24" iMac

This morning I downloaded and installed the new Google Earth 4.0.2 beta on my 24" iMac. GE loads but crashes as soon as I attempt to navigate to any where. Now I am trying to download the previous version 3 from Google but it just downloads the newest beta and because I told the new version to replace my old version I have no version. Any body else having the same problem? I have 2.16, 2gig, 7600, 500MB iMac.
24" iMac Mac OS X (10.4.8)

It runs fine here. Since you are having the same problem on the new machine, and the machine you migrated from (sounds like you migrated your Home folder) why don't you try this:
1. Quit Google Earth
2. Navigate to ~/Library/Preferences (Note: "~" is the Short Name for your user account, which can be viewed in System Preferences --> Accounts)
3. Move the file 'com.Google.GoogleEarthPlus.plist' to your Desktop.
4. Relaunch Google Earth and see if the problem persists.

Lion + Safari made Google Earth stop working properly

Upgraded to Lion now Google Earth Plugin won't work on Safari anymore. It works perfectly on Firefox, Chrome and Opera. I would like to keep using...please help. Thanks.
It worked FLAWLESSLY (Safari & Google Earth) on Snow Leopard before upgrading to Lion.

No problem using Google Earth with Safari 5.1.1 on Lion v10.7.2 here.
Perhaps the preferences are corrupted.
Go to ~/Library/Preferences
Move the following files to the Trash.
com.google.GoogleEarthPlugin.plist
com.GoogleEarthPlus.plist
com.GoogleEarthPlus.plistlockfile
Restart your Mac. Try launching Google Earth.
~ (Tilde) character represents the Home folder.
For Lion: To find the Home folder in OS X Lion, open the Finder, hold the Option key, and choose Go > Library

Google Earth hangs Firefox 10.0.2

I'm seeing Firefox hang when using Google Maps. Specifically when switching to the Google Earth option on Google Maps. The problem is most likely to happen during rotations to view the horizon but can also crash when just moving around.
I didn't used to have this problem on older Firefox versions (3.x) and the problem currently does not occur on Google Chrome or IE9.
I think it may have something to do with OpenGL since it's using 3D rendering. I am using Windows 7 with an NVIDIA GeForce 8800 and have updated the drivers to see if that fixed it but to no effect.
Could Google be pulling a Microsoft and making it so the app does not work well? Not my real question, just thinking out loud.
Real question is does anyone else see this problem?
Details:
Windows 7
Firefox 10.0.2
8GB RAM
Dual Monitor (occurs on either monitor)
GeForce 8800 latest drivers
Problem varies from just a hang with the everlasting blue circle or Firefox on some occasions just exits during navigation.
To reproduce just go to http://maps.google.com and then switch to Earth mode. Zoom in as close as you can to the terrain and rotate around to view the horizon. Then move around till crash occurs.
Thanks
Darv

Let me know if you are unable to reproduce it. I still have a number of add-ons turned off but it was when I switched RightToClick on that the problems returned. I switched it on an off several times and every time it was on, Google Earth would just stop dead in it's tracks after a bit of navigating.
Thanks for the prompt reply.
Darv

Using Google Earth in Premiere Pro

I am trying to make a video for a competition using premiere pro and i want to put google earth in it. how do i do that?

function(){return A.apply(null,[this].concat($A(arguments)))}
the_wine_snob wrote:
You might need to use a video screen-cap program, like Camtasia, or CamStudio, to "record" your Google Earth movements. If so, then this ARTICLE might be of use to you, when it comes time to editing the footage. Also, Jeff Bellune has added some recent replies to other Camtasia threads, that tell more about using the TechSmith CODEC's.
Good luck, and let us know what you find the best,
Hunt
NO.You need Google Earth Pro version which can export video tour.Then import in Premiere.

Moving google earth bookmarks to the iphone

I've found a lot of places on google earth and put bookmarks (pins) into them.
How do I move these to my iphone?

i also was wondering if this could be done. i have a 4s running 5.0.1 that i have not upgraded to the new ios specifically because i have hundreds of bookmarks that i use in google maps for responding to emergency calls. i'm worried that if i upgrade i will lose all my hours of hard work inputing these bookmarks.

Working with WMV Google Earth Video

Howdy. I am attempting to integrate a Google Earth movie I recorded (WMV format) into my project and to put it lightly... it's not going well. Not only is it unable to render the timeline in the project window when it gets to the wmv footage (just gets stuck while audio continues), but it takes an insanely long time to render... six hours for a 30 second clip.
I took a shot at transcoding the clip using handbrake to mp4 but it crashed instantly when added to the premier timeline.
Sorry for the ametuerish question. As you can tell, I'm new at this. Any help is much appreciated.

Good news. AME is a good "converter" too, and is often overlooked. While it might not have the range of some dedicated conversion apps., when it can work with footage, it does a good job.
Thanks for reporting your success!
Good luck,
Hunt

Google Earth 7.1 - planet is spinning like crazy

Hi,
today when I opened Google Earth, the window came up, the overlays loaded and then the planet startet to spin like crazy. Everything I tried did not stop the spinning. It spins fast and constantly moves from north to west and back to north. It is unusable and I have no clue, where that is coming from. I googled the problem and could not really find any usable info, that's why I am posting it here now.
I have rebootet my machine, deleted the app and redownloaded it from Google to no avail. Still doing the same crazy thing. I just used it last week a few times and all was fine. I have not done any hardware changes or hook ups to my iMac since then. For all the years I use Google Earth, I have never had anything like that.
Any help would be appreciated.
Cheers
Peter

Check your USB devices.
I had the same problem and went through the whole delete and reinstall the application rigmarole, including preferences and everything that I could find, even in the hidden /User/Libray folder, and nothing worked until I Googled the problem and found the answer: that by unplugging my (rarely used) USB steering wheel, quitting Google Earth (easier said than done as it was very sluggish in responding) then restarting Google Earth, the application now works perfectly.
Relief!
So it seems that, in my case, a USB device was sending the earth into a spin.

Google earth will not run since downloading yosemite

google earth will not run since downloading yosemite

Do a backup.
Quit the application.
Go to Finder and select your user/home folder. With that Finder window as the front window, either select Finder/View/Show View options or go command - J. When the View options opens, check ’Show Library Folder’. That should make your user library folder visible in your user/home folder. Select Library. Then go to Preferences/com.apple.Safari.plist. Move the .plist to your desktop.
Restart, open the application and test. If it works okay, delete the plist from the desktop.
If the application is the same, return the .plist to where you got it from, overwriting the newer one.
Thanks to leonie for some information contained in this.

Update of Google Earth 4.3 Continually Crashes before opening...

I just update the Google Earth from 4.2 to 4.3....upon trying to open it, it crashes every time I attempt to do this...??
Any input from You?

HI Robert,
Try deleting the Google preference file: com.Google.GoogleEarthPlus.plist
/Users/YourName/Library/Preferences. Open the Preferences folder, locate that file, drag it to the Trash, empty the Trash and reboot.
Try to launch Google Earth now.. If that doesn't help try this:
If you can't log in to Google Earth, you'll need to delete these files from your directory folder. Please follow these steps to delete 'dbCache.dat' and 'dbCache.dat.index':
From the Finder, open the Home Directory icon labeled with your user ID.
Select Library > Caches > Google Earth.
Look for the 'dbCache.dat' files.
Ctrl-click on both the 'dbCache.dat' and 'dbCache.dat.index' files and select Move to Trash to delete these files.
These files will be regenerated the next time you log in to Google Earth.
I found the last tip here at Google Help: http://earth.google.com/support/bin/answer.py?hl=en&answer=77769
Hope something works!
Carolyn
Message was edited by: Carolyn Samit

I can't remove Google Earth

Google Earth was messed up and I was unable to use it so I deleted it from the applications folder and installed the latest version. It still didn't work so I used the included uninstaller. I noticed the old Google Earth was still in the Applications folder so i moved that to the trash. Later i noticed that Google earth was still in the lauchpad, and I cannot remove it from there. Please Help!

Right click on the Google Earth icon in the Applications folder (not on the dock), select 'Move to Trash'

Can you use Apple Maps to make guided tours and video recordings, similar to Google Earth Pro?

Hi Fellow Apple's
I am using Google Earth Pro to make tours, I'm using the build in Movie Maker function to export the tours as video clips. Now my question is if there's anyway to do the same in Maps.? Perhaps I'm not the only one looking for a feature like this?
Cheers,
Mick

No.

Google Earth Jerky Movement

Similar Messages

Maybe you are looking for