Paraview 12 Connector crashes Paraview 12

Hi,

Is anyone able to get paraview 12 to work with OV?

I have been using Paraview with OV for a long time. I just built a new computer (Windows 11 Pro and 4090). I installed OV launcher 1.9.13. I have latest apps installed and created a localhost. Everything seems to work correctly, except Paraview 5.12 (201.0.1). When I open the localhost connection, I get a dlalog that says use the browser to login, but it automatically logs in.

I add an omniverse viewport with default settings. The viewport does not change and after a while Paraview closes. The Paraview Session is created with folders and a fullscreen.usd file.

I will try older versions of the connector and paraview.

The Paraview 11 connector works. I thought I had used Paraview 12 connector, but it appears to not be the case. Anyone able to use Paraview 12 connector with Paraview 12?

Just to clarify, are you saying that version 11, works fine with our version 11 connector, but you cannot get version 12 to work with our version 12 connector? You were able to download and install version 12 ok? It shows up in Paraview version 12, but then the Omniverse viewport window hangs, and then crashes Paraview 12?

Let me ask the connector team. Our apologies. For now, try to use version 11, with our version 11 connector.

Hi Brad, just a quick check before diving deeper: where are the Session folders currently written to with 5.12, localdisk or the nucleus server?

The lack of a nucleus login confirmation window in the browser is concerning and likely the reason things are going wrong, so this should be resolved first. Could you try to:

  • go to the Omniverse Launcher’s Nucleus tab
  • click settings (the triple horizontal line icon next to the local nucleus server header), which will open a browser window
  • then navigate to the connections tab
  • remove all entries there

This should reset your Nucleus connection tokens, which should cause the browser window to pop up again if you retry to connect from within ParaView 5.12.

If it’s still not working, we have to dive deeper, but I’m personally developing and testing on Windows 11, so I don’t expect any deep problems.