Update/Fix for World Wind 1.4.0 Imagery and Terrain

[pangloss]

lol. ok

That is the correct MD5.

I searched for cdlpwin130aen at the start and all I could find were Canon links. I was somewhat puzzled. I used to have a Canon iP4200, it was a nice printer.

I was hoping someone might find terrain servers for Mars and the Moon, but nothing ever turned up.

Also, someone contacted me about the Place Finder not working. It never seemed to find anything I was trying to locate, so I never really used it. I don't know if it was broken before the update.

[James_In_Utah]

Were the placenames also being served by worldwind25? If so, that probably won't work any more. We could ship the placenames that came with V1.35.

[pangloss]

The 1.3.5 placenames are included in the update, as well as a set of vector boundaries. Those components seem to work fine. They are both installed locally.



This was about the PlaceFinder plugin (PlaceFinderLoader in the plugin stratup menu). It is the magnifying glass in the toolbar. It doesn't seem to be a stand-alone *.cs, so I guess it is coded somewhere.

[James_In_Utah]

In placeFinder.CS in the source, they seem to be sending a query to "http://s0.tileservice.worldwindcentral.org/querryGeoNames?=" appended by a name. When I try to ping that URL, it resolve to an IP address of 69.43.161.156, but I get no returns from it. I don't think it will work for any version.

[Genericly]

**UPDATE 2/16/12**

Well, I've finally found the time to finish up my testing and packaging of a new installer. Thanks to James_In_Utah, maleport, and pangloss for everything related to getting this WW version working again. This update has been given a v1.4.0.1 version designation primarily to differentiate it from the 1.4.0 release, plus I believe this is the version number in SVN. This installer is comprehensive and contains everything someone should need to get WW running on any machine.

New installer contents:
-Full World Wind 1.4.0.1
-All server updates
-All data additions
-DirectX and Managed DirectX checks, plus MDX redist installer
-.NET check and installation help

Fixes:
-Server Fix updates
-Data Fix updates
-Windows 64-bit OS support
-BmngLoader turned off by default
-PlaceFinder Global Placename Search working

Download link (temporary): http://www.mediafire.com/?v8xa871lbwlmcu3

Bugs:
-Managed DirectX installation sometimes hangs after it installs without any notice to the user. Solution: Open task manager, end task on the 'mdx-oct-2005.exe' process to allow the WW installer to continue.

PS: I know there was an issue of installing WW on 64bit systems into the 'Program Files (x86)' directory, however in my testing I haven't noticed any ill effect.

[Genericly]

Updated installer includes placename search fix and better uninstaller cleanup.

[James_In_Utah]

That sounds very impressive. I'm downloading it right now. Maybe pangloss can update the first post in this thread with a link to your new build.

[Genericly]

Running any non-official build WW1.4.0.1 release I see:
---worldwind.exe??

I don't understand this post. Where do you see this? More info on how you installed, your system, and where you see this message might help me determine if I can help.

Cheers!

[pangloss]

Once it is finalized, I can put it on my server along with the other two. Mediafire may be blocked for some.

Isn't the elusive alpha called 1.4.0.1? Does this include that code?

For some reason, I can't edit posts that are more than a few days old, although I used to be able to do this. Maybe an admin can look at my account settings. It was a lot easier when I could change pointers that were superseded or updated.

[Genericly]

Unless there's a major bug with the installer I think I'm done playing with the code/installer. I don't have the knowledge to finalize a new 1.4.1 release.

The alpha I played with couple years ago was 1.4.1a. In fact I used to have it installed alongside 1.4.0 until I replaced them both with your server fix installer. Since I'm not certain where the 1.4.1a code came from I cannot really be certain if it's included in the 'HEAD' code that I compiled (revision 4099). I'm sure someone else knows better than me.

I'm in the same boat regarding editing my old posts. It seems I cannot edit my old posts from even 3 days ago.

[James_In_Utah]

I did have a conflict with my V1.4.1Beta which also had a version of 1.4.0.1. I think that's the version of the beta in SVN, or maybe that's what I called it. Anyway, not sure how to resolve that so they both work.

[pangloss]

James_In_Utah: You can backup and restore the two files in:
%UserProfile%\Application Data\NASA\World Wind\1.4.0.1

World.xml
WorldWind.xml

This way you can switch between multiple independent WW installations in different locations.

If you need it, the registry key is at:
HKEY_CURRENT_USER\Software\NASA\World Wind

Most of the installers use this to find the WW location

These will vary, depending on the Windows version.

----------------------------------

Genericly: There seem to be quite a few essential things missing or modified. I'm trying to put together a list, so give me a bit of time.

[James_In_Utah]

Hi Pangloss,
I usually just rename the \1.4.0.1 directory when I want to try a new build with the same version number. I was just saying going forward, it would be better if the two builds had different versions. I think I will change my version number on my latest stuff to 1.4.1.0. We are running it on a closed LAN at work, so everything there continues to work fine.

[pangloss]

Yeah, is it a branch or a new species? I'll leave the taxonomy to others.

Missing Files:

\Plugins\FOTW\fotw.txt
\Plugins\FOTW\Textures\*.dds

from the Waving Flags Plugin. I was never a big fan if this, but since it seems to be coded into the program, it might as well work. I can send you fotw.txt, but I don't have the texture files.


More critically, most of the wpl files are missing in:

\Data\Earth\Placenames\*\*.wpl

These are required for the Placenames to display.

I can send you these, if they got lost. They seem to be present in the earlier installers.


000-0001.txt, 0000_0001.wpl, 0000_0002.wpl and 0000_0003.wpl in the
\Data\Earth\Placenames\ root can be deleted. These are orphans that I missed in my clean-up.



Bugs:

When some layers are turned on, all the other layers and their sub-components seem to turn themselves off. I see this in the Jupiter and Saturn Moons. I don't know if it happens elsewhere, too. Nor do I have a solution. It's a pretty big glitch, though.

Left: Jupiter default, after opening. Everything is turned on and off correctly.

Center: Clicked the "Jupiter's Moons" entry. Still OK.

Right: Clicked the "Europa" entry. All of the entries turned off by themselves.

[Genericly]

James: I don't know too much about the internal versioning of WW.Net but can look into it and see if this can be adjusted. I wouldn't know what to call this build: 1.4.0.2 maybe?

Pangloss: I don't know if you were talking to me but I'll certainly reply

Missing Files:

\Plugins\FOTW\fotw.txt
\Plugins\FOTW\Textures\*.dds

from the Waving Flags Plugin. I was never a big fan if this, but since it seems to be coded into the program, it might as well work. I can send you fotw.txt, but I don't have the texture files.

Agree, not a big fan but it should still work. I'll look into my files and see if I still have these to add back in.

Y
More critically, most of the wpl files are missing in:

\Data\Earth\Placenames\*\*.wpl

These are required for the Placenames to display.

I can send you these, if they got lost. They seem to be present in the earlier installers.


000-0001.txt, 0000_0001.wpl, 0000_0002.wpl and 0000_0003.wpl in the
\Data\Earth\Placenames\ root can be deleted. These are orphans that I missed in my clean-up.

I'm glad you pointed this out. I had been wondering why placenames had worked previously but not with the new installer. I didn't have a good explanation for this. I should have those WPL files since I had them working previously. I'll get those put back in as well.

Bugs:

When some layers are turned on, all the other layers and their sub-components seem to turn themselves off. I see this in the Jupiter and Saturn Moons. I don't know if it happens elsewhere, too. Nor do I have a solution. It's a pretty big glitch, though.

Left: Jupiter default, after opening. Everything is turned on and off correctly.

Center: Clicked the "Jupiter's Moons" entry. Still OK.

Right: Clicked the "Europa" entry. All of the entries turned off by themselves.

I definitely see what you mean and may have actually experienced this bug with the Landsat data (I can't remember exactly which dataset), but it was basically as you illustrated. My first instinct is that this is an XML config issue but my first instincts are usually wrong . I'll certainly look into it and see what I come up with.