Hello Cory,
I checked the system path on my computer and I couldn't find anything
related to Qt. I even tried removing Matlab-related entries but it didn't
work either. Is there anything else that I could try?
Best,
Junxi
On Mon, May 14, 2018 at 10:50 AM Cory Quammen <cory.quam...@kitware.com>
wrote:
> On Fri, May 11, 2018 at 1:52 PM Zhu Junxi <markzhumi1...@gmail.com> wrote:
>
>> Hello Cory,
>>
>> I tried a bunch of different versions and found out that those with Qt5
>> does not work while those with Qt4 looks fine (i.e., v5.3 and above does
>> not work, the latest version that works is v5.2.0 with Qt4). It seems that
>> it has something to do with the Qt5. I am wondering if other users are
>> experiencing similar issues with Qt5?
>>
>
> Thanks for checking all the versions. We have run into some issues with
> Qt5, but I had thought we worked through most of them. This is the first
> we've encountered with completely transparent render windows and
> translucent UI, hence I was wondering if there was something unique on your
> system that modified the graphics environment.
>
>
>> As for add-ons, do you have a list of specific add-ons that you are
>> particularly suspicious of? My desktop has a bunch of software installed
>> but they are either work-related (e.g., Matlab) or seemingly harmless
>> (e.g., steam). BTW, I don't have Nahimic sound driver, which I saw other
>> people reporting messing up with Qt.
>>
>
> Unfortunately, I do not. We have steam installed on some systems that run
> ParaView just fine, so I would be surprised if that were the cause. You
> could always try removing steam and seeing if ParaView versions 5.2+ work,
> but that may be more than you want to do.
>
> You mentioned you have Matlab installed. I believe Matlab ships with Qt
> and it may have put its Qt location in your system PATH environment
> variable. Try removing (or modifying) your system PATH environment variable
> so that ParaView won't find Matlab's Qt instead of the Qt version ParaView
> ships with. Some folks have run into this problem in the past and modifying
> the PATH was the solution.
>
> Thanks,
> Cory
>
>
>>
>> Best,
>> Junxi
>>
>> On Thu, May 10, 2018 at 8:36 PM Cory Quammen <cory.quam...@kitware.com>
>> wrote:
>>
>>> On Thu, May 10, 2018 at 11:40 AM Zhu Junxi <markzhumi1...@gmail.com>
>>> wrote:
>>>
>>>> Hello Cory,
>>>>
>>>> Thank you for such a quick reply. I checked the OpenGL entries and it
>>>> is indeed using the NVIDIA video card. The OpenGL renderer is listed as
>>>> GeForce GTX1080/PCIe/SSE2. I search online and although people say my
>>>> i7-6700k processor has a built-in 530 graphics card, I do not see it in the
>>>> device manager somehow..
>>>>
>>>
>>> Okay, thanks for checking. We have encountered a number of issues with
>>> Intel graphics in the last year or so, but driver updates have mainly
>>> resolved most of them. That doesn't seem to be the concern here, though.
>>>
>>>
>>>> I have also tried the NVIDIA control panel. I did not find the High
>>>> performance NVIDIA processer you mentioned in the global settings, but I
>>>> did change the OpenGL renderer to GTX1080.
>>>>
>>>
>>> That should ensure you are using the GTX1080, but it looks like ParaView
>>> already was using it.
>>>
>>>
>>>> However, Paraview still cannot display correctly after applying the
>>>> changes (so does the 3D Slicer). I am wondering if you need any system logs
>>>> to diagnose this issue and I would be happy to provide them.
>>>>
>>>
>>> I can't think of any system logs that would help. But there are a couple
>>> things you could try.
>>>
>>> 1). Install an older version of ParaView and see if that works. If it
>>> does, that will help us narrow down possible reasons for the transparency
>>> you are using. ParaView 4.4 would be a good one to try:
>>> https://www.paraview.org/download/
>>>
>>> 2). Do you have any add-ons to Windows installed that modify the window
>>> system in some way? If so, try disabling or uninstalling those.
>>>
>>> Thanks, and sorry for the trouble.
>>>
>>> Cory
>>>
>>>
>>>> Best,
>>>> Junxi
>>>>
>>>> On Thu, May 10, 2018 at 11:22 AM Cory Quammen <cory.quam...@kitware.com>
>>>> wrote:
>>>>
>>>>> Jun
