On Fri, 2007-02-09 at 00:25 +0000, leee wrote: > Just checked again, with current cvs osg/simgear/flightgear, and I still got > the same problems. As before, re-setting the A/P via the menu seems to kick > everything into life. There also seems to be a random element to this > problem - in half a dozeeen tests, most of the time it was the same > controllers that seemed not to be working but in two tests there seemed to be > a couple of additional ones that didn't want to play. > The power check I added to kap140.nas moves the call to initialize the autopilot (apInit) to inside the apPower loop. apPower is called by a setlistener that monitors power="/systems/electrical/outputs/autopilot to makes sure there is power to the autopilot before starting the power monitor apPower to prevent a "nil used in numeric context" nasal error.
So, those reporting this behavior, please look at the Log Window; after the description. There should be two lines: Initializing Nasal Electrical System power up If "power up" is not there, then apPower has not been called and apInit has not been called, and the state of the various locks is unknown. This would indicate a problem with the setlistener. If it is there, my changes are not causing this problem. -- Dave Perry <[EMAIL PROTECTED]> ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
