I'm current running into some weird behavior with vspaero in 3.45. I have experienced issues in all the newer versions but testing now the most recent 3.45.2.
Based on my testing, this seems to stem from intersections but not totally sure. Behavior is described below.
I have a relatively simple wing-body geometry, attached for reference. I have only tested in thin surface mode, as I need to ultimately run supersonic. All my testing has been done at Mach 0.3.
1. Running wing only, everything runs fine with both symmetry and full span.
2. Running with wing-body with default settings and full span, the solver NaNs and produces no output.
3. Running wing-body with default settings and XZ symmetry, it appears to run fine (maybe, I can't be sure). But that precludes me from using any of the other run types, like pitch stability for example to get neutral point.
4. Running wing-body with full span and cull orphans on (using its default settings), it runs but produces quite asymmetric results in the span loading with beta = 0.
5. Increasing the cull orphans parameters up from the default, say to 0.5, starts to improve the asymmetry but does not eliminate it.
My model is built as part of an automated upstream process (that writes a vspscript file) that runs fine in previous versions (e.g. 3.43). I've attached resulting vsp3 file.
Any ideas?
Brian