and it seems that indeed it saves the date in ordinary .txt format.
Regarding your second approach with “savesol”, you need to be more specific with your choice of “fespace” for “[Ux,Uy,P]”, what is “uu” (from which fespace) and what is Rd1 (integer or fe function) ? Here is also the reference for using “savesol” - Developers - I couldn’d really find the “readsol” in documentation (it says “Todo” in External libraries, I guess the documentation on this topic isn’t completed yet).
From Developers it appears that “order” in “savesol” has to be 0 or 1 (and no other) - are your finite element spaces all P1 or P0 ? This might be the first issue.
I assume “int Rd1=1”, i.e. “Rd1” is “order” in your code above. The code below works well for me (only one vector finite element space)
In case your “Rd1” is finite element function from scalar fespace (P1). In this case you have two different fespaces of order P1, one vector fespace and one scalar. The following code seems to work well for me:
uh[][k] vhx[][2k] vhx[][2k+1] ... for k = 0 : Uh.ndof
note, Vh.ndof = 2*Uh.ndof. Also, you might want to look into how dofs are numbered for vector fespaces.
As a general suggestion, its not a bad idea to create very coarse mesh and fespaces on it, and savesol in txt format and then you can personally investigate what is going on.
You can also check your options with vtk/vtu format (for visualizetion in Paraview) - External libraries. Documentation is very clear here.