Is it possible newest googleearth is broken on amd64/nvidia ? 
At least the 'flight control'. It's sucking 80% CPU1 + 50% CPU2 even minutes 
after the last user action. Nearly no keyboard or menu response, in this 
situation. 
It also doesn't update the 3D terrain details, then. It seems to relief when it 
doesn't 
need to render 3d polygons (for example, 'looking down') which hints at GL. 
Only sometimes after launch, it works fast and smooth as usual.
Anybody experiencing the same ?

It's a standard system: Nvidia GeForce7300GT 256M, AMD Athlon 64 X2 Dual Core 
Processor 3800+, 2G Ram. Debian unstable, kernel 2.6.22-rc5 from 
kernel-archive. 

Running make-googleearth-package --force, and dpkg -i --force-architecture,
installed Google Earth 4.1.7076.4458 (beta), Build Date May 6 2007, 
Build Time 11:10:05, Renderer OpenGL, Operating System Linux (2.6.22.0)

These errors:
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGCore.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGGfx.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGAttrs.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGDisplay.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGGui.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGSg.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGCollision.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGMath.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGUtils.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGOpt.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED ./libIGExportCommon.so' not 
recognized

... didn't prevent the installation. I should mention that with this kernel i 
had to build the 
nvidia module with m-a manually, and it works flawless (nvidia-settings, 
xscreensaver-gl.)

Honestly flight-control is the only thing that makes me use g.E.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to