Re: [Flightgear-devel] AH-1 Merge Request
On Sat, Feb 19, 2011 at 4:54 AM, Jack Mermod wrote: Hi, As many of the textures were originally photos, they were edited in .jpg format and sent to me like that. I made the careless mistake of simply changing the extension from jpg to png. I will convert these the proper way in photoshop, and commit it to the AH-1's repository, which can be seen here: http://www.gitorious.org/bell-ah-1-cobra If I commit my changes there, will you be able to merge the files directly from my repo into fgdata? Sure. Let me know when you've sorted out the textures. Note that I can't guarantee I'll be able to get to it immediately, so I'll just commit whatever is in HEAD when I get to it. Is that OK? BTW, it's grown quite a bit since the last update - from 24MB to 38MB. You might want to see if there are any textures that can be reduced in size. -Stuart -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Logos and licensing
On Fri, 18 Feb 2011 13:50:25 +0100, Oliver wrote in message 20110218125025.291...@gmx.net: Stuart wrote: snip I agree with Jon on this - ideally we should be pro-active about asking for permission, even if we don't like the answer. Very good points mentioned. Especially the point that this will increase FGs appearance on some radars. However lots of people are nowadays using Google so the debate has become public anyway. I would to point out that besides the two results yes and no there might be a third one worth considering which is: No answer from the TM holder. This might be treated the same as yes or no. In case of treating it as yes we should agree how to treat potential consequences ;) Oliver ..that third option can easily be split in 3; 3a) Prepare to plead mercy in the courts, 3b) Depend on mercy in the courts, and 3c) Plead mercy in the courts. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] FGrun compile problem against v.2.2 git
I find issues with building FGrun on Ubuntu 10:10 FG and SG are both current from the git repostories FG run is v1.5.2 Make stops with: In file included from wizard.cxx:7: wizard.h:331: error: ‘string’ does not name a type make[2]: *** [wizard.o] Error 1 wizard.h line 331 is : FlightGearThread *fgThread; I have done it on a minimal system only added libfltk1.1 libfltk1.1-dev to the list I use for FG. I get the same result with the brisca script. I did compile this version of fgrun against v2.0 ok before with the same compiler and installs needed for FG. This is the compile command, the fktk on the end makes no difference if its thee or not. ./configure --prefix=$prefix CPPFLAGS=-I$prefix/include/ LDFLAGS=-L$prefix/lib -L$prefix/lib64 --with-fltk=/usr/local Is this an issue from compiling fgrun to the git version of FG? -- Regards Harry -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FGrun compile problem against v.2.2 git
On Sat, Feb 19, 2011 at 2:28 PM, Harry Campigli harryc...@gmail.com wrote: I find issues with building FGrun on Ubuntu 10:10 FG and SG are both current from the git repostories FG run is v1.5.2 Make stops with: In file included from wizard.cxx:7: wizard.h:331: error: ‘string’ does not name a type make[2]: *** [wizard.o] Error 1 wizard.h line 331 is : FlightGearThread *fgThread; Sounds like you are looking at the wrong file/line, since that line doesn't have string on it. Is this an issue from compiling fgrun to the git version of FG? This is a problem in fgrun, it is missing #include string and/or it has problem with properly referencing the namespace. -- Csaba/Jester -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FGrun compile problem against v.2.2 git
Thanks Csaba Sorry I must have been in error copying line 331 to the post incorrectly. Any how : Puttting adding namespace std; in the wizard.h file as I saw someone suggest for fgrun elsewhere works around the problem. Harry On Sat, Feb 19, 2011 at 10:49 PM, Csaba Halász csaba.hal...@gmail.comwrote: On Sat, Feb 19, 2011 at 2:28 PM, Harry Campigli harryc...@gmail.com wrote: I find issues with building FGrun on Ubuntu 10:10 FG and SG are both current from the git repostories FG run is v1.5.2 Make stops with: In file included from wizard.cxx:7: wizard.h:331: error: ‘string’ does not name a type make[2]: *** [wizard.o] Error 1 wizard.h line 331 is : FlightGearThread *fgThread; Sounds like you are looking at the wrong file/line, since that line doesn't have string on it. Is this an issue from compiling fgrun to the git version of FG? This is a problem in fgrun, it is missing #include string and/or it has problem with properly referencing the namespace. -- Csaba/Jester -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] minor spelling mistake...
It's Golden Eagle. :) Awesome airplane. g. - Log - commit 8a793672e68b9540816f4674b0e5c0e3622626d5 Merge: 723bfc5 96f882b Author: BARANGER Emmanuel Date: Sat Feb 19 10:38:32 2011 +0100 Merge branch 'master' of git://gitorious.org/fg/fgdata commit 723bfc5d66805e22b35a58fbb2f25634ccd918f3 Author: BARANGER Emmanuel Date: Sat Feb 19 10:04:04 2011 +0100 Cessna 421 Golden Eagel -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] ..3 different shader bugs?, was: minor spelling mistake...
On Sat, 19 Feb 2011 08:43:54 -0800 (PST), Gene wrote in message alpine.lfd.2.00.1102190840040.19...@grumble.deltasoft.com: It's Golden Eagle. :) Awesome airplane. ..yes, and he fixed the wee spelling snag, but _which_ colors did Emmanuel mean to put on his craft??? ..chasing the ati|radeon shader bug http://code.google.com/p/flightgear-bugs/issues/detail?id=264 a radeon driver update washed off the tar leaving a smoke sheen, that goes away if you disable the Material shaders. Furthermore, if you dis|enable the Random objects, and time your screenshot _just_ right (takes a little practice ;o)), you'll be able to capture that wee little blink of right colors. ..the fgfs-2.0.0-3-00[1-5].png are Debian Sid 2.0.0-3 shots, the fgfs-screen-0*.png etc are FG-git screen shots: https://github.com/gasguru/flightgearthings/tree/master/smoke-sheen ..the paint colors looks right when the Material shaders are off: https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-003.png https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-004.png https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-007.png https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-006.png ..but Emmanuel's(?) splash screen match 'the Material shaders are on': https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-012.png https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-018.png ..the wire frame bird is FG's own 737 737-700: https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-005.png -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] ..3 different shader bugs?, was: minor spelling mistake...
..the paint colors looks right when the Material shaders are off: https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-003.png https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-004.png https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-007.png https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-006.png ..but Emmanuel's(?) splash screen match 'the Material shaders are on': https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-012.png https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-018.png That's due the fact, that he uses his own version of effect file, and with that a too strong effect. Not a bug- it's author's fault ;-) -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] ..another nice promising bird in git: se5 :o)
Hi, ..it's a sweet wee pussycat as far as handling goes, also on roll-out, where it appears to _try_ carry the full weight of its shadow: ;o) https://github.com/gasguru/flightgearthings/raw/master/smoke-sheen/fgfs-screen-001.png ..the sim brakes are ok in KSFO grass, but could use a disk lube job after brake disk rust removal, waaay too touchy now for KFSO tarmac. ..pay due attention to the ground crew on start-up. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] AH-1 Merge Request
Hi Stuart, I've converted the textures, deleted unused/outdated files, and done my best to keep the file size down. Now the AH-1 is ready to be merged. http://gitorious.org/bell-ah-1-cobra Thanks, Jack -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FGrun compile problem against v.2.2 git
It doesn't make sense to me because neither line 331, nor the line you cited has string in them. Moreover, line 13 of wizard.h reads using std::string; Are you sure your sources of fgrun are current and you don't have an old wizard.h elsewhere ? Regards, -Fred - Harry Campigli a écrit : Thanks Csaba Sorry I must have been in error copying line 331 to the post incorrectly. Any how : Puttting adding namespace std; in the wizard.h file as I saw someone suggest for fgrun elsewhere works around the problem. On Sat, Feb 19, 2011 at 10:49 PM, Csaba Halász csaba.hal...@gmail.com wrote: On Sat, Feb 19, 2011 at 2:28 PM, Harry Campigli harryc...@gmail.com wrote: I find issues with building FGrun on Ubuntu 10:10 FG and SG are both current from the git repostories FG run is v1.5.2 Make stops with: In file included from wizard.cxx:7: wizard.h:331: error: ‘string’ does not name a type make[2]: *** [wizard.o] Error 1 wizard.h line 331 is : FlightGearThread *fgThread; Sounds like you are looking at the wrong file/line, since that line doesn't have string on it. Is this an issue from compiling fgrun to the git version of FG? This is a problem in fgrun, it is missing #include string and/or it has problem with properly referencing the namespace. -- Frédéric Bouvier http://www.youtube.com/user/fgfred64 Videos -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FGrun compile problem against v.2.2 git
On Sat, Feb 19, 2011 at 10:44 PM, Frederic Bouvier fredfgf...@free.fr wrote: Moreover, line 13 of wizard.h reads using std::string; Which, incidentally, is not something you like to see in header files. But I guess we can live with that in FGRun. -- Csaba/Jester -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] double check my git instruction,
To be sure I am building what I think I am, What git clone instruction do i need to give to download the fgV2.2.0 being prepared for release -- Regards Harry -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
