I've had another try using an older version of OpenVSP (3.30.0) in case there was a version specific issue. The command window is still showing the same messages:
ERROR 7: Could not open History file: Unnamed_VSPGeom.history
File: D:\a\OpenVSP\OpenVSP\src\geom_core\VSPAEROMgr.cpp Line:2242
ERROR 7: Could not open Polar file: Unnamed_VSPGeom.polar
File: D:\a\OpenVSP\OpenVSP\src\geom_core\VSPAEROMgr.cpp Line:2422
ERROR 7: Could not open Load file: Unnamed_VSPGeom.lod
File: D:\a\OpenVSP\OpenVSP\src\geom_core\VSPAEROMgr.cpp Line:2665
Error: Aerothermal database (*.adb) file not found. Execute VSPAERO before running the CpSlicer
As it seems to be attempting to open files from my D: drive this is clearly not correct as it's directory is located on my C: drive. The D: drive is purely a backup on my machine and should not be accessed by any installed programme.
As previously noted, my machine is running Windows 11.
The in-app console window displays:
C:\Users\jonat\OneDrive\Desktop\OpenVSP-3.31.1-win64\vspaero.exe -omp 4 Unnamed_VSPGeom
VSPAERO v.6.4.5 --- Compiled on: Nov 11 2022 at 00:55:06 PST
Initializing OPENMP for 4 threads
NumberOfThreads_: 4
Mach: 0.000000
AoA: 0.000000
ReCref_: 10000000.000000
Sref = 13.500000
Cref = 1.370000
Bref = 11.500000
X_cg = 1.170000
Y_cg = 0.000000
Z_cg = 0.000000
Mach = 0.000000
AoA = 0.000000, 5.000000, 10.000000
Beta = 0.000000
Vinf = 100.000000
Vref = 100.000000
Rho = 0.002377
ReCref = 10000000.000000
ClMax = -1.000000
Clo2D = 0.000000
MaxTurningAngle = -1.000000
Symmetry = NO
FarDist = -1.000000
NumWakeNodes = 64
WakeIters = 3
NumberOfControlGroups = 0
NumberOfQuadTrees: 1
QuadTree(1): 2: 0.00000
NumNodes: 11159
MaxNumberOfGridLevels_: 24
NumTris: 22314
VSPGEOM defined NumKuttaNodes: 0
Found 1 VSPGEOM Surfaces
DumChar: # VSPGEOM Tag Key File
DumChar: Unnamed_VSPGeom.vspgeom
DumChar: 0
NumberOfVSPSurfaces: 0
DumChar:
DumChar: # tag#,geom#,surf#,gname,gid,ssname1,ssname2,...,ssid1,ssid2,...
NumberOfKuttaNodes after trimming: 41
NumberOfKuttaNodes: 41
NumberOfKuttaEdges: 38
Working on VortexSheet: 1
Found a starting wake sheet node...
VortexSheet: 1 finished... and 33 out of 41 kutta nodes are now allocated
Working on VortexSheet: 2
Found a starting wake sheet node...
VortexSheet: 2 finished... and 37 out of 41 kutta nodes are now allocated
Working on VortexSheet: 3
Found a starting wake sheet node...
VortexSheet: 3 finished... and 41 out of 41 kutta nodes are now allocated
Done
No results are produced. Is this fixable or a Windows 11 intractability?
Thanks for looking,
Jon