In the case of the FDM this can be done by configuring the -fdm=null switch. The easiest thing to avoid such problems is to completely disable the corresponding subsystem. You can use the property tree browser to check if certain properties are tied or not, see the wiki for details. In a sense, you have to differentiate between input and output properties. This could for example be the FDM, which uses so called "tied properties" - basically, the properties tied by the FDM are not owned by the property tree, they are owned by the FDM and the property tree merely holds references/pointers to the FDM properties. That is why you need to use the provided interface to sort of "tell" the corresponding system to stop doing what it is doing so that you can apply changes.įor example, you can overwrite most properties using a custom protocol, however you have to ensure that the data you are trying to overwrite isn't being written to by any other subsystems or parts of FlightGear. You CAN modify most properties, but you need to use the interface that is provided - some properties are getting permanently recomputed, which would mean that changes to them would be invalidated immediately by some other subsystems, others are "tied" properties that cannot be directly written to.
PS: Obviously, we would appreciate it if you could help us maintaining/updating the relevant docs (like I said, I don't even use a joystick myself!), which is easy to do just by registering a wiki account and editing the articles there - please let us know if you need any help doing that. If you find a bug that can be reproduced, please use the issue tracker to report it: Please see the links I posted earlier to browse the devel list for related discussions, you only need to search the archives using a query like "udp native ctrls" or "udp joystick" or "native ctrls" or FGNetCtrls to find lots of relevant postings Linking several computers via the native/fdm/null-fdm setup is well-documented, and we've had plenty of related discussions. Specifics like the I/O subsystem are introduced in $FG_ROOT/Docs/README.IO. Thus, I would not play with any custom compiler directives unless you really understand them and are prepared to deal with them, if the alignment of the structure is wrong, I'd file a bug report and post the details.
Flightgear source code code#
37664.html (including source code snippets, see the whole discussion!)īTW: I don't know understand why you are changing the structure alignment at all ?įG is multi-platform software, and things like the I/O system have to work reliably on different computers, regardless of the compiler used. 34274.htmlįor detailed instructions, please see.
0 kommentar(er)
