Re: [osg-users] Procedural terrains in oder to dig it.

[Chris Hanson]

There's some ability in osgEarth to do this.

Can you clarify better what you mean? Your English grammar is a little hard
to parse into a single meaning.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] OpenSceneGraph-3.6.3 release candidate 1 tagged!

[Eric Sokolowsky]

I just tried my application with 3.6.3-rc1 and it seems to work fine.
Fedora 26 (Linux). I still would like to know if there's an easy way to
limit usage to one of my two screens set up with Xinerama, like what
happened by default in 3.4.

Eric

On Thu, Sep 6, 2018 at 11:27 AM Robert Osfield 
wrote:

> Hi Glenn,
>
> The changes look OK from a a first scan.  Could you generate a PR
> against OSG master or 3.6 and I'll do a full review.
>
> Cheers,
> Robert.
> On Thu, 6 Sep 2018 at 15:58, Glenn Waldron  wrote:
> >
> > Robert,
> >
> > I apologize for not proposing this sooner. I made a couple updates to
> the Font and Glyph classes to address some thread-safety problems, and then
> forgot about them until now :)
> >
> > Creating objects from different threads was causing some unprotected
> access and this cleans that up.
> >
> >
> https://github.com/pelicanmapping/OpenSceneGraph/commit/c8b5a925459aa624a1d779192d3b8b0d7c4fa767
> >
> > I made this change against the 3.6.x branch. It's a small patch, but if
> you need a proper PR let me know and I'll spend some time putting it
> together.
> >
> > Glenn Waldron
> >
> >
> > On Thu, Sep 6, 2018 at 7:38 AM Robert Osfield 
> wrote:
> >>
> >> Hi All,
> >>
> >> I have tagged the first release candidate for the upcoming 3.6.3 stable
> release:
> >>
> >>
> https://github.com/openscenegraph/OpenSceneGraph/tree/OpenSceneGraph-3.6.3-rc1
> >>
> >> To make sure that this stable release is a rock solid as we can make
> >> it I need the community to help out with build and runtime testing
> >> across all the build platforms that our users are working with. Any
> >> issues please post them to this thread and we can work together to
> >> resolve them.
> >>
> >> My goal for 3.6.3 is to make sure all reported issues have be resolved
> >> prior to tagging the final release.   I would love to be able to get
> >> 3.6.3 out by the end of next week, so prompt testing would be very
> >> much appreciated.
> >>
> >> Cheers,
> >> Robert.
> >> ___
> >> osg-users mailing list
> >> osg-users@lists.openscenegraph.org
> >>
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
> >
> > ___
> > osg-users mailing list
> > osg-users@lists.openscenegraph.org
> >
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] OSG and Xinerama

[Eric Sokolowsky]

I have been using OpenSceneGraph 3.4 with my application. Recently I tried
out OSG 3.6 and everything seems to work, with the following difference.
When I run my app with OSG 3.4 on a dual-monitor setup (Linux using
Xinerama) the application only uses one monitor, while the same application
using OSG 3.6 spreads the window across both monitors. I actually prefer my
application to just use one monitor. Once upon a time, Producer had these
text-based configuration files which I found to be very useful, but I'm not
sure if such configuration is possible any more. Is there a way to indicate
that only one monitor is to be used, using OSG API calls, environment
variables, or some sort of configuration file?

Eric
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org