FSLeyes UI showing but black screen for image

[meghtank]

Hello,

I downloaded FSLeyes through WSL2 on my Windows 11 computer. The setup was completely smooth and I had no problems. When I opened up FSLeyes, there was no image showing for the given file, and any other file I tried there was nothing showing up. I already tested the file to see if it was the problem, but the files worked on 3d-slicer and the format is nii.gz. I also am running this on XLaunch and that shouldn't be the problem since programs like xclock work. I tried everything from redownloading Ubuntu but nothing has fixed the issue.
Greatly appreciate it if anyone has a fix.
Thanks

[pauldmccarthy]

Hi @meghtank, are any error messages printed to the terminal?

Is there a particular reason you are using a separate X server? Have you tried using the GUI capabilities built into WSL?

[meghtank]

Hello Dr. McCarthy, There are no error messages printed on the terminal. I think I followed a tutorial that said to use a X server. I deactivated it and used the GUI capabilities that are on WSL and still no luck.

[pauldmccarthy]

Hi @meghtank, can you take a screenshot of the FSLeyes -> About dialog, and share it here?

There seems to be a a problem with certain Intel graphics cards. You could try forcing software-based graphics by calling FSLeyes like so:

LIBGL_ALWAYS_SOFTWARE=1 fsleyes

[meghtank]

Hello Dr. McCarthy,
I am using this processor: Intel(R) Core(TM) Ultra 9 185H 2.30 GHz
My GPU is an RTX 4050
Here is the screenshot:

[meghtank]

Hello Dr. McCarthy,
I tried forcing the software based graphics with your code, and it did work.
Thanks a lot for helping. I am a undergrad researcher at Johns Hopkins University in an MRI lab, so getting this software to work is a life saver.

[pauldmccarthy]

Good to hear that software-based rendering works. You can make this permanent by adding export LIBGL_ALWAYS_SOFTWARE=1 on a separate line at the bottom of your shell configuration file (the file in which the FSL configuration was saved - probably one of ~/.bash_profile or ~/.profile).

It sounds like this is an issue with certain Intel cards (see e.g. microsoft/wslg#482). The last comment in that issue suggests that you may be able to get hardware acceleration working by updating your system so that it has the latest available Intel driver. I'm not a Windows user, so I'm afraid I can't advise on how to go about doing that.