Re: [Flightgear-devel] keepingup with OSG(was Who turned the sun off?)
-- From: ThorstenB bre...@gmail.com Sent: Saturday, May 07, 2011 10:40 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Who turned the sun off? On 07.05.2011 10:20, Alan Teeder wrote: Ever since the atmospheric scatter patches went in I have had black sky, instead of blue. If I turn on material shaders, then there is a small area of blue close to the horizon, but that is the best I an achieve. The attached is from my TSR2 cockpit with shaders off. Which OSG revision? Saw the same effect when I experimented with latest OSG trunk last week. Sky turned black when attempting to render fog. Since there were also other issues (text display and clouds not working) I reverted back to OSG 2.9.9. Not seeing any issues now. cheers, Thorsten Which begs some questions. How is FG going to progress if it is stuck in a time warp with an old version of its key graphics library? Are the FG code developers liasing with their OSG counterparts, especially in the area of backwards compatibility? Alan -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] keepingup with OSG(was Who turned the sun off?)
On 10.05.2011 10:36, Alan Teeder wrote: How is FG going to progress if it is stuck in a time warp with an old version of its key graphics library? Are the FG code developers liasing with their OSG counterparts, especially in the area of backwards compatibility? First of all, 2.9.x are OSG developer releases (unstable). The stable OSG release was 2.8.3 for a long time - now there's 2.8.4 (since April). I'm not aware of major issues concerning stable OSG. We're checking compile-compatibility against OSG trunk regularly (automatic Hudson build). When necessary, we're adapting to OSG changes - though that will take a few weeks. Sometimes bugs are also introduced on the OSG-side - like http://code.google.com/p/flightgear-bugs/issues/detail?id=268 Incidentally, I have just invested a lot of time this weekend, tracing the specific OSG commit causing the problem and debugging it. The problem is now identified (OSG forgot to update one of their font plugins) and thankfully the OSG maintainer is now looking into this. There's also a temporary patch in our tracker. If the black sky issue persists for some time (i.e. OSG isn't fixing the issue themselves - which they often do, since most bugs aren't FlightGear-specific and there are a lot of active OSG devs/testers), then someone of us will also need to look into this. So, we're not stuck in a time warp just because there are occasional OSG issues. But it's tiring to be a constant OSG beta-tester. Seems we have enough own issues to take care of. Anyone volunteering though is welcome to test OSG trunk regularly, check for new issues, trace conflicting changes and report problems - preferably on a level which can be reported to OSG directly. Indeed, I guess Tim would be happy for any help in maintaining the FG/OSG code. And remember: you're not getting any new features just by installing a fancy new OSG library. We'd also need someone to add new code to FG in order to take advantage of available OSG features. cheers, Thorsten -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] keepingup with OSG(was Who turned the sun off?)
-- From: ThorstenB bre...@gmail.com Sent: Tuesday, May 10, 2011 11:01 PM First of all, 2.9.x are OSG developer releases (unstable). The stable OSG release was 2.8.3 for a long time - now there's 2.8.4 (since April). I'm not aware of major issues concerning stable OSG. We're checking compile-compatibility against OSG trunk regularly (automatic Hudson build). When necessary, we're adapting to OSG changes - though that will take a few weeks. Sometimes bugs are also introduced on the OSG-side - like http://code.google.com/p/flightgear-bugs/issues/detail?id=268 Incidentally, I have just invested a lot of time this weekend, tracing the specific OSG commit causing the problem and debugging it. The problem is now identified (OSG forgot to update one of their font plugins) and thankfully the OSG maintainer is now looking into this. There's also a temporary patch in our tracker. If the black sky issue persists for some time (i.e. OSG isn't fixing the issue themselves - which they often do, since most bugs aren't FlightGear-specific and there are a lot of active OSG devs/testers), then someone of us will also need to look into this. So, we're not stuck in a time warp just because there are occasional OSG issues. But it's tiring to be a constant OSG beta-tester. Seems we have enough own issues to take care of. Anyone volunteering though is welcome to test OSG trunk regularly, check for new issues, trace conflicting changes and report problems - preferably on a level which can be reported to OSG directly. Indeed, I guess Tim would be happy for any help in maintaining the FG/OSG code. And remember: you're not getting any new features just by installing a fancy new OSG library. We'd also need someone to add new code to FG in order to take advantage of available OSG features. cheers, Thorsten Thanks for the response, which has allayed my fears. My posting this was because there have been several postings about problems with recent versions of OSG and I had not seen much progress on this forum. I don´t have the time. or expertise, to consider getting involved with the OSG group. I appreciate that with a project with FG, which in turn depends upon other projects such as OSG etc etc there will be problems such as this. My attitude as a would be aircraft developer is that keeping up with bleeding edge has the advantage of being more future-proof, but is bound to produce such distractions. Regards Alan -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
