[boffin5]

Hi,
I have a new desktop PC, and am trying to run paraview to look at OpenFoam simulations.
The geometry shows up, but when I change the opacity to make it translucent, it all disappears.
I did some searching, and one lead said to look for 'depth peeling' in the Paraview.ini file. That file is attached here, but I don't see anything with those terms.
For my graphics card, I have a Radeon RX580. In the course of my searching, I saw remarks that Nvidia graphics processors were better for paraview than the AMD Radeon ones. I have a feeling that I should have gone with Nvidia.

Could this be related to the problem? Should I switch to Nvidia?
Help! This is a show stopper!

[boffin5]

Hi,

My showstopper problem is still plaguing me.
I ran the damBreak tutorial, and when I start Paraview, I get this message:

Created temporary 'damBreak.foam'
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
qt5ct: using qt5ct plugin
qt5ct: D-Bus global menu: no

It shows the simulation results, but when I change the opacity, all the geometry disappears. I need to see translucent bodies.

I am running OpenSUSE 15.4 on Vmware. My graphics card is an Nvidia GeForce GTX 1080.

Desparately need help!!

boffin5

[SadBoySquad]

I stumbled upon your thread by chance and figured I'd answer. Your problem is probably caused due to a combination of graphics libraries and graphics drivers. When I faced the same problem some time ago, I did not have time to delve deeper and find the exact cause.

Did you install ParaView via the SUSE repositories? If yes, then try downloading the ParaView binaries from their website and see if the problem persists.

When I faced this problem, it would happen only in the repository installation of ParaView. If you download the binaries I think everything will work as intended since, in contrast to the repository version, no already present libraries will be used to compile and install ParaView; it will be more "self contained" let's say. That solved the problem for me at least.

[boffin5]

Thanks SadBoySquad!


Regarding ParaView, and OpenFoam actually, I was embroiled in a search where I tried a number of different flavors and permutations of Linux emulators and distros.


I finally zeroed in on OpenSuse on VMware, but even with this, ParaView and OF did not work properly with the Gnome desktop, but when I switched to the KDE plasma desktop, it was like the parting of the waves; all the problems were pushed aside, and everything started working like a champ.


I can't explain why; my method was just try repeatedly until something works. Now, I'm having trouble with chtMultiRegion, but that's another story, and the 'try over and over' technique is not going to work. So with helpful people like yourself, I hope to get over the hump.

[SadBoySquad]

Well, if it works it works! I was also on Gnome when I faced this problem, so it probably has something to do with the Gnome qt5 libraries. I am guessing the solution lies somewhere along those lines.

I think I was on Pop_OS or Manjaro Gnome.

[boffin5]

More than a month ago, I was making good progress in OpenFoam, but then my computer crashed when running a script. I could not revive VMware, and lost a lot of work when it and the accompanying OpenFoam files had to be flushed. Then, I went to work reinstalling everything, but ran into the same old problem with ParaView images disappearing when the opacity was changed. After thrashing the problem to the point of insanity, finally I discovered that "enable 3D acceleration" has to be UNPICKED in the display settings. This, and editing the Nvidia control panel to specify high performance GPUs, finally brought me out of this mess.
Now, back to OpenFoam problems and challenges, but I like those!