I add a PROP in disk mode via the Python API and run ExecAnalysis("VSPAEROComputeGeometry"). If I do not add a WING first, I can access the actuator disk and set/read RotorRPM, RotorCT, RotorCP. If I add a WING before running compute-geometry, the disk becomes inaccessible: GetNumActuatorDisks() returns 0 and FindActuatorDisk(0) raises FindActuatorDisk::disk_index 0 out of range, so I cannot read or modify RPM/CT/CP after the analysis.
I attach a minimal reproducible Python script that toggles the add-wing / no-wing cases. Is this a known regression in 3.46.0, or is there a required analysis input I should set so the actuator disk remains accessible?
Thanks.
Steven