I’d make sure ParaView is of version 5.9.0 (from here) and simply extracted somewhere under the home directory to avoid access problems, like ~/, to where you can then set the PVOV_INSTALL_PATH. I’m not sure why it’s trying to install to /usr/local though, or even completing without errors but crashing afterwards. Running the installer independently from the launcher can work, but the result won’t feed back into the launcher itself. Only by clicking the launcher icon on the top-right of the screen and pressing Exit, is the instance actually shut down. When you try to then run the launcher again from another terminal, it actually reopens the previous instance and the PVOV_INSTALL_PATH is likely not set. However, if you already had a Launcher instance running before, and closed it by clicking the cross in the gui, it is still running in the background. I have a couple of suggestions for what may be the cause of the issues you’re seeing:Īs you probably know, the PVOV_INSTALL_PATH export has to be in the same environment as the running launcher instance, generally by running something like PVOV_INSTALL_PATH="~/Downloads/ParaView-5.9.0-MPI-Linux-Python3.8-64bit" ~/Downloads/omniverse-launcher-linux.AppImage. Hi, thanks for trying the PV connector on Ubuntu. So I tried to run ParaViewOmniSetup.sh from terminal, and it installs and showsīut if I go to the launcher, the installation is not reflected. I could not install directly from Omniverse launcher, it keeps give me the following error even though I have exported the PVOV_INSTALL_PATH.Įrror occurred during installation of Kitware ParaView: Command failed: “/home/juntao/.local/share/ov/pkg/paraview-connector-100.0.0/ParaViewOmniSetup.sh” -iĮrror: PVOV_INSTALL_PATH not set! Aborting install… Hi,I’m trying to install paraview connector with ubuntu 20.04.
0 Comments
Leave a Reply. |