On 27.07.2011 22:31, Robert Osfield wrote:
Your report of problems when mixing OSG's built in analgyphic stereo
with shaders is the first one I've seen.  I've just tested osgvolume
with analyglyphic stereo and it works fine with svn/trunk and the
OSG-3.0 branch - this uses shaders, and J-S has tested with other
shader based example so I'll not look go chasing this further.  As far
as I'm aware there hasn't been any regressions in stereo support since
2.8.

I'm still really unsure what's triggering it. But I already had to dismiss my shader theory again. It also happens with shaders disabled. But your hint at a (custom) culling issue sounds like a possible cause - indeed it also affects the shape of some elements... Maybe Mathias already spotted something earlier, I wasn't aware of any FG-related OSG 3.0 issues he's been discussing with you. I'll ask him if his observations are related here. Otherwise, we'll indeed go for a binary search to identify the exact commit introducing the issue for us. Keeps the CPU busy for hours, but has already proved helpful earlier...

For most users OSG-3.x will
be pretty similar to OSG-2.8.x, and the reports of problems we've seen
since 3.0.0 are all relatively minor, certainly not to the extent that
FlightGear seems to be having.

And it also didn't seem too bad for us. The stereo issue really is the only major OSG-related problem reported so far.

Once we have a better idea of what might be causing the problem we
could look at fixes to FlightGear or OSG.  I'll be tagging the 3.0.1
maintenance release this Friday so if a problem is spotted before then
we'll be able to merge it.  If nothing comes before Friday then either
a workaround/fix to FlightGear will be required, or you have OSG fixes
come along in time for 3.0.2 maintenance release - I don't have a
shedule for this release - it'll be released if there are fixes to
justify it.

I'll see if we can narrow it down until then - but I don't really expect that before Friday. Admittedly, I was just hoping for the issue to be a general OSG problem, but since it (un)fortunately seems to be working for you :), we'll now need to start digging on our side now...

Thanks Robert (and J-S) so far!

cheers,
Thorsten
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to