search

OpenChemistry / tomviz

Cross platform, open source application for the processing, visualization, and analysis of 3D tomography data
https://tomviz.org/
BSD 3-Clause "New" or "Revised" License
324 stars 86 forks source link

GUI looking weird upon installation #2028

Open RealPolitiX opened 4 years ago

RealPolitiX commented 4 years ago

I recently installed tomviz (v1.8) on a new computer running Windows 10, but after starting the GUI, the screen looks like the following picture. Tomviz runs well on other computers which also run Windows 10, so I wonder if there's anything missing that I should install on the new computer. Note that when I installed tomviz using the msi, there was no message saying that I missed other dependencies (I have Anaconda distribution of Python 3 on the new computer). Thanks in advance.

Screenshot

I tried rebooting the computer, but the problem persists.

cryos commented 4 years ago

Tomviz is a completely self-contained installer, and doesn't require anything else to be installed. Are you using an Intel graphics card? There was a bug in the Intel driver, that I thought had been resolved. Other thoughts are that Anaconda can set environment variables aggressively sometimes (or I have seen it at least) causing things to leak that can cause breakage - if your PATH for example contains other Qt or Python libraries.

RealPolitiX commented 4 years ago

My graphics card is Intel HD 530, I've updated to the latest driver, but it didn't solve the problem. The only PATH variable related to Qt or Python is PyCharm, but deleting it didn't solve the problem either.

Interestingly, when I installed the v1.2.1 of tomviz, the screen display shows up fine! So the problem is only associated with later releases (probably less to do with my computer settings).

cryos commented 4 years ago

We have seen a number of issues with Windows machines using Intel embedded GPUs. Last I heard it was fixed by updating the driver, I think it is an interaction between Qt and the graphics card driver but it has been tough to pin down. The 1.2.1 release is old, and uses a much older Qt. Our next release will feature an updated Qt that could possibly help here too. I don't know what triggers it, and it only seems to happen on a few machines. Sorry I don't have more answers, it is possible there is something we are missing too. I don't have access to a machine where this happens to track it down further.

cryos commented 4 years ago

I added more notes in #2030 - that links to some ParaView bug reports that detail which Intel driver versions were affected. I don't have access to any machines with this issue, it would be great to confirm upgrading/downgrading your driver works (or switching to a dedicated card if your laptop has one).