Hi Enno, I think all of these things could be implemented, though I can imagine some of them may be difficult to work with in practice (for example, negative TE wedge angle and variable TE thickness). However, I could probably code them up and you could give it a go. No promises on when that will be done, though. I've been busy with other interests lately and Xoptfoil has been on the backburner for awhile. Sorry about that. I do have a version 2.0 in the works, which I'm sure will be finished eventually....
If they are small bumps like in the profile you posted, you will need to use the BUFF option to generate the grid instead of SMTH, because the smoothing procedure will not preserve them. Be aware that this will result in the number of grid points along the surface being equal to the number of points in the airfoil file, which in the case you posted was huge (2000+ or something). So you may need to do some manual adjustment of the input file to remove unneeded points. In general, though, it will be...
Bunching of farfield cells in O-type grids
Loading of saved settings data
NaN error when SMTH the profile
Have you looked at that profile? It's no wonder it doesn't work. It's got multiple loops and self-intersections. Construct2D is only meant for use with single profiles forming a loop. I've attached an image of your profile.
With the hyperbolic solver, there is the FUNI option that affects the farfield spacing. Unfortunately, it's not always possible to really improve the wake spacing with this parameter. However, if you switch to the elliptic solver, there is the FDST setting under SOPT. If you set this to a number greater than 1, it will reduce the make the resolution finer at the farfield in the front and back of the domain. There is also always the potential to use a C-grid instead of an O-grid to improve the wake...
With the hyperbolic solver, there is the FUNI option that affects the farfield spacing. Unfortunately, it's not always possible to really improve the wake spacing with this parameter. However, if you switch to the elliptic solver, there is the FDST setting under SOPT. If you set this to a number greater than 1, it will reduce the make the resolution finer at the farfield in the front and back of the domain.