> > > > What kind of problems with the xml? > Turns out to be operator error. Have two machines, both were running with cygwin for fg and opengc glass cockpit displays Well config control was a little sloppy, had a very, very stale base tar package that got untarred on the new linux machine
So, with the executable in /usr/local/bin and the base in /usr/local/FlightGear the command line fgfs --fg-root=/usr/local/FlightGear/ --aircraft=747-yasim --opengc=socket,o ut,36,192.168.2.255,udp brings up fg and outputs data to the displays. Nice. It was a struggle, but looks like I get about 10 more fps under linux with the nvidia board. seems like a too large a gain. will have to run a few more rigorous benchmark tests to see if the gain in performance is real. (Still not "unconfused" where the files should live and why the config used under cygwin fails under linux, but that's tomorrow's problem) Changed the display options in the .xml file to true for full screen and game mode but the xterm window frame is still present. Any thoughts on what to look for? Something in glut, XF86 config file, xinitrc, or fg compile options. I know there is a function in glut to call for a full screen, something like glutfullscreen(). Is that what FG is using? Toughest part was trying to remember all the things related to linux/xwindows. cygwin can make one a little lazy ;-) thanks to all of you for the help Regards John W. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
