When importing a temporal file series (e.g. foo_N.vtk), paraview currently only recognizes N as an integer sequence (for instance where N=001,002,003,..). If the time series is named after a time represented by a float (e.g. N=0.5,1.0,1.5,... where you can think of that numbers as being seconds) the file series is not recognized.
Since naming a file after it's simulation time seems to be a fairly common practice, it would be helpful to expand the naming patterns and allow for N to be a float and not only an integer.
Instead of using the center of the screen (camera view) as zoom center.
In some modeling software, when you are in transform mode (ie the transform filter) you can select a particular axis to translate/rotate about by pressing 'x', 'y', or 'z' before performing the operation. It is very hard to position an object in 3d without that ability. Maybe by clicking the "balls" at the end of the transform axes with different buttons you could specify that functionality.
It is often useful to check distance between parts of a 3D geometry you are viewing and processing. This could be achieved with a ruler tool That would give not only the distance magnitude between two points, but also x, y and z distances.
Right now the text boxes in the GUI can display numbers of pretty much any precision. Although in general this is a good thing, it get really annoying if the boxes are displaying numbers with too much precision to fit in the text box. For example, if you rotate the camera with the mouse and then go the the Adjust Camera dialog, all the text boxes under Camaera Positions have a crazy amount of precision that makes it impossible to really read the numbers and hard to edit them. This happens in many other places in the GUI such as in the 2D widgets associated with a 3D widget and numbers generated from data like the auto generated scale factor in the Glyph panel.
It would be nice if the user could still use the UI while the servers are working.
Since virtually all computers have at least 2, rather 4 or even more cores, it would be great to be able to utilize them.
While it is posible to export .x3d and . vrml in Paraview, it is only for static scenes. There should be an posibility for exporting time varianse geometry to open 3d animation formats.
It would be great to set the opacity by a certain data value or set an alpha blending respectively.
E.g. you have a 3D object with a discrete density distribution. The density is illustrated by color. Every density value was determined with a certain accuracy. Now it would be great to illustrate cells with good accuracy opaque and cells will fade more and more by increasing errors.
Support for NASTRAN output files f06 or/and op2.
It would be great if Paraview could directly output animations to the GIF format.
The standard release of Paraview can read binary double precision OpenFOAM cases. It would be very useful if it could read binary and ascii and single and double precision natively. If it could autodetect the format and precision when reading the data in, this would also be extremely useful.
would be great to have a keyboard shortcut for load state (it's as useful as a shortcut for open).
Stream lines often break with point locator (default) of stream tracer with unstructured vtu data. One solution is to choose cell locator instead of point locator. But "stream tracer with custom source", which includes all flexibility to choose source points, does not have these options to choose.
Today, SpacePilot is supported only if you build ParaView manually. My guess is that this excludes most users. It would be great if SpacePilot could be supported by default - or if that has drawbacks, then maybe as a plugin?
I find it a bit annoying that the "Output Messages" window pops up every time I do something in Paraview. I've dug around in menus and settings and there seems to be no obvious way of disabling it.
I would prefer it to stay closed when I press "close", or at least not have it always on top of the UI. Most of the time, things are working well and I don't need to see the information in this window. I just want to look at my data.
QSpiAccessible::accessibleEvent not handled: "6" obj: QMenu(0x3992b50) ""
QSpiAccessible::accessibleEvent not handled: "7" obj: QMenu(0x3992b50) ""
This is already being sent to stdout so it's hardly necessary to have a dedicated always on top pop-up window for it as well (I also wonder a bit why a user would be interested in this stuff in the first place). Granted, not all users run Paraview from the terminal, but still...some options would be nice here.
Laser scanning data are typically in xyzRGB format, where xyz are the coordinates and RGB are columns for the R, G, and B colours (values from 0...255 for each). The current support for only one colour field could be extended to define the colours through three different fields. In addition, laser scanning data, i.e. point clouds, may contain points up to billions, in which case long coordinates may hinder the calculation time needed for the visualisation. Therefore it is suggested to build an filter or process that only takes into account the changing parts of the coordinates.