# General

## I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

### There are two ways to get more votes:

• When an admin closes an idea you've voted on, you'll get your votes back from that idea.
• You can remove your votes from an open idea you support.
• To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

1. ## Enable vector export of axis labels specified in MathText form in line chart views

Currently (as of version 4.1), when exporting line chart views in vector form, the mathtext axis labels get output in plain form such as $\gamma$ instead of the Greek gamma symbol. Mathtext apperaing elsewhere, such as legends, gets output correctly. Only the axes labels do not get output correctly. I have tested it with both "renedr text as paths" checked and unchecked and the error was not affected by it.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
2. ## Correct wireframe for quadratic elements in multi-core mode

Wireframe (or surface with wireframe) representation does not work with quadratic elements when in multi-core mode. The cause is that quadratic wireframe is not supported when geometry is shipped from server to client (which is implicitly the case for multi-core mode). See bug 10676, the bug that originally implemented correct quadratic wireframes, for more details on this unimplemented case.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
3. ## Add better NASTRAN support

Add better NASTRAN support for bulk file input

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
4. ## universal file

Many open-source CAE software can import/export .unv files (I-DEAS universal files).

I would like to have this option in ParaView

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
5. ## edge elements

Right now quantities are associated to nodes or elements, but in electromagnetics some quantities are naturally associated to faces (fluxes) or edges (magnetomotive forces) and special finite elements (nedelec / raviart-thomas) can be used to interpolate such quantities. Is support for such entities planned? If not how difficult would it be to implement it?

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
6. ## Create the ability to change the type of line (e.g. dashed for negative) when creating contour lines

I'm trying to create contour plots for fields that range from negative to positive values, but I'm unable to easily change the negative one to dashed lines so they can easily be identified.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
7. ## Add a time range selection on filters input, in particular, for the temporal statistics filter

A lot of simulations have a transient period, interesting but not relevant for statistics. In addition, it could be useful to not "download" these data: a kind of new time origin.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
8. ## SEG-Y seismic data reader (2D and 3D)

It would be useful to have a reader for SEG-Y seismic data, with the option to translate between big-endian and little-endian forms (UNIX to PC). This may be a complicated task since most data will be in two-way time (unless depth converted). However , this should not be a problem given that the freeware GMT software can read the data and convert to a useable format. Something to consider.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
9. ## Easier to use Plane Source

The plane source seems very awkward to use - specifying three corners of the plane. A more natural way to specify a plane is by the origin and normal vector. A radius would also be needed to specify how large the patch of the plane should be. Maybe a "Square Sphere Source" source could be added on top of the existing Sphere Source so people can use the existing one for "difficult" planes (non-rectangular) and the new one for "easy" planes (square).

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
10. ## Add a ability to select nearest point...

Would be a nice feature to select a point in the data not only with the rubber-band but with a modus "next point". This means, clicking on a surface an hold e.g. <cntl> the nearest point relative to the cursor is selected.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
11. ## Add the ability to use different fonts

Adding latex functionality would also be great, but impractical for some purposes. There are 3 fonts, serif, sans and mono. I am using Ubuntu 10.04 on this computer, and it gives me the options of arial, times and courier, the free ms fonts. The fonts, however, are not arial times and courier. I think they are some of the fonts from my distribution. I installed the ttf-mscorefonts package which installs arial, times etc. from the repositories, but the fonts remain the same.
I personally would like to choose my own font like Freesans or Nimbus, which both are Helvetica clones.…

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
12. ## Allow to write the meshes format that can be read ! (For instance .stl, .ply ...)

It is very frustrating to use various softwares in order to convert files from .vtk. Since Paraview includes lots of readers, why not writing the corresponding writers ?

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)

I see that it's been requested for quite a while! It'd be marvelous if you could just obtain the difference, union or intersection of two shapes with a click of a button... Just saying....

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
14. ## improve windows 10 compatibility

Windows 10 seems to have some incompatibilities with Paraview (v. 5.1.0), and sometimes crashes when opening .xdmf files. Also, when representing volumes, they do not look as good as in Ubuntu 14.04.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
15. ## Extend "Select Cells On" etc. to the missing boolean operations.

Currently the menu options: Select Cells On, Select Cells Through, Select Points On/Through ... offer the possibility to select subsets with the mouse. An already selected "selection" can be extended with the Ctrl key as modifier and the same commands. But it is not possible to remove from the selection with for example the Alt key as modifier (as is implemented in a lot of other programs). This would be a conventient extension of these 4 menu commands.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)

Support ESRI's shapefile, which is widely used for geospatial data. This is useful for a lot of CFD problems, which sometimes need to be visualized in a geographic environment.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
17. ## varying timestep size for .vtk format files

As suggested here,
http://www.paraview.org/pipermail/paraview/2011-May/021348.html
I propose supporting varying timestep for .vtk format files
via the vtk index.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
18. ## cell volume

It would be great to have a filter that directly computes cells volume and store it as a variable

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)

The tool to interpolate camera positions via the Animation view is very nice. But typing cam positions is very boring. In the dialogue you can use the current cam position. But I miss the possibility to load saved camera positions via the pvcc file.