Re: [Flightgear-devel] Change in failures.nas
Am 25.03.2012 00:46, schrieb Eugenio Mondini: I'd like to understand something that seems to affect only me. As you can see in the forum [0] after a recent fgdata update I couldn't use one plane because it checked against a property in failure-manager part of the tree, that was not appering for me. Once I understood more or less what was happening I reverted a part of the commit [1] only in the failures.nas file and it worked again. Oops, there was another change in my commit that wasn't supposed to be pushed. I somehow missed that. Try latest fgdata and see if it's back to normal now. The issue should have affected all aircraft using the failure module. Thanks for reporting. cheers, Thorsten -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Change in failures.nas
On Sunday 25 March 2012 05:20:03 ThorstenB wrote: Am 25.03.2012 00:46, schrieb Eugenio Mondini: I'd like to understand something that seems to affect only me. As you can see in the forum [0] after a recent fgdata update I couldn't use one plane because it checked against a property in failure-manager part of the tree, that was not appering for me. Once I understood more or less what was happening I reverted a part of the commit [1] only in the failures.nas file and it worked again. Oops, there was another change in my commit that wasn't supposed to be pushed. I somehow missed that. Try latest fgdata and see if it's back to normal now. The issue should have affected all aircraft using the failure module. Works perfect again, now. Sorry for the delay but I had network troubles. Thanks for your help. Thanks for reporting. cheers, Thorsten Thanks, Eugenio. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Change in failures.nas
Hi everyone. Thanks for the awesome sim you all make.
I'd like to understand something that seems to affect only me.
As you can see in the forum [0] after a recent fgdata update I couldn't use
one plane because it checked against a property in failure-manager part of the
tree, that was not appering for me. Once I understood more or less what was
happening I reverted a part of the commit [1] only in the failures.nas file
and it worked again.
This is what I reverted manually in my install:
--
diff --git a/Nasal/failures.nas b/Nasal/failures.nas
index ccf6f79..23cb738 100644
--- a/Nasal/failures.nas
+++ b/Nasal/failures.nas
@@ -177,12 +177,12 @@ var setAllMCBF = func(mcbf) {
}
}
-
# Initialization, called once Nasal and the FDM are loaded properly.
-_setlistener(/sim/signals/fdm-initialized, func {
+var fdm_init_listener = _setlistener(/sim/signals/fdm-initialized-once,
func {
+removelistener(fdm_init_listener); # uninstall, so we're only called once
srand();
-# Engines are added dynamically because there may be an arbritary number
+# Engines are added dynamically because there may be an arbitrary number
var i = 1;
foreach (var e; props.globals.getNode(/engines).getChildren(engine))
{
breakHash[e.getPath()] = { type: type.MTBF, failure: fail.ENGINE,
desc : Engine ~ i };
--
What could be the problem?
Thanks, Eugenio.
[0]
http://www.flightgear.org/forums/viewtopic.php?f=4t=13296p=153965#p153945
[1]
https://gitorious.org/fg/fgdata/commit/f1e4c6503643587a933e742fcfc15cb5af127802
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
