#2296 Compositor rendering freezes when enabeling anaglyph 3d

[merspieler]

When enabeling Anaglyph 3d, it renders a single frame and that's it.

Gui dialogs work just fine, as do all interactions. The frame time and fps counter do change as normal but the visible frame is never updated.

Turning 3d off, shows everything as if nothing had happened.

[merspieler]

well... after a fg restart it works... but the loading screen is anaglyph as well... and the rendering is more or less broken while it looked correct while it was frozen

[merspieler]

One thing to note is, that WITH anaglyph, the osgText works while WITHOUT it's invisible

[Fernando García Liñán]

Yeah, I don't know if this is fixable. Didn't know people still used anaglyph 3D, I'll have a look. Is there a way I can mark this as Accepted?

[Fernando García Liñán]

I currently don't have an easy way of testing whether this worked in Rembrandt or not. Can anyone confirm?

[James Turner]

I fear the set of people running Rembrandt, Anaglyph 3D and reading these tickets is ... {}

Anaglyph is one of those rather unmaintained features, we might want to mark it as inoperative temporarily and see if anyone is motivted to work on it.

However, I can also guess it's 'just' an osg::FrameStamp glitch stopping it, might be quick to fix: I just have not much clue how it's even supposed to work. (And I never run Rembrandt OR Analgyph myself)

[Fernando García Liñán]

I've never dealt with anaglyph 3D so no idea to be honest. It's probably not a osg::FrameStamp problem as OP reports that osgText works with anaglyph, which shouldn't happen if it's something not related to rendering. I could be (hopefully) wrong though.

[merspieler]

James, I then assume me == {}
:P

On 2020.2.1, the menu option for 3d is disabled.
I was unable to build 2018.3 so I couldn't checkt that...

[Fernando García Liñán]

This is now fixed on next.