What dx problem?
I can use GE with either Open GL or Direct X9 without any other problems.
Other programs I use report DX9 OK - only GE reports DirectX 8

I mean if you have no dx8, there must be a problem. It is weird. But not worth to trouble yourself.

I like some of the new features but you went and back tracked on the mapping.

I have a house under construction and in the older 4.1 version, it reflects the grading and lot construction work. I just installed the 4.2 Beta and it now goes back to pre clearing of the lot. I have double checked this against several other locations and they all reflect older dated mapping as opposed to the the earlier version I was running

What gives here ????? When are you going to put the updated mapping back.

The areas I am primarly talking about are Tampa Florida Pasco County.

I have server/network link combination like this example and the GE beta4 4.0.2xx clients suffer this same problem. If terrain is checked the <range> variable on any 4+ client increases by about 2000m every time the network link refreshes. GE 3 clients work as normal.
Bug? Something I am leaving out because this was written when only kml 2.0 was available?

Crispyjones,

Can you post a sample kml of your 2000m networklink problem? I haven't heard of this one before. (Start a new thread in KML Discussions about it).

I would love to help, but my server is strictly an intranet deal on our corporate LAN (which I have 0.0 admin rights on:). So, unfortunately, the network link won't do much in the outside world. Let me know what would help and I'll post it.

I'll try and describe in detail what goes on. A Perl script on a generic Debian based PC (my 'server') reads data from a modem (live copter position data) and writes this to a lat, long, speed, and a few other files. PHP page uses this position data as well as the client's ViewFormat values for heading, tilt, and range (to preserve client view). I uncommented a debug line that shows the LookAt values in a <snippet> tag and when terrain is checked (only in Beta4) the range variable increases by a few thousand meters every refresh. And the client's view goes up up up and up.

BTW I upgraded a Mac client from 3 to Beta4 and the same problem cropped up.

Discussion moved HERE at the request of PenguinOpus

I am using a linux box (Kanotix 2005 kernel 2.16.18-slh-up-2, KDE 3.5.5). When I first started using GE, it had some buggs but still worked. I updated in july and it freezes at the startup screen, I have updated using the latest sept update and it still does that. Is there a file or files (eg. conf or myplaces) that was installed with the earlier version that could be causing the prob, or could it be one of my linux packages that could be causing a conflict. Kanotix is very much pure debian sid.

Mac beta 4 version constantly quits, (Intel Macbook Pro, OS X 10.4.8) can't use it

My idea was to create an easy Flight Simulator.

Therefore I have created a NetworkLinkControl which requests periodically a service and has the FlyToView-on-Refresh set (GE 4.0.1693). The service returns a single placemark, with LookAt child nodes:
<LookAt>
<longitude>35.000</longitude>
<latitude>30.000</latitude>
<altitude>2000</altitude>
<range>500</range>
<tilt>45</tilt>
<heading>20</heading>
<altitudeMode>absolute</altitudeMode>
</LookAt>
The placemark is moving on every response (as it should), but the range, tilt and heading node parameters are ignored. The view is always in vertical direction to earth.
(Of course, I know, it is impossible to use these parameters at the same time if there are two placemarks to be shown. But wouldn't it be nice to have the functionality with only one placemark?)