Re: [Flightgear-devel] Who wants to port FG to a Beagle?
On Fri, 5 Sep 2008 08:38:01 -0700, GWMobile wrote in message [EMAIL PROTECTED]: On Fri, 5 Sep 2008 5:00 am, Holger Wirtz wrote: Hi all! on Linux Tag 2008 in Berlin/Germany I won a Beagle-Board from TI (see http://beagleboard.org/). This is a small embedded system but it is very powerful and seems to support OPENGL-embedded. Some small kind of disadvantage is that it has no onboard ethernet interface - but you can use one via usb. I thought it would be nice to try a port of FG to the beagleboard - but I just have no time for trying this. Is someone around who has some time and knowledge for this project? I will spend this board for someone who is interessted in this project. Please contact me by email. Regards, Holger Wow that is an amazingly 3d computer on a chip board for less than $150 ! Unbuntu and angstrom linux already ported. ..and Debian, you want the armel architecture and you must first set up the initial boot system in qemu on a pc or use a boot-ready image, or press both buttons and net boot it off your boot server. Hardware supported open GL 2.0 spec. ..any word on glxinfo and glxgears on these? I tried googling. It should support X up to HD, 1920x1080 or 1920x1200. Or is that an hype meaning 1366x768 or less? ..a wee benchmark idea to cut-n-paste: alias aiglxbenchmark='w \ ;cat /proc/version ;cat /proc/pci |grep VGA ||lspci |grep VGA \ |colrm 1 4 ;cat /proc/cpuinfo |egrep model name|MHz|bogomips \ ;xdpyinfo |egrep version:|dimensions|depth of ;glxinfo |egrep \ -A2 direct rendering|OpenGL vendor ;cat /var/log/Xorg.0.log \ |grep architecture ;cat /var/log/Xorg.0.log |grep flip ;glxgears \ -info sleep 51 ;killall glxgears ;w ;glxgears -fullscreen \ sleep 51 ;killall glxgears ;w ' , I get about 3295fps and 358fps full screen at [EMAIL PROTECTED], this buys me FG at 15 to 35fps in a [EMAIL PROTECTED] window with the screen shot server running, so, thank you guys for making FlightGear what it _is_. :o) Great 3d graphics and only 2 watts power consumption Usb, s video and hd tv 720 out. All standard usb peripherial support like bluetooth and keyboard s and mice and vr googles. The fully capable 3d gaming pc just got a LOT smaller and cheaper. (About 2in by 2inches ..the ref manual says 3.1 by 3 inches and 78.74 by 76.2mm, will still fit nicely in most r/c models, and now I know why I never got around to fix my 5.1 Volt flywheel charger blunder, it should feed 5.3V to a 4 cell flight pack, the other reason is I poured hot gun glue all over it and then shut the tin box I put it in 28 years ago, and the (b)eagle wants 4.8 thru 5.2 Volt juice. ;o) and no fan or even heat sink needed! ..any word on how much it heats up in vacuum, with only heat radiation to do cooling? See youtube for videos of this beagleboard in acton. Unbeleivable. Love to see a youtube vidoe of this tiny board running flightgear ..aye, and it can be done on-board too. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] f16 speedbrakes
On Fri, Sep 5, 2008 at 11:54 PM, Erik Hofman [EMAIL PROTECTED] wrote: I also see that (I'm only looking at the speedbrakes effects). Two things are unclear for me: 1. The values of alpha in f16.xml are exactly half those in NASA's TP1538 report. 2. The values of the coefficients are close to each other, but not exactly the same. For CmDsb I'm looking on TP1538 page 58 (PDF page 64) For CLDsb I'm looking on TP1538 page 65 (PDF page 71) Off course you need to transform the data from body axes to wind axes first.. Erik Sorry I've mixed the page numbers on TP1538 paper in my former message. Erik, 1. Transformation from body to wind axes would modify the coefficient values much more than the differences I see; moreover, I see difefrences even at alpha=0 (for CmDsb, -0.0036 in f16.xml instead of -0.0038 in TP1538). 2. The alpha values are still HALF those on TP1538. No matters what our conclusion will be on these issues, I really value the great job you've done in this model, making it a great source for learning JSBSim. Thanks. Fabian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LFPN Problem
On 5 Sep 2008, at 17:21, James Turner wrote: Yep, that's quite a likely source - thanks for the help, I'll work out from this. Got it. If someone could kindly apply the attached patch, that'll keep this from crashing, I believe. The fix is easy since FGAirport can now always provide an active runway - there's no need to guess at random, or rely on the tower having set one up. AIlocaltraffic.patch Description: Binary data Regards, James - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] FGPositioned update
I've been carrying on with my experiments with my FGPositioned idea, and I now have several of my original steps done: - Fix, NavRecord, Airport and Runway all inherit the base class - they all live on the heap, where previously Runway and Fix were stack based, and hence rather heavy to work with - since the liftetime is now (generally) long, I can use a persistent spatial index (currently not Matthias', but it's an easy, internal change) - I can query all of the above in a unified fashion, and add more types easily (Jon Stockhill has obstacle data I can add in) - I've written a bunch of test cases, all of which pass identically on the mainline and with my changes applied Lots of code quality cleanups fall out from the above, and there's plenty more I can pursue once the basic code is committed. So from my perspective it feels like a 'good' change, quite apart from my major motivation for it - providing the foundation for the NAV display and FMS features. I can continue working away privately, but I'd like to avoid drifting every further from the mainline, so unless someone can think of reason why it's an absolutely dreadful concept, I will start firing code at some luckless victim. I'm not going to submit a single diff because it's already rather large, and contains some other features I stupidly did on the same branch. Comments? Attached - current FGPositioned header. I'm still undecided about switching it to Tim's 'flightgear' namespace (and dropping the FG prefix), if we're going to go down that path I'd sooner submit a boring cleanup patch for the derived classes as well. James positioned.hxx Description: Binary data - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] f16 speedbrakes
Jon S. Berndt writes: I don't know if this matters, but remember that not too long ago we added the ability to enter aero coefficients in several coordinate systems - including BODY and WIND, etc. so if i were to represent the wind tunnel data in x,y,z axis then the drag due to horizontal tail deflection (the data on pages 45-49 of the nasa technical paper 1538) would then look like this: axis name=X function name=aero/coefficient/CDDh descriptionDrag_due_to_horizontal_tail_deflection/description product propertyaero/qbar-psf/property propertymetrics/Sw-sqft/property table name=CDdHT independentVar lookup=rowaero/beta-deg/independentVar independentVar lookup=columnaero/alpha-deg/independentVar independentVar lookup=tablefcs/elevator-pos-deg/independentVar tableData breakPoint=-25 -30 -25 -20 -15 -10 -8 -6 -4 -2 0 2 4 6 8 10 15 20 25 30 -20 -0.1837 -0.1853 -0.1904 -0.1899 -0.1949 -0.1914 -0.1872 -0.186 -0.186 -0.1868 -0.1899 -0.1902 -0.19 -0.1896 -0.1883 -0.1833 -0.1838 -0.1787 -0.1771 -15 -0.1714 -0.1765 -0.1792 -0.1827 -0.1816 -0.1834 -0.1852 -0.1853 -0.1877 -0.1875 -0.1898 -0.1876 -0.1868 -0.1848 -0.1841 -0.1852 -0.1817 -0.179 -0.1739 -10 -0.1531 -0.1627 -0.1692 -0.1718 -0.1695 -0.1693 -0.1707 -0.1735 -0.1772 -0.1787 -0.1769 -0.1729 -0.1711 -0.1706 -0.1698 -0.1721 -0.1695 -0.163 -0.1534 -5 -0.1151 -0.1232 -0.1276 -0.1317 -0.139 -0.1415 -0.142 -0.1425 -0.1437 -0.1432 -0.1425 -0.1422 -0.141 -0.1397 -0.1372 -0.1299 -0.1258 -0.1214 -0.1133 0 -0.0907 -0.0985 -0.1043 -0.1093 -0.112 -0.1115 -0.1122 -0.1124 -0.113 -0.1132 -0.1129 -0.1119 -0.111 -0.1102 -0.1092 -0.1065 -0.1015 -0.0957 -0.0879 5 -0.0514 -0.0567 -0.0603 -0.064 -0.0653 -0.0661 -0.0668 -0.0675 -0.069 -0.0693 -0.0686 -0.068 -0.0664 -0.065 -0.0649 -0.0631 -0.0594 -0.0558 -0.0505 10 -0.0079 -0.0108 -0.0099 -0.0101 -0.0074 -0.007 -0.0078 -0.009 -0.0116 -0.012 -0.0123 -0.0106 -0.0088 -0.0083 -0.008 -0.0107 -0.0105 -0.0114 -0.0085 15 0.0354 0.0358 0.0388 0.0402 0.0477 0.0503 0.0535 0.0553 0.0538 0.0537 0.0533 0.0536 0.0527 0.0509 0.0485 0.041 0.0396 0.0366 0.0362 20 0.074 0.0756 0.0746 0.0745 0.0867 0.0888 0.0924 0.0941 0.0948 0.0951 0.0975 0.0939 0.0913 0.0867 0.0824 0.0702 0.0703 0.0713 0.0697 25 0.1092 0.1124 0.1102 0.1067 0.1101 0.1121 0.1126 0.1129 0.1123 0. 0.1122 0.1125 0.1136 0.1115 0.1075 0.1041 0.1076 0.1098 0.1066 30 0.0915 0.101 0.0975 0.1079 0.1188 0.1333 0.1399 0.1422 0.1443 0.1435 0.1431 0.1407 0.1379 0.1359 0.1323 0.1214 0.111 0.1145 0.105 35 0.1079 0.1137 0.1198 0.1278 0.1402 0.1425 0.1478 0.157 0.1623 0.1663 0.1667 0.1664 0.1637 0.156 0.146 0.1336 0.1256 0.1195 0.1137 40 0.1306 0.1437 0.135 0.1441 0.1574 0.1585 0.1601 0.1682 0.1726 0.1739 0.1711 0.1699 0.1655 0.1611 0.1567 0.1434 0.1343 0.143 0.1299 45 0.1535 0.1603 0.1605 0.1604 0.1637 0.1671 0.1664 0.1639 0.1674 0.1659 0.1649 0.165 0.1625 0.1597 0.1573 0.154 0.1541 0.1539 0.1471 50 0.1471 0.1584 0.1646 0.1671 0.1712 0.1712 0.1676 0.1644 0.1656 0.1693 0.1714 0.1728 0.1749 0.1725 0.173 0.1537 0.1457 0.1435 0.1362 55 0.1554 0.1615 0.1568 0.1661 0.1778 0.1769 0.1765 0.1749 0.1762 0.1804 0.1743 0.1666 0.1677 0.1724 0.1761 0.1722 0.1347 0.1448 0.1442 60 0.1501 0.1599 0.1647 0.1525 0.1664 0.1662 0.1704 0.171 0.1719 0.1718 0.1728 0.173 0.1734 0.1721 0.1688 0.1471 0.1462 0.1486 0.146 70 0.1501 0.1536 0.1569 0.142 0.1573 0.1595 0.1788 0.1715 0.1738 0.1695 0.171 0.1712 0.173 0.172 0.1686 0.1474 0.1567 0.1557 0.1545 80 0.1685 0.1615 0.1559 0.152 0.1521 0.1521 0.1535 0.1585 0.1566 0.1598 0.1573 0.1563 0.1586 0.1558 0.1572 0.141 0.141 0.1467 0.1538 90 0.1712 0.1651 0.1608 0.1648 0.1676 0.166 0.1686 0.1667 0.1669 0.166 0.1672 0.1662 0.1664 0.1711 0.1677 0.1531 0.1493 0.1549 0.1624 /tableData tableData breakPoint=-10 -30 -25 -20 -15 -10 -8 -6 -4 -2 0 2 4 6 8 10 15 20 25 30 -20 -0.1362 -0.1351 -0.1419 -0.1386 -0.1374 -0.133 -0.1268 -0.1249 -0.1222 -0.1223 -0.1246 -0.1247 -0.1252 -0.1257 -0.1282 -0.1294 -0.1327 -0.1259 -0.127 -15 -0.1216 -0.1245 -0.1235 -0.1208 -0.1176 -0.1176 -0.117 -0.1177 -0.1184 -0.1188 -0.1185 -0.1187 -0.1182 -0.1178 -0.1184 -0.1216 -0.1243 -0.1253 -0.1224 -10 -0.1018 -0.1066 -0.1068 -0.1071 -0.1061 -0.1068 -0.1072 -0.1083 -0.1094 -0.1147 -0.1095 -0.1084 -0.1077 -0.1063 -0.1069 -0.1079 -0.1076 -0.1074 -0.1026 -5 -0.0655 -0.0706 -0.0746 -0.0771 -0.0836 -0.0864 -0.0876 -0.0887 -0.0889 -0.0893 -0.0885 -0.0875 -0.0859 -0.0842 -0.0812 -0.0747 -0.0722 -0.0682 -0.0631 0 -0.0483 -0.0509 -0.0532 -0.0544 -0.0578 -0.0589 -0.0597 -0.0606 -0.0613 -0.0617 -0.0611 -0.0603 -0.0595 -0.0577 -0.0561 -0.0527 -0.0515 -0.0492 -0.0466 5 -0.0118 -0.0106 -0.0096 -0.0102 -0.0142 -0.0148 -0.0155 -0.0161
Re: [Flightgear-devel] Windows and source code
On Thu, 2008-09-04 at 18:27 +0200, Stefan C. Müller wrote: I'd like to thank Stefan Muller for his excellent advice in getting me pointed in the right direction with compiling FG. However, at some 90% done I've run into two snags. The CVS download of FlightGear has a SimGear project in the FlightGear project file. But there is no SimGear.sln or SimGear.vcproj or SimGear anything. Is this a problem? If so how do I go about getting the simgear project for FlightGear. (I do have the SimGear project downloaded and compiled... so I am talking here of a flightgear project with the simgear subproject. Hope I'm clear on this). The second snag I ran into was a linker problem in the flight gear (VC7.1 version) GPSsmooth subproject. It complains that unresolved external symbol class std::vectorclass std::basic_stringchar,struct std::char_traitschar,class std::allocatorchar . and so on. If I am correct (And I am not a fluent Window's programmer) that should be part of the STL and MSvcrt.lib should be the library. I explicitly changed the additional dependencies in MSVC++ 2008 Express Edition to include MSvcrt.lib but that did not get rid of the error. As always, any help greatly appreciated. -- Geoff McLean McLean Research Associates To be good is not enough when you dream of being great. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
