Paraview 12 Connector crashes Paraview 12

Omniverse Deprecated Apps and Extensions Connectors
1

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.

2

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?

3

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.

4

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.

5

This is not an issue with the Paraview Connector. It is an issue with having just Paraview, Paraview Connector and a portable Kit application. The kit app built from a template does not install the Omniverse runtime stuff. Worked fine when I still have launcher installed. With launcher cleaned from the system and a portable kit app (it was installed from a package I created on another computer. There are files missing that the Paraview connector needs. If I install an app like Isaac Sim, I am certain the Paraview connector would work. I want this to be simple for others to try, so just unzip the packaged app and install the paraview connect. But with the missing dependencies the connector does some stuff but crashes when I load data.

brad

6

This is what I want to do.

  • build and package a Kit 109 composer application.
  • Transfer package to a computer off the internet
  • Unpack the “portable” application
  • Install Paraview 5.12 connector (201.0.2)
  • Open a new Viewport “Layout #2” and select “Omniverse Connector” and Click Create.
  • Load a Paraview example.
  • Open Kit 109 app. Open the USD generated from Paraview.

When I load the can.ex2 example it was crashing the app.

I just tried disk_out_ref.ex2 and that worked.

I tried the can.ex2 again and that worked.

I thought there were some missing dependencies or something that were missing because I didn’t have launcher, nucleus or an app like Isaac Sim installed. I will need some time to evaluate what is working and if I can reliably replicate the issue.

Brad Carvey

7

If I add the Paraview 5.12 connector plugin to Paraview 5.12 on a computer without any Omniverse apps, will it still save USD files to the local disk? Or do I need to install something for the connector to work? If so, what is the minimum that I need to install on a Windows computer to get the Paraview Connector to save USD to the local disk?

Brad Carvey

8

I did some investigation and Paraview Omniverse Connector appears to requires more than just the Paraview and the plugin.

The issue from the log file is “Failed to find local Omniverse installations Code 1”

Brad Carvey

Paraview Omniverse Connector Crash

This is a repeatable failure.

Computer information

Windows 11 Enterprise 24H2

NVIDIA 3090 driver 560.94

DirectX runtime version: 12.0

Detailed steps

Ran ParaViewOmniSetup.bat inside folder “paraview-connector-201.1.0.windows-x86_64.release”

Installed without errors.

Ran Paraview 5.12.1 on a Windows 11 computer.

Select disk_out_ref2.ex2 example (upper right) at startup.

Add second layout viewport.

“Create View” clicked “Omniverse Connector”

Omniverse Connector Settings dialog opens. Use defaults and click Create.

36 seconds later Paraview crashes. No errors are displayed.

Paraview Session was created with FullScene.usd and 5 empty folders.

I found a log in the Paraview\OmniverseConnector folder.

· ( 213.924s) [paraview ]pqOmniConnectLauncherCl:102 WARN| Failed to find local Omniverse installations. Code 1

· ( 255.345s) [paraview ]pqOmniConnectSettingsDi:267 INFO| Open view Settings saved

· ( 255.345s) [paraview ]pqOmniConnectSettingsDi:307 INFO| Omniverse Connector View Settings saved

· ( 255.374s) [paraview ]pqOmniConnectViewsSetti:372 INFO| Omniverse Connector View `OmniverseConnector1` created

· ( 255.374s) [paraview ]pqOmniConnectLogger.cxx:33 INFO| { connector_view_settings

· ( 255.374s) [paraview ]pqOmniConnectLogger.cxx:43 INFO| . OmniServer = localhost

· ( 255.374s) [paraview ]pqOmniConnectLogger.cxx:43 INFO| . OmniWorkingDirectory =

· ( 255.374s) [paraview ]pqOmniConnectLogger.cxx:43 INFO| . LocalOutputDirectory = D:/Paraview_Sessions

· ( 255.374s) [paraview ]pqOmniConnectLogger.cxx:51 INFO| . OutputLocal = true

· ( 255.374s) [paraview ]pqOmniConnectLogger.cxx:51 INFO| . CreateNewOmniSession = true

· ( 255.374s) [paraview ]pqOmniConnectLogger.cxx:51 INFO| . OutputBinary = true

· ( 255.374s) [paraview ]pqOmniConnectLogger.cxx:43 INFO| . UpAxis = Y

· ( 255.374s) [paraview ]pqOmniConnectLogger.cxx:51 INFO| . UsePointInstancer = true

· ( 255.375s) [paraview ]pqOmniConnectLogger.cxx:51 INFO| . UseStickLines = false

· ( 255.375s) [paraview ]pqOmniConnectLogger.cxx:51 INFO| . UseStickWireframe = true

· ( 255.375s) [paraview ]pqOmniConnectLogger.cxx:51 INFO| . UseMeshVolume = false

· ( 255.375s) [paraview ]pqOmniConnectLogger.cxx:51 INFO| . ShowOmniErrors = true

· ( 255.375s) [paraview ]pqOmniConnectLogger.cxx:51 INFO| . ShowOmniDebug = false

· ( 255.375s) [paraview ]pqOmniConnectLogger.cxx:47 INFO| . NucleusVerbosity = 0

· ( 255.375s) [paraview ]pqOmniConnectLogger.cxx:47 INFO| . No. Partitions = 1

· ( 255.375s) [paraview ]pqOmniConnectLogger.cxx:47 INFO| . Session No. = 5

· ( 255.375s) [paraview ]pqOmniConnectLogger.cxx:33 INFO| } 0.000 s: connector_view_settings

9

When I install a packaged kit 109 app on a computer, it is a portable application. It appears that with older versions of the Kit SDK there was a batch file “link_app.bat” that would make the Omniverse runtime available on the system. I have tried to add paths to make the files needed by the connector available. I have tried creating symbolic links to folders in the composer app in the C:\Users\brad\AppData\Local\ov\pkg. I think there is a simple fix to this issue, but I have not been able to get the Paraview connector to work.

10

I have been replying to my posts, so you may not of seen the updates.

The big issue is that no connectors will work with an Omniverse app created from the Kit templates. The apps are portable and don’t share the Omniverse runtime with the system. The paraview connector is looking for an installed Omniverse app and when it doesn’t find it, it tries for about 36 seconds and then Paraview crashes. See my sequence of posts to see what I have tried.

Brad Carvey

11

After lots of investigation, the Paraview 5.12 connector is not compatible with Kit 109 applications. The have different versions of some DLLs that make it crash when the USD converter is called. I was able to get the plugin to generate a working USD session using just a sphere. I had to copy tdd.dll and a few others from paraview to the custom kit 109 composer app. The dlls were not the same version between Paraview and Kit. This helped. But when I loaded a Paraview example disk_out_ref.ex2 Paraview crashed. This proved to me that the two are not compatible. I did make other changes, but syncing a few dlls got it to work with a sphere.

12

Hi everyone,
This is a VERY old thread from 2024. It is also in the depreciated section. If you want to start a new thread, please do so.

Secondly, as discussed, connectors are no longer being worked on and being phased out. All software is now doing NATIVE USD for import and export. Please just use native usd or fbx/stp as a fallback. Please do not attempt to use the connectors as they will no longer work.

For Paraview specifically we have open sourced a small github code sample that allows you to just export out as USD. Please use that until such time as ParaView implements their own.
GitHub - NVIDIA-Omniverse/ParaViewConnector: Plugin for Kitware ParaView adding Omniverse and USD support