[Flightgear-devel] GUI update almost completed (Was: gui colors)
Melchior FRANZ wrote: The gui stuff is almost done. We have to wait for a plib bugfix, though. Here's the screenshot du jour: http://members.aon.at/mfranz/fgfs_gui6.jpg [265 kB] One can set /sim/gui/font to one of 7 built-in plib or 2 built-in fgfs pixmap fonts (e.g. VERA_13B, as in the screenshot), or to one of the texture fonts in $FG_ROOT/Fonts/ (e.g. helvetica_medium.txf). On gui-reinit the new font takes effect. Same with colors. The font in the screenshot is quite fat, but this looks better on dark backgrounds. There are thinner fonts available. And in the end we can have whatever font we like (as long as it's GPL compatible). Nice, just what I had in mind (except maybe for a different color scheme :-) ) Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [Flightgear-cvslogs] CVS: source/utils/GPSsmooth Makefile.am, 1.1,
Curtis L. Olson wrote: Update of /var/cvs/FlightGear-0.9/source/utils/GPSsmooth In directory baron:/tmp/cvs-serv15890 Modified Files: Makefile.am Log Message: Attempt to add -lwinmm for windows builds (untested.) I'd like to suggest another fix, as the IRIX build lacks -lm, which is apparently needed. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Nasal runtime error
This is just an update/reminder concerning Nasal errors on IRIX. This is the startup log of a current FG-Build. At the end I press 'v' once to change the view - which obviously doesn't work. Pressing F10 to enable the menu is still functional: SGTimeZoneContainer(): No such file or directory Audio initialization failed! Altitude = 49 Temp at alt (C) = 17 Temp sea level (C) = 17.0963 Altitude = 49 Dewpoint at alt (C) = 14 Dewpoint at sea level (C) = 14.0098 Reading xml electrical system model from /home/martin/CVS/FlightGear/data/Aircraft/pc7/pc7-electrical.xml Nasal runtime error: non-objects have no members at /home/martin/CVS/FlightGear/data/Nasal/view.nas, line 24 Nasal runtime error: non-objects have no members at /home/martin/CVS/FlightGear/data/Nasal/gui.nas, line 40 Nasal runtime error: non-objects have no members at /home/martin/CVS/FlightGear/data/Nasal/controls.nas, line 17 Nasal runtime error: non-objects have no members at /home/martin/CVS/FlightGear/data/Nasal/autopilot.nas, line 29 Nasal runtime error: non-objects have no members at /home/martin/CVS/FlightGear/data/Nasal/fuel.nas, line 17 Nasal runtime error: no such member at /input/keyboard/key[118]/binding, line 1 Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: GUI update almost completed
* Erik Hofman -- Wednesday 06 July 2005 10:46: Melchior FRANZ wrote: http://members.aon.at/mfranz/fgfs_gui6.jpg [265 kB] Nice, just what I had in mind (except maybe for a different color scheme :-) ) You'll be able to submit your creation in the big Default Style Contests, and maybe win the first prize: a Cheapo[TM] coffee machine! Hey, I'm just playing around with this stuff. This was to show white fonts on black, something that didn't work with the old texture fonts, and does still not work well with plib's built-in pixmap fonts, which are too thin. That's why I compiled two fgfs fonts in binary form. The first[1] is still thin but a little bigger than what plib offers, and the second[2] is bold enough for dark backgrounds. Could possibly be made a bit smaller (12 pt?). I thought first that we should keep the old style by default, and only make new ones optional. But maybe it's time for a change for v1.0.0? The light blue is really only suited for boys. We'd need a pink one anyway. ;-) m. [1] HELVETICA_14 -adobe-helvetica-medium-r-*-*-*-140-75-75-*-*-iso8859-1 [2] VERA_13B -*-bitstream vera sans-bold-r-*-*-*-130-75-75-*-*-iso8859-1 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: GUI update almost completed
Melchior FRANZ wrote: * Erik Hofman -- Wednesday 06 July 2005 10:46: Nice, just what I had in mind (except maybe for a different color scheme :-) ) You'll be able to submit your creation in the big Default Style Contests, and maybe win the first prize: a Cheapo[TM] coffee machine! Ah, a hammer and a blowtorch. Hey, I'm just playing around with this stuff. This was to show white fonts on black, something that didn't work with the old texture fonts, and does still not work well with plib's built-in pixmap fonts, which are too thin. That's why I compiled two fgfs fonts in binary form. The first[1] is still thin but a little bigger than what plib offers, and the second[2] is bold enough for dark backgrounds. Could possibly be made a bit smaller (12 pt?). Is there a reference anywhere which built-in fonts are available? BTW. I prefer 1px fonts myself: ... .. . .. .. .. .. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: GUI update almost completed
* Erik Hofman -- Wednesday 06 July 2005 13:35: Is there a reference anywhere which built-in fonts are available? freeglut/plib: FIXED_8x13, -misc-fixed-medium-r-normal--13-120-75-75-C-80-iso8859-1, FIXED_9x15, -misc-fixed-medium-r-normal--15-140-75-75-C-90-iso8859-1, HELVETICA_10, -adobe-helvetica-medium-r-normal--10-100-75-75-p-56-iso8859-1, HELVETICA_12, -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1, HELVETICA_18, -adobe-helvetica-medium-r-normal--18-180-75-75-p-98-iso8859-1, TIMES_10, -adobe-times-medium-r-normal--10-100-75-75-p-54-iso8859-1, TIMES_24, -adobe-times-medium-r-normal--24-240-75-75-p-124-iso8859-1 fgfs: HELVETICA_14, -adobe-helvetica-medium-r-*-*-*-140-75-75-*-*-iso8859-1, VERA_13B, -*-bitstream vera sans-bold-r-*-*-*-130-75-75-*-*-iso8859-1, The first group is already part of plib, so it doesn't use up more space. That's why I make the TIMES_ROMAN_24 font available, too, although it doesn't make that much sense. The second group are the fgfs specific fonts. They use some space, but have the benefit that they include all the fancy accented letters from iso8859. This should be good enough for 90% of all languages. (The plib fonts do only contain ASCII.) BTW. I prefer 1px fonts myself: ... .. . .. .. .. .. Hey, I have a Morse font for you! But currently, this is the smallest you can get: http://members.aon.at/mfranz/fgfs_gui7.jpg [19 kB] m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: GUI update almost completed
* Erik Hofman -- Wednesday 06 July 2005 13:35: Is there a reference anywhere which built-in fonts are available? Here's the source. The fonts are included here: $PLIB/src/fnt/fntBitmap.cxx I'll add a similar file $FGFS/src/GUI/fonts.cxx for the fgfs-specific fonts, if I get the OK. :-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] how do I access GetCoefficientValuesfromFGAerodynamics?
With the potential of exposing my C++ knowledge deficiency, I'll explain how far I got ;-) As mentioned in the last post, I have two variables I can access through the existing code I have. One variable is cur_fdm_state which is of type FGInterface. FGInterface is a parent class of JSBSim so accessing accessing the said 'get_fdmex()' method isn't easily done. I tried declaring a virtual method in FGInterface and defining it in JSBSim, but this only got ugly. The other variable is 'globals', but I haven't had much luck here either. With your knowledge of flightgear, do you know if it is possible to access methods from the JSBSim object via either of these variables? If so, could you provide suggestions? In FGJSBSim (the JSBSim object derived from FGInterface) there is a private member called Aerodynamics that points to the FGAerodynamics object of JSBSim. If you have your own cur_fdm_state object, however, the Aerodynamics object won't be accessible unless you change the Aerodynamics object to be protected instead of private, or unless you provide a getter such as GetAerodynamics() that returns the pointer to the Aerodynamics object. Then, you could simply do: my_string = cur_fdm_object-Aerodynamics-GetCoefficientStrings(delimiter); -or- my_string = cur_fdm_object-GetAerodynamics()-GetCoefficientStrings(delimiter); With the other option of using the XML file, could you give me an example of how the values would be retrieved? output name=localhost type=SOCKET port=1139 rate=10 coefficients ON /coefficients /output If you were to do the above (i.e. place it in your aircraft config file) you would have to have a listening socket somewhere ready to receive the data. In another shell window you could type: nc -l -p 1139 to listen to the data output by the sim. I've only done this with JSBSim standalone - not with FlightGear. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: GUI update almost completed
Melchior FRANZ wrote: * Erik Hofman -- Wednesday 06 July 2005 13:35: Is there a reference anywhere which built-in fonts are available? Here's the source. The fonts are included here: $PLIB/src/fnt/fntBitmap.cxx I'll add a similar file $FGFS/src/GUI/fonts.cxx for the fgfs-specific fonts, if I get the OK. :-) It would be nice if you would add all available fonts to the README.gui document. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/utils/GPSsmooth Makefile.am,
Erik Hofman wrote: Update of /var/cvs/FlightGear-0.9/FlightGear/utils/GPSsmooth In directory baron:/tmp/cvs-serv8203 Modified Files: Makefile.am Log Message: IRIX fixes. Thanks - works, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/utils/GPSsmooth Makefile.am,
Martin Spott wrote: Erik Hofman wrote: Update of /var/cvs/FlightGear-0.9/FlightGear/utils/GPSsmooth In directory baron:/tmp/cvs-serv8203 Modified Files: Makefile.am Log Message: IRIX fixes. Thanks - works, 'course it works, it's tested on IRIX :-) Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs]
Erik Hofman wrote: 'course it works, it's tested on IRIX :-) Do you actually _run_ FG on IRIX recently or do you just use it for testing the build ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs]
Martin Spott wrote: Do you actually _run_ FG on IRIX recently or do you just use it for testing the build ? I can't exactly call it 'running FlightGear' but I do start it once in a while. If we can track down the Nasal problem it actually runs quite well with 3d clouds (first time for big-endian systems like IRIX machines) and shadows. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: code optimisation
Hi, One comment and some documentation has indicted that FDM doesnt consume much CPU. I ask myself why? The modelling of a generalised rigid body with six degrees of freedom in a rotating frame of reference should max out anyones and everyones CPU! Of course any model is only as good as the approximations used so we apply symmetry to an aircraft (what happens if an engine drops off!) and various other restrictions. From my point of view I would rather devote spare CPU to the accuracy of the FDM. I notice that JSBSim uses a simple single step method for integration whereas LaRCSim uses a multi-step method. Spare CPU could be utilised in doing a multi-step predictor/corrector integration with variable step size especially for more esoteric aircraft types with high speeds and high altitudes and even near orbital capability in JSBSim. Anyone with any comments or advice or done anything similar? cheers Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: code optimisation
Jim Campbell wrote: The modelling of a generalised rigid body with six degrees of freedom in a rotating frame of reference should max out anyones and everyones CPU! People were doing that in real time with VAX 11/780's in 1981. :) Seriously, no: the FDM takes up comparatively little CPU. Of the two main ones, YASim is the slowest, because it breaks the fuselage down into a bunch of discrete units that need to be individually handled. The last time I looked at this YASim took up about 5-7% of so of the total CPU budget for the flight model I was looking at. I honestly forget when this was, on what computer, or what plane I was using. Sorry, but the 3D graphics are the lions share of the performance budget, and always will be. Of course any model is only as good as the approximations used so we apply symmetry to an aircraft (what happens if an engine drops off!) and various other restrictions. YASim is perfectly happy with asymmetric aircraft, FWIW. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: code optimisation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Campbell schrieb: Hi, One comment and some documentation has indicted that FDM doesnt consume much CPU. I ask myself why? The modelling of a generalised rigid body with six degrees of freedom in a rotating frame of reference should max out anyones and everyones CPU! Calculating the updating 6 DOF is a real simple task. It only takes a few operations. It can be far more challenging to calculate change in the 6 DOFs. This can be done cheaply on the basis of functions / lookup tables (like the FDMs we use). Or it can be done by solving navier stokes equations at each timestep. This would max out the CPUs for quite a while (especially when it comes to direct numerical simulation - there are even current supercomputers maxed out for simpler tasks than the flow around an air foil) Oh, btw, we are currently updating our 6 DOF much more often than the image gets redrawn... I notice that JSBSim uses a simple single step method for integration whereas LaRCSim uses a multi-step method. Spare CPU could be utilised in doing a multi-step predictor/corrector integration with variable step size especially for more esoteric aircraft types with high speeds and high altitudes and even near orbital capability in JSBSim. I doubt that changing the integration method will cause any performance problem. So you might try it. But making delta t smaller also helps, so that might give you more precision for the time spend tweaking the code. And as we've got an interactive application I guess that the absolute error in the integration doesn't bite us. Any turbulence in the real world will change the position more than precision errors will (assuming perfect FDM parameters) CU, Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCzC7xlhWtxOxWNFcRAstrAJ9F5IodbEMqjrRUQxvOjDAEJAXR/QCgnxCD yavFP/qrqy1BScpH8FFzOEE= =saYF -END PGP SIGNATURE- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] light works
hi all; I think its mentioned before few days ago by another developer about ksfo aproach lights. But no suggestion replied ...to play with the runways lights height where do we have to exactly look at??? terragear flightgear simgear..there are lots of different declerations in every package and I dont know where to start thanks _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Code Typo?
Hopefully I'm not too out of date with this since I'm looking at 0.9.8 code and am not an active CVS watcher. In file Main/viewer.cxx, in function MakeVIEW_OFFSET(...), on line ~118 where the third matrix is being made, there is the following line: tmp = t * axis2[1]; Since this is making the third matrix from the third angle, shouldn't this line be: tmp = t * axis3[1]; I'd assume this has been fixed on CVS but don't have the time to set it up and look, hopefully someone more involved in the dev process could check on this one real quick. Also is there an archive of this list or a bug database that allows searching through it? begin:vcard fn:Patrick Quirk n:Quirk;Patrick email;internet:[EMAIL PROTECTED] tel;work:919-962-1715 x-mozilla-html:FALSE version:2.1 end:vcard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Code Typo?
Citeren Patrick Quirk [EMAIL PROTECTED]: I'd assume this has been fixed on CVS but don't have the time to set it up and look, hopefully someone more involved in the dev process could check on this one real quick. Also is there an archive of this list or a bug database that allows searching through it? The archives can be searched at the bottom of this page: http://www.flightgear.org/mail.html. Greets, Steven ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Code Typo?
On Wednesday 06 Jul 2005 20:50, Patrick Quirk wrote: In file Main/viewer.cxx, in function MakeVIEW_OFFSET(...), on line ~118 where the third matrix is being made, there is the following line: tmp = t * axis2[1]; It's still in there... You don't have to do a cvs checkout to view the current state of any file, by the way, there's an interactive browser at http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/FlightGear/?cvsroot=FlightGear-0.9 Cheers, AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Code Typo?
Ah, nifty tool that CVS browser, thanks :) So am I correct in thinking that's a typo? I haven't had time to change it and test it myself, thats for tomorrow, though I can't imagine too many bad things could happen (its amazing it works with that typo to begin with). AJ MacLeod (email lists) wrote: On Wednesday 06 Jul 2005 20:50, Patrick Quirk wrote: In file Main/viewer.cxx, in function MakeVIEW_OFFSET(...), on line ~118 where the third matrix is being made, there is the following line: tmp = t * axis2[1]; It's still in there... You don't have to do a cvs checkout to view the current state of any file, by the way, there's an interactive browser at http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/FlightGear/?cvsroot=FlightGear-0.9 Cheers, AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d begin:vcard fn:Patrick Quirk n:Quirk;Patrick email;internet:[EMAIL PROTECTED] tel;cell:919-260-9918 x-mozilla-html:FALSE version:2.1 end:vcard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
