fsbrain icon indicating copy to clipboard operation
fsbrain copied to clipboard

New fsbrain installation on M1 Mac does not show colorbar

Open utooley opened this issue 2 years ago • 3 comments

Describe the bug No colorbar appears when using vis.region.values.on.subject, and I get the error below.

FALLBACK (log once): Fallback to SW fragment processing (outputInfo.polygonModeMismatch)
FALLBACK (log once): Fallback to SW fragment processing, m_disable_code: 800000

To Reproduce Steps to reproduce the behavior: Use draw_colorbar=T with vis.region.values.on.subject. Without draw_colorbar=T, no error.

Expected behavior A clear and concise description of what you expected to happen.

Colorbar appearing, no error. Screenshots If applicable, add screenshots to help explain your problem.

Environment:

  • Operating System [e.g. MacOS10.13, or Ubuntu 20.04]: MacOS Monterey 12.2.1
  • R version (output of R --version in system shell): R version 4.1.2 (2021-11-01) -- "Bird Hippie"
  • fsbrain version (output of packageVersion('fsbrain') in R):‘ 0.5.3’

Additional context Add any other context about the problem here.

utooley avatar Mar 03 '22 18:03 utooley

Thanks for the detailed report! I have no M1 Mac, but I will see whether I can get access to one somehow.

I have the impression that these log messages are unrelated though, they seem to come from the M1 OpenGL driver and should only lead to worse performance (no hardware acceleration). I guess something in the rgl package (the renderer used by fsbrain) triggers them.

dfsp-spirit avatar Mar 04 '22 12:03 dfsp-spirit

Hi! Sorry for the delay, I think I forgot about this -- you're correct, the error messages are not reproducibly associated with the lack of colorbar, which is reliable while the error messages are not. However, I do still have this issue -- do you have any idea what is causing or a workaround? I've been using coloredmesh.plot.colorbar.separate but it is far less convenient.

utooley avatar Jun 19 '22 19:06 utooley