I think Im gonna restart the server and see if that helps, honsetly idk what is going on

I dont have cliffs on my surface

The restart didnt do anything. I have no idea what is goig on

Your snappy hex mesh is drunk or something bro

I've never seen anything like that 😅

your airfoil is like 1e-38m thick and you're having precision issues

setting nSmoothPatch back to 3 fixes it, the airfoil luckily is in a reasonable thickness area of around 50mm

There still some oddness going on but that helped with whatever is going on in the snapping

did you get back to larger tolerance? (smaller values should worsen snapping)

I am trying higher tolerance now aswell with feature snapping again, also going from nSolveIter 50 to 30

That got it back to a reasnoable shape, I guess I will just have to deal with it

the collapsing cells on the feature edge are right where those collapsing cells on the surface area anyway, or where that line intersects the wingtip

Okay I have managed to get a boundary layer over most of the surface by doing the add layer step 1 by 1 in reverse

starting with the biggest layer and slowly reconstructing and remishing going down to the first layer

its calculating, unless I have missed something that might just make this a bad simulation

y+ average of 6.5, not quite hit the mark on first layer height but... its not looking bad

6.5 is good enough for me and should still be in the range of correct values for the wall function

this... worked really well

I still have patches where the boundary layer didnt build and you can clearly see it effect the downstream stuff but it looks good

What did you do, nLayers 1 and keep adjusting the height?

exactly

it keeps the boundary layer from before and extrudes below it

meaning you have to start with the largest layer and work your way down

yes so that is the reverse of what snappy does, great. Now make an update for new version of openfoam where you can switch order setting, just kidding 🙂

I guess lol

Is there an easier way of handling the mesh btw? Specifically if I write the flags for knowing where the BL was actually created it creates time directories, can I reconstruct these to save them in the seriell setup temporary to then apply another BL step on it?

Or is there a smarter way

I'd probably save the layer fields individually, and then use a function object to sum them

Not the nicest way, but I think it'd work

If you need those fields for examining your mesh