Sebastien Jourdain (Kitware)

This will be a naive example but in some way, that show the concept but in order to properly skip any render call on the server side more work will...

Here is the main [example](http://kitware.github.io/paraviewweb/examples/RemoteRenderer.html)

Yes the client can switch between them. You can try that with ParaView Visualizer since it is easy to run and toggle between those modes.

Hi @misterjoa, The summary provided at the top is still valid at the high level. The technology stack underneath has strengthen to be simpler. Unfortunately we don't have a good...

It is indeed strange that the `TimestepValues` is a single time value rather than a list... Do you have a small data file example that we could use to create...

I've reported the issue in ParaView [here](https://gitlab.kitware.com/paraview/paraview/-/issues/20418)

What do you mean by error notification?

I see those are the `console.error` output in the catch call of the client rpc. That one should be [here](https://github.com/Kitware/paraview-lite/blob/master/src/stores/time.js#L45)

So technically the pvrenderingserver is not mandatory and you can use a pre-built version of ParaView with OSMesa to do the work. Basically, you don't need to create a view...

You can not run only that part. Just use pvpython from a OSMesa build that you can get for linux [here](https://www.paraview.org/download/)