In the Paraview GUI (5.11), there is an issue when the coordinate values are not the first, second and third variable. For example, if variable 1 is x, variable 2 is y, variable 3 is var and variable 4 is z, you get the option to load the DataArray "z", not "var". Even if you check the "z" variable, you still do not get "var" as point (or cell) variable. In python or the Python Shell, when you say GetActiveSource().DataArrayStatus = ["var"] and then update the pipeline, you get the desired variables, however. So it is just a GUI issue.
Maybe after reading the variables from the file, first the coordinate variables should be determined and all remaining variables should be presented to the user for inclusion in the DataArrayStatus?
An example ASCII tecplot file is attached: multizone-cubes.dat
When reading an ASCII Tecplot file into Paraview (5.11) where two (or more) zones have identical names (which is allowed), it is not possible to extract these zones to separate blocks using ExtractBlocks (which now uses block names, instead of indices like previously). If you use the ExtractBlock filter with one of the zones selected, it will outputs still both zones.
Suggestion: if zones have identical name, append the name with an index such that unique block names will be available?
A very simple example of the problem is attached: one Tecplot file and a python script to read it into Paraview illustrating the problem. It also contains the MergeBlocks and Connectivity filters for your convenience.
When writing data to vtm, it is possible to select which array to write, both in the gui and through python (ChooseArraysToWrite=1 in combination with e.g. CellDataArrays=[...]). It would be nice to also have this option when writing to CGNS. When writing multiple cgns files, this saves defining several PassArray filters.