LesterBoffo wrote in Thu May 14, 2015 4:55 pm:Neither here nor there but there is one 'paper-cut bug' in FG that I've also routinely encounter in other sims[...] The point of this ramble is such, there are gaps and omissions in both FDM's in FG at the base coding, either because there just wasn't enough time or knowledge to implement for the volunteers who coded the initial code.
I do not disagree with the notion that there's tons of hackish/problematic Nasal code all over the place trying to work around such limitations, and that this should ideally be addressed at some point - however, the whole point you made above may be really relevant/important to you, but it obviously isn't as relevant to many others, and it also doesn't match the criteria posted/requested to be used by bugman in his introductory posting, as per:
Subject: Looking for aircraft with 'paper cut' bugsbugman wrote:I'm not talking about fixing clunky FDMs or incomplete parts, but really basic maintenance - aircraft which start with tonnes of errors, and especially aircraft that cannot be started.
Thus, I would politely suggest not to hijack this thread by raising tons of contributor specific pet peeves, or this may quickly become really irrelevant.
If you are truly passionate about getting this fixed, I would suggest to team up with other contributors interested in this - such as e.g. the combat folks you mentioned briefly (Bomber comes to mind) - and maybe come up with an RFC on the wiki that you can raise on the devel/JSBSim list to ask for feedback.
It is true that this kind of stuff shouldn't be done in Nasal - these days, even using property rules would be a feasible workaround, without being specific to any particular FDM engine.
If you agree, we can split off your postings and move them to a dedicated thread in the FDM sub forum.