Polygons are not rendered correctly

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Load the attached KML file into a Google Earth Plugin instance.
2. Rotate/tilt the globe and notice how the polygon starts moving and 
eventually disappears.

What is the expected output or behavior? What do you see instead?
Expected behaviour is that the polygon stays in its place, as is the case when 
using the application Google Earth 5.2.1.1329. Instead the polygon starts 
moving when the globe is being rotated or tilted. Depending on the size of the 
polygon and the position of the camera, the polygon is either drawn in the 
incorrect place or not visible anymore. 
When clicking the location of the polygon, the balloon with the description 
will pop-up.

Which plugin version are you using?
5.2.1.1329

Which browsers and operating systems are affected?
Tested on Windows 7 using Firefox 3.6/IE 8

Please provide any additional information (code snippets/links) below.
A KML document is attached containing one polygon. In addition a screenshot of 
Google Earth application as reference of the expected output and a number of 
screenshots of the Google Earth Plugin showing the rendering issue.

Original issue reported on code.google.com by arnoudgl...@gmail.com on 25 Jun 2010 at 2:20

Attachments:

• simple-polygon.kml
• ge-polygon.png
• gep-polygon-1.png
• gep-polygon-2.png
• gep-polygon-3.png

[GoogleCodeExporter]

Thanks for this detailed bug report.  However, I am unable to replicate the 
issue on 5.2.1.1329 on either Windows or Mac.  

Can you confirm whether you see the same thing in the downloadable Google Earth 
Client application?

And, if you can attach a KML with a LookAt such that the it defaults to a view 
that displays this issue, that would also be useful in case I am somehow just 
not moving/tilting in the appropriate way to duplicate.

Original comment by jli...@google.com on 25 Jun 2010 at 4:15

• Changed state: NeedsMoreInfo

[GoogleCodeExporter]

This issue is not reproducible in the downloadable client application, only in 
the plugin.

I've prepared three KML's with a LookAt that should enable you to reproduce it. 
However it is not depending on these specific LookAts, as simply moving the 
earth around here is enough to reproduce it. 
I also attached a screencast that demonstrates the effect.

Original comment by arnoudgl...@gmail.com on 28 Jun 2010 at 12:53

Attachments:

• polygon-1.kml
• polygon-2.kml
• polygon-3.kml
• screencast.avi

[GoogleCodeExporter]

Hi Folks,

I am able to produce this problem on version 5.2.1.1329. This issue will appear 
on some Graphic cards with the newest version of the plugin. Also, to resolve 
this problem, you will need an older version of the Google Earth plugin 
(5.2.0.5932). Basically, with the version upgrade from 5.2.0.5932 to 
5.2.1.1329, this issue will appear. We came across this issue when we upgrade 
the version on the computers from 5.2.0.5932 to 5.2.1.1329.

The following are three of the Graphic cards that this problem will appear on:-

# 1
-----

Name: Mobile Intel 965 Xpress Chipset Family
Chip Type: Mobile Intel 965 Xpress   
DAC Type: Internal
Approx. Total Memory: 358MB
Current Display Mode: 1280x800 (32bit) 59HZ
Monitor: Generic PN Monitor

Drivers
Main: igdumd32.dll
Version: 7.14.0010.1295
Date: 9/19/07

# 2
-----

Windows XP (5.1 Build 2600)
Name: Intel 82865 G Graphics Controller
Chip Type: Intel 82865 G Graphics Controller
DAC Type: Internal
Approx. Total Memory: 96MB
Current Display Mode: 1024x768 (32bit) 60HZ

Drivers
Main: ialmrnt5.dll
Version: 6.14.0010.4299
Date: 4/5/2005

# 3
------

Name: ATI RADEON XPRESS 200 Series
Chip type: ATI Radeon Xpress Series
DAC type: Internal DAC(400MHz)
Display Memory: 512.0 MB
Current Mode: 1280 x 1024 (32 bit) (75Hz)

Driver Name: ati2dvag.dll
Version: 6.14.0010.6727
Date: 6.14.0010.6727

Please feel free to write to obtain more information. Thanks.

Original comment by wdt...@gmail.com on 28 Jun 2010 at 9:14

[GoogleCodeExporter]

Thanks for the additional details!

Original comment by jli...@google.com on 29 Jun 2010 at 2:36

• Changed state: Confirmed
• Added labels: Internal-2802603

[GoogleCodeExporter]

I apologize for the typo. The ATI Radeon Xpress 200 Series driver date is 
9/29/2007

Original comment by wdt...@gmail.com on 29 Jun 2010 at 3:58

[GoogleCodeExporter]

Hi Folks,

Just more supplement. Attached is a screenshot pertaining to the polygon not 
rendering at on those Graphics cards with the newest plugin version (5.2.1.1329)

1) polygon_not_rendered_on_5_2_1.jpg - shows the polygon Not being rendered on 
the newest plugin version 5.2.1.1329

2) polygon_rendered_on_5_2_0.JPG - shows what it should look like. The polygon 
successfully rendered on older version of the plugin (5.2.0.5932)

3) transparent_red_polygon.kml - the source kml for the transparent red polygon

4) transparent_purple_polygon.kml - the source kml for the transparent purple 
polygon

5) color_triangles.kml - the source kml for the color triangles

Original comment by wdt...@gmail.com on 29 Jun 2010 at 5:00

Attachments:

• polygon_not_rendered_on_5_2_1.jpg
• polygon_rendered_on_5_2_0.JPG
• transparent_red_polygon.kml
• transparent_purple_polygon.kml
• color_triangles.kml

[GoogleCodeExporter]

Also,

For the benefit of those who have no choice but to work with one of those 
Graphics cards until this problem is resolved... I hope, Google doesn't mind... 
this is what we did to revert to an old version of the Plugin (5.2.0.5932) for 
FireFox.

1) Make a copy the files (except the geplugin.exe) from the computer with the 
older version of the plugin (i.e. 5.2.0.5932) at i.e. C:\Program 
Files\Google\Google Earth\plugin. Hopefully, you have another computer with the 
older version of the plugin....

2) Totally uninstall newest Google Earth Plugin (5.2.1.1329) and Google Earth 
Desktop by going to the control panel and then "Add or Remove Programs" 
(sometimes Google Earth Plugin may show up separately, remove that too) 

2) Go to: http://earth.google.com/support/bin/answer.py?hl=en&answer=168344. 
They will need to click the "+" next to Google Earth (free version) Direct 
Installer Links. 

3) Under v5.1 click the "Windows" link.  It will prompt you to download the 
install, so click "Save".

4) When the file is finished downloading, run it to install Google Earth 5.1.

5) Once this older version of  Google Earth 5.1. is installed, then overwrite 
the files at C:\Program Files\Google\Google Earth\plugin with the copied files.

6) Give the Google Earth plugin a try, the version should be an older version 
(5.2.0.5932) instead of 5.2.1.1329 (that's the problematic version).

Hope this helps. 

Original comment by wdt...@gmail.com on 29 Jun 2010 at 5:21

[GoogleCodeExporter]

More supplement. Polygon are not rending with the newest version of the Google 
Earth plugin 5.2.1.1329

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600)
System Manufacturer: Gateway
System Model: DX4820
Processor: Intel Core 2 Quad CPU Q8300 @ 2.5GHz (4 CPUs), ~2.5GHz
Memory 6144MB Ram
Dirext X Version: DirectX 11

Display Devices:
Card name: Intel® G45/G43 Express Chipset
Chip Type: Intel ® 4 Series Express Chipset Family
DAC Type: Internal
Approx. Total Memory: 1695 MB
Current Display Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor: Gateway FHX2300

Drivers:
Main Driver: igdumd64.dll,igd10umd64.dll
Version: 8.15.10.1749
Date: 7/13/2009 8:41:07 PM 
WHQL Logo’d: n/a
DDI Version: 10
Driver Model: WDDM 1.1

If I do the rollback (to plugin 5.2.0.5932 and Google Earth 5.1) for FireFox 
using the instruction above, the polygon will render.

Thanks.

Original comment by wdt...@gmail.com on 7 Jul 2010 at 9:42

[GoogleCodeExporter]

The issue of polygons not rendering properly with Google Earth plugin 
5.2.1.1329 may be due to an issue with DirectX for the graphics cards mentioned 
above.  Using the desktop version and changing the mode to DirectX caused 
strange polygon display issues, which were not apparent when viewing in OpenGL 
mode on the Desktop.  I have found one work around discussed at the following 
link.
http://groups.google.com/group/google-earth-browser-plugin/browse_thread/thread/
5d5c7b7c90450de2/ee45771ce4a4d6a2

You can force rendering with OpenGL by setting a value of '1' to a registry key 
located at 
HKEY_LOCAL_MACHINE\Software\Google\GoogleEarthPlugin\Render\RendererApi
or
HKEY_CURRENT_USER\Software\Google\GoogleEarthPlugin\Render\RendererApi.

This may help people with the graphics cards mentioned above to render the 
polygons effectively with the latest Google Earth Plugin Version 5.2.1.1329.  
Hopefully Google can use this information about it being a DirectX related 
problem to sort out this rendering issue.

Original comment by david.ma...@gmail.com on 7 Jul 2010 at 11:16

[GoogleCodeExporter]

Hi all,

I've been pointed to this thread from a thread I started a few weeks back...

http://www.google.com/support/forum/p/earth/thread?fid=3532aec2d411074800048a6ad
9933efb&hl=en

I am also having a problem with polygons, but this is using the desktop version 
of Google Earth (5.2.1.1329 (beta)), I haven't tried this in the browser 
plugin. Basically, when I produce a KML file with more than a few hundred 
polygons, just after I load the file into Google Earth it instantly quits, no 
error message or anything. I have tried this on several laptops, using both the 
free and pro versions of Google Earth (and using directX and OpenGL).

My current systems is...

System Information:
Time of this report: 7/8/2010, 00:37:35
   Operating System: Windows XP Professional x64 Edition (5.2, Build 3790) Service Pack 2 (3790.srv03_sp2_gdr.100216-1301)
           Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
       System Model: Precision M6300                 
               BIOS: Default System BIOS
          Processor: Intel(R) Pentium(R) III Xeon processor (2 CPUs), ~2.5GHz
             Memory: 4094MB RAM
          Page File: 1818MB used, 5894MB available
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.3790.3959 64bit Unicode

Display Devices:
        Card name: NVIDIA Quadro FX 3600M
     Manufacturer: NVIDIA
        Chip type: Quadro FX 3600M
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_061C&SUBSYS_019B1028&REV_A2
   Display Memory: 512.0 MB
     Current Mode: 1920 x 1200 (32 bit) (60Hz)
          Monitor: Default Monitor
  Monitor Max Res:

Drivers:
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0011.7575 (English)
      DDI Version: 9 (or higher)

Hope you can help.

Original comment by cnew...@gmail.com on 7 Jul 2010 at 11:50

[GoogleCodeExporter]

Hey david.mancini, 

We tried your recommendations by forcing OpenGL through the registry key as 
described on Plugin version 5.2.1.1329. No luck though. The polygon of this 
attached KML does not show up.

Original comment by wdt...@gmail.com on 8 Jul 2010 at 6:15

Attachments:

• demo.kml

[GoogleCodeExporter]

Issue 488 has been merged into this issue.

Original comment by jli...@google.com on 8 Jul 2010 at 6:30

[GoogleCodeExporter]

I've tried the demo.kml attached on a machine with an Intel® G45/G43 Express 
Chipset graphics card, and I've attached a screenshot of the file loaded in the 
latest Google Earth Plugin version 5.2.1.1329 after forcing OpenGL through the 
registry.

As mentioned in the link I posted above, after making the registry change, 
you'll need to kill all geplugin.exe 
processes: 
    Start -> Run -> taskkill /f /im geplugin.exe 
or else the registry changes won't stick. 
WARNING: only use this for testing, as this may change in the future.
I hope this helps clarify a few things.

Original comment by david.ma...@gmail.com on 8 Jul 2010 at 11:06

Attachments:

• demo_kml.jpg

[GoogleCodeExporter]

I am also having this problem.

The machine is running Windows 7 64 and has 2 display adapters with the 
following title: "ATI FirePro V5700 (FireGL)"

Driver Provider: ATI Technologies Inc.
Driver Date: 10/31/2009
Driver Version: 8.663.3.0

Original comment by tucker...@gmail.com on 15 Jul 2010 at 8:45

[GoogleCodeExporter]

I've this problem also.

I'm working on a web page with GE plugin. 
we encounter "floating/moving polygon" problem with some onboard intel display 
adapter with XP. tune down the directX acceleration setting 2 or 3 knob within 
display setting solve that problem.

now with the new GE plugin,we encounter the problem above. I can't make the 
plugin to render polygon within the KML. but the main program render everything 
correctly.
I try to tune the acceleration setting or reinstall display driver or reinstall 
DirectX or GE plugin. but no luck.

Hope google can release fixed version or patch.

My system config is:
ATI R9550 AGP.
Driver version. 8.593.100.0 (10/2/2010)

Goodluck to all of us.

Original comment by petrecy...@gmail.com on 19 Jul 2010 at 8:54

[GoogleCodeExporter]

Hey tuckerpmt and petrecycle folks,

Could you please do Google a favor by doing the following steps:-

1) On your Windows. Go to "Start".
2) Select "Run"
3) Type "dxdiag" on the text field at "Open:". Click "Yes" if a dialog box 
appears asking for permission
4) A "DirectX Diagnostic Tool" window appear
5) Click the "Save All Information..." button. A dialog window will appear 
asking where you should save the file. This will create a text log file.
6) Attach the text dxdiag log file here so Google can check it out. 

This will help Google dissect the problem better. 

Oh... don't forget to "Star" this issue, yah.

Thanks.

Original comment by wdt...@gmail.com on 19 Jul 2010 at 11:02

[GoogleCodeExporter]

Attached DxDiag diagnostic txt file as wdtinc suggested.

I ran those test b4 and after I reinstall directX and the display driver.
everything display ok before and after the update.
but still can't see the polygon render on the screen.

Thanks.

Original comment by petrecy...@gmail.com on 20 Jul 2010 at 3:16

Attachments:

• DxDiag.txt

[GoogleCodeExporter]

I updated my drivers yesterday to see if that would help.  So, the info I 
posted earlier will not match this new info.

Strange thing is I could not replicate the problem with the Polygons that I 
first noticed this problem with.  But, the demo.kml that is linked to by wdtinc 
still moves around when the zoom level changes.

Hope that helps...

Original comment by tucker...@gmail.com on 20 Jul 2010 at 1:26

Attachments:

• DxDiag.txt

[GoogleCodeExporter]

Hi Google Folks,

This computer has the polygons are not rending on the newest version of the 
Google Earth plugin 5.2.1.1329 (using the above demo.kml file). Attached is the 
"DxDiag.txt" file.

Original comment by wdt...@gmail.com on 26 Jul 2010 at 10:21

Attachments:

• DxDiag.txt

[GoogleCodeExporter]

Folks,

More supplement. Another machine that has the polygon not rendering issue after 
installing Google Earth plugin latest version 5.2.1.1329 (when using the above 
demo.kml file). 

The polygon not rendering issue for this machine can be resolved by forcing 
OpenGL using david.mancini's above solution by entering a value 1 for 
"RenderingApi" in the registry. 

Please find in the attachment the "DxDiag.txt" file of this machine.

Thanks.

Original comment by wdt...@gmail.com on 27 Jul 2010 at 5:17

Attachments:

• DxDiag.txt

[GoogleCodeExporter]

Hey Guys,

Another machine that has this issue. This machine has a video card with Mobile 
Intel(R) 945GM Express Chipset Family. 

Fortunately for this machine, the issue can be resolved by forcing OpenGL using 
david.mancini's above solution with the registry. 

Please find in the attachment the "DxDiag.txt" file of this machine.

Thanks.

Original comment by wdt...@gmail.com on 28 Jul 2010 at 6:31

Attachments:

• DxDiag.txt

[GoogleCodeExporter]

Folks,

This will relate to tuckerpmt and arnoudgl...@gmail.com's issue of the polygon 
(shadow like) moving around with the zoom level changing on the latest version 
of Google Earth plugin 5.2.1.1329. The 'shadowy' polygon remains even after 
opening another web page with Google Earth Plugin.

demo_kml.PNG - the polygon from the above demo.kml
shadow_polygon.PNG - the same polygon moves when changing zoom levels

This machine has a video card with Intel(R) HD Graphics (Core i3). The problem 
does NOT get resolved with david.mancini's above solution with the registry 
(yes... I tried the taskkill command that returns the message saying "No 
geplugin.exe" process). In this case, no luck.

The machine's OS is Windows 7. This polygon issue appears on both Firefox and 
Internet Explorer browsers.

Please find the DxDiag.txt file and also the screenshots.

Thanks.

Original comment by wdt...@gmail.com on 30 Jul 2010 at 8:17

Attachments:

• demo_kml.PNG
• shadow_polygon.PNG
• DxDiag.txt

[GoogleCodeExporter]

Another machine!

Original comment by mtut...@gmail.com on 30 Jul 2010 at 8:23

Attachments:

• DxDiag.txt

[GoogleCodeExporter]

Hi,

I am having the same problem with polygons no longer rendering or rendering as 
large coloured squares. I am using Google Earth Pro Client 5.2.1.1329 (beta) 
and experience the same problems in the plug-in. This problem has rendered all 
polygon data I generate unusable unfortunately.

I have one of the graphics cards affected. 

Does anyone know when a fix or an updated version of GE will be launched? I 
have attached my DxDiag.txt file to help Google unpick the issue.

Original comment by wateraid...@gmail.com on 4 Aug 2010 at 11:08

Attachments:

• DxDiag.txt

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hello,

I am experiencing the following problem as is described in posts above. When I 
view a KML file on my laptop it is working fine. When I view the same file on 
my pc (with the affected graphics card) I see the polygon as a large square 
shape and only at certain magnifications.

Is there any indication when this problem will be fixed?

Thanks

Original comment by joseph.p...@kcl.ac.uk on 4 Aug 2010 at 12:09

Attachments:

• polygon-problem.PNG

[GoogleCodeExporter]

Hello Folks,

Please check out this discussion I started on the Google Earth Plug-in forum 
about version 5.2.1.1329 and this polygon rendering issue at...
http://groups.google.com/group/google-earth-browser-plugin/browse_thread/thread/
c17e4d07c8fb7607/56d432e12dc42626#56d432e12dc42626

Please chime in that "Version rollback, or option to install an earlier 
version" discussion topic if you have any suggestions, or if you like an idea.

Also, please continue to assist Google by reporting in any other affected video 
cards  by describing in detail what you are experiencing (images/video clips 
can be used to illustrate) and attaching the DxDiag.txt (hardware specification)

Thank you all for the assistance and feedback! 

Original comment by wdt...@gmail.com on 4 Aug 2010 at 3:41

[GoogleCodeExporter]

Hi all, 

We have made 5.2.1.1547 available on the developer channel which should go a 
long way towards solving this issue.  If you have been affected, please install 
this new release, which you can get from the download link at 
http://code.google.com/apis/earth/documentation/developer_channel.html 

Currently the windows version is available, and the mac version should  be 
available very shortly. 

Original comment by jli...@google.com on 5 Aug 2010 at 6:36

[GoogleCodeExporter]

All of the KML files in this thread work as expected on my machine with this 
new plugin.

:)

Original comment by tucker...@gmail.com on 5 Aug 2010 at 8:48

[GoogleCodeExporter]

The provided version 5.2.1.1547 works here as well!

Original comment by arnoudgl...@gmail.com on 6 Aug 2010 at 8:02

[GoogleCodeExporter]

All,

The above KML files worked as expected on the Intel(R) 4 Series Express Chipset 
Family with this new version (5.2.1.1547). The polygons rendered as expected.

More testing on other affected video cards. Will send in the results and 
feedback asap!

Thanks! 

Original comment by wdt...@gmail.com on 6 Aug 2010 at 10:14

[GoogleCodeExporter]

More feedbacks...

The above KML files worked as expected on NVIDIA GeForce FX 5500 with this new 
version (5.2.1.1547).

Thanks!

Original comment by wdt...@gmail.com on 9 Aug 2010 at 3:00

[GoogleCodeExporter]

Fixed in r5.2.1.1547

Original comment by jli...@google.com on 9 Aug 2010 at 5:47

• Changed state: Fixed