Update/Fix for World Wind 1.4.0 Imagery and Terrain

[pangloss]

Genericly:Yes, I was talking to you, sorry if that was unclear.

The xml files are identical to the originals (date/size/CRC). They work correctly in 1.4.0. I have seen this with ScreenOverlay components, but never with the standard tags.

iirc, there were still bugs in the beta code. This may be one.

[James_In_Utah]

I'm pretty sure the version is set in \Worldwind\AssemblyInfo.cs. Just change:

[assembly: AssemblyVersion("1.4.0.1")]

to something else.

[danzig70]

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.

What happens if you change ShowOnlyOneLayer to false in the layer.xml file?

[Genericly]

What happens if you change ShowOnlyOneLayer to false in the layer.xml file?

That definitely resolves the issue of all child layers of all main-category children turning off. It allows more than one moon to be turned on at a time which may be undesirable, but that's a pretty small drawback considering the alternative.

[pangloss]

It wouldn't be a big deal for the few xml files included in the installer, but it breaks all the old addons, so it isn't such a minor thing. The point of this effort is for people to be able to continue using all that stuff.

[dgeoughea]

I'm a new user just trying to get WW working, and I run windows 7 64 bit. I ran in to the same issue describe in the post where it will not work after running the Data+Terrain fix. It seems like you guys a fix in the works, but is there any work around I can do in the mean time?

[Genericly]

I'm a new user just trying to get WW working, and I run windows 7 64 bit. I ran in to the same issue describe in the post where it will not work after running the Data+Terrain fix. It seems like you guys a fix in the works, but is there any work around I can do in the mean time?

Feel free to use this test release that should work on your system: http://forum.worldwindcentral.com/sh...3&postcount=35

It contains a few bugs: non-working visual placenames, wrong assembly version number, non-working flags of the world, extraneous files need removed, sub-layer unselection bug.

Fortunately, this test build is still very functional and works on 64-bit variants of Windows. I plan on packing up a new test build with most of these bugs fixed, I've just been swamped with work and house projects. Let me know if you run into any problems.

[dgeoughea]

I have installed the test release for the time being. Having never used WW before, I honestly won't notice if I run into any issues unless they are very obvious crashing-type issues.

Having said that, I don't know how Placenames should work, but I am getting very detailed place names in several locations in the US I am familiar with as well as less info, but still functional, in two arbitrary locations (1 in Europe, 1 in South Africa). I don't know if that is significant at all, but since I got the impression that they wouldn't work from the previous conversation, I thought I would mention it.

Also, the plug-in list immediately after installation seems significantly different than what I saw when I installed the 1.4 full version previously. I enabled a few that I hadn't seen before, like LayerManager, WhiteboardPlugin, and Virtual Earth Plugin, and I got some unexpected behavior. Virtual Earth gave me an error message and did not work. Whiteboard would scroll instead of drawing or letting me click inside the white board menu window in WW half of the time. Layer manager would scroll instead of toggling layers off and on some of the time. I have no idea if this is normal or a test build issue, so again, I thought I would mention it.

[Corrodias]

This temporary 1.4.0.1 build at least launches on my windows 7 x64 system, unlike the previous 1.4.0.

But i bring with me a bug report! Sort of. The "measure tool" only functions on worlds with a TerrainAccessor tag in their xml, like Earth and Moon, and doesn't work for others, like Jupiter and my custom world, even though they have an EquatorialRadius property in their World tag. I certainly don't have a terrain server for my custom world, so it'd be nice if i could keep measuring without one.

[pangloss]

Try creating a dummy TerrainAccessor entry. IIRC, I had to do this to get the spacecraft icons to work correctly for Venus (32-bit Windows, WW 1.4.0.1). It fixed the icon problem there, even though no terrain server exists. I don't know if it will work for you, the measure tool seems to work in x386 for planets without terrain.

No guaranties, but it is easy to try.

from Venus.xml:

<TerrainAccessor Name="topo">
        <TerrainTileService>
            <ServerUrl>http://worldwind25.arc.nasa.gov/venus/venus.aspx</ServerUrl>
            <DataSetName>venus</DataSetName>
            <LevelZeroTileSizeDegrees>20.0</LevelZeroTileSizeDegrees>
            <NumberLevels>8</NumberLevels>
            <SamplesPerTile>150</SamplesPerTile>
            <DataFormat>Int16</DataFormat>
            <FileExtension>bil</FileExtension>
            <CompressonType>7z</CompressonType>
        </TerrainTileService>
        <LatLonBoundingBox>
            <North>
                <Value>90.0</Value>
            </North>
            <South>
                <Value>-90.0</Value>
            </South>
            <West>
                <Value>-180.0</Value>
            </West>
            <East>
                <Value>180.0</Value>
            </East>
        </LatLonBoundingBox>
 </TerrainAccessor>

[oaktree_b]

Fix seems to work

Thanks for the info! Seems to work, although I find it strange NASA wouldn't put out an update (or at least a warning) that the servers had changed...

[mbeatstech]

Done!