Does anyone know anything about setting a constant wind speed from a certain direction via the property tree? I've been modifying the property tree via telnet (specifically /environment/wind-from-heading-deg and /environment/wind-speed-kt) although it seems to not work properly. They values of these properties either do not seem to change or are change to a number different from what I supplied it with.Any help? We just want a constant wind speed from a certain direction, and we would like to be able to set this up via the property tree.Thanks.

>Does anyone know anything about setting a constant wind speed>from a certain direction via the property tree? I've been>modifying the property tree via telnet (specifically>/environment/wind-from-heading-deg and>/environment/wind-speed-kt) although it seems to not work>properly. They values of these properties either do not seem>to change or are change to a number different from what I>supplied it with.>>Any help? We just want a constant wind speed from a certain>direction, and we would like to be able to set this up via the>property tree.>>Thanks.The weather system uses various layers of different settings for different altitudes, if you check out the weather dialog under $FG_ROOT/gui/dialogs/weather.xml you will see that you can easily write the corresponding values directly to the property tree using pathes such as /environment/config/aloft/entry in order to access the nodes for wind altitude/direction/speed etc..Likewise, you can play with these settings using the property browser.

Thanks, that worked out for us. Since you seem to know about the property tree pretty well can you tell us why these commands are coming back saying the object doesn't support item assignment when I'm changing them from within the property browser just fine?# self.fg['/sim/reset-on-crash'] = 'true'# self.fg['/sim/menubar/visibility'] = 'false'Thanks again.

>Thanks, that worked out for us. Since you seem to know about>the property tree pretty well can you tell us why these>commands are coming back saying the object doesn't support>item assignment when I'm changing them from within the>property browser just fine?>># self.fg['/sim/reset-on-crash'] = 'true'># self.fg['/sim/menubar/visibility'] = 'false'>>Thanks again. What programming language are you using, are you using Nasal?Usually, you would simply do something like:setprop("/sim/menubar/visibility",false);in order to set a property to an arbitrary value in Nasal.However, if you are using the telnet interface, you would access the property tree using the telnet commands:set /sim/menubar/visibility false

We are using python code, and the included FlightGear telnet interface class that comes in the /scripts/python directory. For some reason, setting these properties this way, an error is being returned saying that these can't be modified. Setting them via the FlightGear http server seems to work okay.Any thoughts?

>We are using python code, and the included FlightGear telnet>interface class that comes in the /scripts/python directory. >For some reason, setting these properties this way, an error>is being returned saying that these can't be modified. >Setting them via the FlightGear http server seems to work>okay.>>Any thoughts?Sorry, I haven't worked with the Python code for quite some time now and I am currently not able to verify your problem. So, I would recommend to first check out whether you are able to modify the corresponding properties via the in-built telnet interface.There's also the possibility that the corresponding sources may not be up to date, too. If you keep having problems, you might want to consider subscring to the FlightGear Devel mailing list, where more people are likely to be familiar with interfacing FG via Python.

I'm guessing this has something to do with these properties using string values. Maybe the python interface doesn't handle strings well?