a 'appy new yrrr ta ya all ...
I am overjoyed my Yasim c172 took off with ease. I was surprised that so much 'leveling' was required. I have flown 152, 172 and 182, and none seemed so 'skitish' as I remember ... Just an observation - I now jump for Crtl+H to stabalize the heading as I gather feet ... great stuff ... thanks ya :-))) Have not had any success with JSBsim. :-( My engine RPM stays 'stuck' at ZERO, despite multiple Page-Ups, even multiple shift+1, space, or shift+~ space, it stays stuck at none!!! HELP? :-( I also had to add to joystick.xml a <js n="1"> <!-- same mappings as js 0 --> </js> to get my joystick to work. Maybe it is 'fiddling' with the c172's alerions giving me this hard time ... I have yet to adjust the 'dead' value to see if that help. Have not had time to try other sim's yet. If any one is interested I did some work with a msvc6 'windows' version of js_demo I call js_demow. It uses the PLIB js.h, with a minor modification to return the actual number of axes rather than 6 all the time. It should show the buttons and axes found, and paint a red dot when you touch a button, or a new value if you move an axes. It reads in a global (js) property tree from joystick.xml, and labels the button and axes assigned therein. I wanted to be able to either 'drag' and 'drop', of combo box assign, or re-assign a button or axes, and write the desired XML file, but it is always a question of time ... Concerning my current environment, I did a plib, simgear, flightgear and fgfsbase cvs update. Actually have been doing it almost each few days ... But in building each of plib, simgear, metakit and flightgear, I ensured "Debug-Mutithreaded DLL" was selected in Project Setting, Win32 Debug, C/C++ tab, Code Generation. This uses the MSVCRT.DLL for all of the system funtions. Note this is not always the currect default, and in the case of PLIB you must select and change each library individually, but it is not a big item. I remember someone mentioned there was a warning when building plib and a few of us quickly answered that this was a 'good' warning. But now you get an ERROR later in the SG/FG build of a 'missing' js.h. I preferred the 'warning', rather than this hard error, but its ok ... There were still some things to change in the FlightGear.dsw/dsp set, but it seems some of these do filter through ... somehow a js.lib got in there!!! Things like the fact plib uses an "_d" for debug, and simgear is in ..\simgear\debug have been mentioned before. They need to be changed in the am2dsp script to make them permanent ... Hope to get in more 'flying' time soon ... still to increase the RAM in this machine. At present FG 'jumps' forward after spending up to a few seconds with my HDD light almost constantly on ... Geoff. PS: Over Christmas I got given Fly! II, but it seems 'very sticky' in my system - like it takes 'seconds' to move the cursor ... Must visit their site and see if anything there helps ... _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel