Blank SOFA render output when built from source on Mac OS

[gavincangan]

Hi, I tried building SOFA from source on my Intel Mac and was able to successfully build it. When I run SOFA, I see the GUI but with a black screen where the rendering should be. Has anyone seen this before?

I don't see any errors, just this warning (see image 2)

I originally used Qt v6.3.0 and had this problem. Then I tried Qt v5.15.2 and recompiled it, but the problem persists

[alxbilger]

@gavincangan try enabling the CMake variable SOFA_GUI_QT_ENABLE_VSYNC to see what happens.

[gavincangan]

@fredroy When I run with the -g qt flag, I no longer run into a segfault but I see the blank render output, and now there are no warnings.

[gavincangan]

@alxbilger Sure, I will try the other branch now

[gavincangan]

@alxbilger I just tried your branch and I am able to run sofa now 😃 🥳

I see this warning, but otherwise, seems to work fine! I will continue to use this for the summer school stuff and let you know if I run into any issues.

[INFO]    [PluginManager] Loaded plugin: /Applications/sofa/from_src/sofa/build/movesurfaceformat/lib/libSofaMatrix.dylib
An OpenGL surfcace format was requested that is either not version 3.2 or higher or a not Core Profile.
Chromium on macOS will fall back to software rendering in this case.
Hardware acceleration and features such as WebGL will not be available.
The constructor with a QGLFormat is deprecated, use the regular contructor instead.

[gavincangan]

Oh and I am able to run with both options now: -g qt and -g qglviewer

[alxbilger]

Excellent! We will prepare a clean pull request so it is merged in the master branch soon. Thanks for the bug report

[alxbilger]

@gavincangan I remember you had a version of SOFA with a working rendering, probably binaries. Do you remember which version? It could help to compare the code/dependencies with the current version.

[gavincangan]

@alxbilger Yep, I currently have v21.12 and v22.06_beta_defrost2022 binaries working on my computer

[hugtalbot]

A priori this is solved by #3105 do you confirm @alxbilger @gavincangan ?

[gavincangan]

@hugtalbot Yep, that solved the issue for me :)

[hugtalbot]

Great thanks a lot for making this discussion @gavincangan and thank you so much for solving it @alxbilger @fredroy 👍

[alxbilger]

The fix is now in the master branch