NOTICE: osgEarth 3.1 release candidate branch

classic Classic list List threaded Threaded
6 messages Options
gwaldron gwaldron
Reply | Threaded
Open this post in threaded view
|

NOTICE: osgEarth 3.1 release candidate branch

Friends,

The RC branch for osgEarth version 3.1 is now available for testing:

  https://github.com/gwaldron/osgearth/tree/3.1

This is a minor release, with several bug fixes and features. You can read the draft release notes here:

  https://github.com/gwaldron/osgearth/blob/3.1/docs/source/releasenotes.rst

Thanks for testing, and thanks for your support!

- osgEarth team

Glenn Waldron / Pelican Mapping
remoe remoe
Reply | Threaded
Open this post in threaded view
|

Re: NOTICE: osgEarth 3.1 release candidate branch

Can't compile it with osgEarth 3.0 CMake configurations:

https://github.com/gwaldron/osgearth/issues/1602
Remo Eichenberger, Switzerland
Himbeertoni Himbeertoni
Reply | Threaded
Open this post in threaded view
|

Re: NOTICE: osgEarth 3.1 release candidate branch

In reply to this post by gwaldron
Thank you, great to see osgEarth still being in active development. It provides a great service to us.

Is there more documentation regarding the features specified in the Release Notes though? E.g. is there an example for "TerrainConstraintLayer"? And mentioning "Improved task cancelation support throughout". What exactly is a task? A tile fetch via the DatabasePager? And from the 3.0 Release Notes: What are CompositeLayers and what service do they provide?
gwaldron gwaldron
Reply | Threaded
Open this post in threaded view
|

Re: NOTICE: osgEarth 3.1 release candidate branch

Not yet.

A TerrainConstraintLayer points to feature data that can "cut into" the terrain, to form a rigdeline, coastline, or a cut-out for a custom inset model. See "constraints.earth" for examples.

Sometimes a background task (like loading tiles) begins, but then is no longer relevant for some reason (camera moved away, user quits the app) and the task needs to be cancelled. The support for that is better now in various ways.

CompositeLayer lets you group multiple like layers together and treat them as a single layer. See "composite_image.earth" for an example.

Hope this helps.
Glenn Waldron / Pelican Mapping
remoe remoe
Reply | Threaded
Open this post in threaded view
|

Re: NOTICE: osgEarth 3.1 release candidate branch

In reply to this post by gwaldron
Is it possible to support "on demand" rendering for rex engine in 3.1? :)
Remo Eichenberger, Switzerland
gwaldron gwaldron
Reply | Threaded
Open this post in threaded view
|

Re: NOTICE: osgEarth 3.1 release candidate branch

Sorry but no, there is too much involved to get it into this release.
Glenn Waldron / Pelican Mapping