-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
still existing UserParm Update issue with 3.25.0 #201
Comments
Can you duplicate this issue using something other than a Wing and somewhat larger perturbations than .000001 ? I see three potential issues... The wing has a somewhat more complex update path than other components because of the way the wing sections combine to form the total -- and because one section's tip is the next section's root. These factors have been known to cause some problems with wing updating from things like advanced links and scripts. Next, there is a tolerance on Parm changes that OpenVSP ignores. If you make too small a change, OpenVSP will not trigger an update. Finally, there are potential issues related to User Parms and Advanced links. So, if you can try some more basic tests, we can hopefully isolate which factor (or combination of factors) is causing the problems you are seeing. |
I'm not entirely sure if this is a bug or just a limitation of Advanced Links. You have two Parms that are both inputs and output Advanced Links: input "rw_x" -> output "wing_rear_x" & input "rw_z" to output "rear_wing_z". When the output Parm "wing_rear_x" is set in the Advanced Link script, OpenVSP updates the input Parm "rw_x" before completing the script. This causes the Geom to fail to update in the GUI until another update is triggered. If you can, it's best to avoid using the same Parm as an input and output in Advanced Links. If you do need to do so, instead use the input Parm before it's associated output is set in the script. Everything should update correctly if you reorganize your script like this:
|
Hi guys,
thanks for fixing a lot of the update bugs.
I tried reproducing update bugs and found that one mentioned earlier (in #189) still exists:
and pressing enter -> The geometry updates somewhat
The wing tip moves forward slightly
The wing tip fore-aft movement issue seems to be unrelated to the Aspect Ratio change issue, as it does not only occur after file load. Each later change in AR_ratio requires 2 Updates of the parameter to work correctly. (Updates only occuring when the paramter actually changes, so something like 1.0 -> 1.000001 is required.
My first guess was some sort of iteration going on inside the Adv Link, with out link code relying on one of its outputs to work correctly. However, I can't find any issues there.
Can the Aspect Ratio setting or the fore-aft movement issue stem from the fact that we set a parameter directly that is not a fundamental parameter of the wing, but one that is calculated based on the basic wing parameters?
Cheers,
Julius
Originally posted by @RY3A1R in #189 (comment)
OpenVSP_Bug_Uservars.vsp3.txt
The text was updated successfully, but these errors were encountered: