Re: [Flightgear-devel] release thoughts
On 17 Nov 2008, at 12:27, James Turner wrote: > Binary build works for me, though precipitation is doing something > very, very odd that is killing frame-rates. Need to test on a second > machine and then I'll post a proper report with some screenshots. Okay, so on my 7300 equipped Macpro, precipitation looks strange - as if the point sprites had been scaled. There's no frame-to-frame coherency - some frames I see the expected rain/snow droplets, other frames I see enormous shaded spheres which I guess are the point sprite scaled up by a factor of a hundred or more. It's fine on my Radeon-equipped MacBook pro. The visual artefacts are accompanied by single-digit frame-rates, even quitting is tricky. If drag the precipitation slider back to zero, as soon as the rain stops, frame rates jump back to normal. I would post a screenshot, but it seems the Grab tool on Mac always grabs a 'correct' frame - I don't know how the tool works for GL contexts, but perhaps something funny happens which means it bypasses what is presumably another driver bug. Anyone else seeing this? 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Hi, I guess I somehow packed a bit older version of Atlas by mistake... :-p I already published a newer build that was statically linked so you don't have to worry about these dylibs. See this forum topic for further installation instruction: http://www.flightgear.org/forums/viewtopic.php?f=2&t=1887&p=20308&hilit=mac+atlas#p20308 By the way, did I tell that I got a feedback from Mac OS 10.4 user? It says that the latest fgfs/cvs binary works on Mac OS 10.4.11!! (Macbook Pro / C2D 2.16GHz / ATI Radeon X1600 / OS X 10.4.11 ) Yay! Tat On Nov 18, 2008, at 4:42 AM, Richard Hornby wrote: > Thanks for this - Atlas still a problem. Double clicking on Atlas > returns in terminal: > > ... > /Applications/FlightGear.app/Contents/Resources/Atlas ; exit; > MyMac:~ richardhornby$ /Applications/FlightGear.app/Contents/Resources/ > Atlas ; exit; > dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib > Referenced from: /Applications/FlightGear.app/Contents/Resources/ > Atlas > Reason: image not found > Trace/BPT trap > logout > ... > > and find on 'libpng' returns nothing. > > ? > > This is not stopping me from enjoying the release! > > Tks, > > R > > > > On 16 Nov 2008, at 23:48, Tatsuhiro Nishioka wrote: > >> Hi Richard, >> >> Thanks for the report. I really appreciate it. >> I'm also glad that it works on GeForce 8800!! >> >> >> On Nov 17, 2008, at 8:26 AM, Richard Hornby wrote: >>> >>> One odd issue is that in video playback of the BO105 the blades are >>> not turning and the aircraft carries its own shadow with it! >> >> This has something to do with either bo105 or playback feature. I'll >> check on it later. >> >>> Plus still can't get ~ /.atlas.sh & to work with Atlas even in >>> latest version. >> >> atlas.sh is not at ~/ but at /Applications/FlightGear.app/Contents/ >> Resources/atlas.sh >> >> To run it, you can do so by: >> 1) Open /Applications/Utilities/Terminal.app >> 2) type the following command on terminal. >> cd /Applications/FlightGear.app/Contents/Resources >> sh /atlas.sh >> >> # I guess I forgot to chmod 755 to atlas.sh sorry for that ;-) >> >> Okay, I'll leave my message so other users can catch this and give >> me feedbacks. >> Reports from 10.4 users are very welcome. >> I confirmed that the latest prebuilt package (as of 11/16) runs at least on: - MacBook Pro with Radeon X1600 (intel; 10.5.5) - MacBook with GMA X3100 (intel; 10.5.5) - iMac with GeForce7300GT (intel; 10.5.5) - iMac with ATI Radeon HD2400 (intel; 10.5.5) So in most of cases, it works fine but I still need to find the cause and workaround for each crash. Maybe the biggest problem is that it works fine on my machine. :-p So, I want many Mac users to give me feedbacks on the latest prebuilt flightgear/cvs. If some of you have Macs later than ppc/G4, please send me the following info: - name of your Mac (e.g. iMac) - CPU (e.g. Core 2 duo 2.1GHz) - GPU (e.g. ATI Radeon X1600) - OS version (e.g. OS X 10.5.5) - works or not (crash log and/or regular log if not) >> >> >> Tat >> >> - >> 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=100&url=/ >> ___ >> Flightgear-devel mailing list >> Flightgear-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > - > 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=100&url=/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Hi, On Nov 18, 2008, at 4:42 AM, Richard Hornby <[EMAIL PROTECTED]> wrote: > Thanks for this - Atlas still a problem. Double clicking on Atlas > returns in terminal: > (snip) > dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib > Referenced from: /Applications/FlightGear.app/Contents/Resources/ > Atlas > Reason: image not found > Trace/BPT trap > logout > ... > > and find on 'libpng' returns nothing. Oops, my bad. Libpng must be linked as a static library, not a dynamic library..., or at least I need to add the dylib to the package. I'll fix this problem asap. Thanks for your report! One solution ATM is that you download macports and build libpng yourself, but it is way far inconvenient for most of users. >> >> >> >>> >> >> >> >> >> >> >> >> - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
2008/11/18 Tatsuhiro Nishioka <[EMAIL PROTECTED]>: > > As James said, The crash was caused probably by driver bug related to > hardware mipmapping. > > [SNIP] > > Try the following commands (using /Applciations/Utilities/Terminal.app): > > [SNIP] That worked, thanks for the information. Looking forward to the final release! Thanks. - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Thanks for this - Atlas still a problem. Double clicking on Atlas returns in terminal: ... /Applications/FlightGear.app/Contents/Resources/Atlas ; exit; MyMac:~ richardhornby$ /Applications/FlightGear.app/Contents/Resources/ Atlas ; exit; dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib Referenced from: /Applications/FlightGear.app/Contents/Resources/ Atlas Reason: image not found Trace/BPT trap logout ... and find on 'libpng' returns nothing. ? This is not stopping me from enjoying the release! Tks, R On 16 Nov 2008, at 23:48, Tatsuhiro Nishioka wrote: > Hi Richard, > > Thanks for the report. I really appreciate it. > I'm also glad that it works on GeForce 8800!! > > > On Nov 17, 2008, at 8:26 AM, Richard Hornby wrote: >> >> One odd issue is that in video playback of the BO105 the blades are >> not turning and the aircraft carries its own shadow with it! > > This has something to do with either bo105 or playback feature. I'll > check on it later. > >> Plus still can't get ~ /.atlas.sh & to work with Atlas even in >> latest version. > > atlas.sh is not at ~/ but at /Applications/FlightGear.app/Contents/ > Resources/atlas.sh > > To run it, you can do so by: > 1) Open /Applications/Utilities/Terminal.app > 2) type the following command on terminal. > cd /Applications/FlightGear.app/Contents/Resources > sh /atlas.sh > > # I guess I forgot to chmod 755 to atlas.sh sorry for that ;-) > > Okay, I'll leave my message so other users can catch this and give > me feedbacks. > Reports from 10.4 users are very welcome. > >>> I confirmed that the latest prebuilt package (as of 11/16) runs at >>> least on: >>> - MacBook Pro with Radeon X1600 (intel; 10.5.5) >>> - MacBook with GMA X3100 (intel; 10.5.5) >>> - iMac with GeForce7300GT (intel; 10.5.5) >>> - iMac with ATI Radeon HD2400 (intel; 10.5.5) >>> >>> So in most of cases, it works fine but I still need to find the >>> cause and workaround for each crash. >>> Maybe the biggest problem is that it works fine on my machine. :-p >>> So, I want many Mac users to give me feedbacks on the latest >>> prebuilt flightgear/cvs. >>> If some of you have Macs later than ppc/G4, please send me the >>> following info: >>> - name of your Mac (e.g. iMac) >>> - CPU (e.g. Core 2 duo 2.1GHz) >>> - GPU (e.g. ATI Radeon X1600) >>> - OS version (e.g. OS X 10.5.5) >>> - works or not (crash log and/or regular log if not) > > > Tat > > - > 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=100&url=/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Hi Pooyan, Nice to hear from you again. As James said, The crash was caused probably by driver bug related to hardware mipmapping. I'll fix this until the next snapshot release. A good news is that you don't have to wait until the next release. Since I applied my own patch to mac version so you can disable hardware mipmapping for avoiding this crash. Try the following commands (using /Applciations/Utilities/Terminal.app): cd /Applications/FlightGear.app/Contents/Resources export OSG_GL_EXTENSION_DISABLE="GL_SGIS_generate_mipmap;GL_EXT_framebuffer_object" ./fgfs.sh --aircraft= --airport= you can also add the second command to fgfs.sh (right before calling fgfs) so you don't have to type these every time. Tat On Nov 17, 2008, at 3:38 PM, Pooyan McSporran wrote: > 2008/11/17 Tatsuhiro Nishioka <[EMAIL PROTECTED]>: >> >> Thanks for the report. I really appreciate it. >> I'm also glad that it works on GeForce 8800!! > > Tatsuhiro, > > I've tried FlightGear-cvs-bin-20081116.dmg on my 24" iMac but it > crashes. Here are the relevant parameters: > > - CPU is an Intel Core 2 Duo, 2.33 GHz, with 2GB of RAM > - GPU is NVIDIA GeForce 7600 GT (not a 7300!) with 256MB of VRAM > - OS is Mac OS X 10.5.5 > > The crash log is available, I can email it to you if you like (it's a > bit too long to attach in the mailing list). But I've pasted the > important bit below. Let me know if you'd like me to try anything > different (direct email is ok). > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x2258a008 > Crashed Thread: 0 > > Thread 0 Crashed: > 0 com.apple.GeForceFXGLDriver 0x02a267b0 gldUpdateDispatch + 138224 > 1 com.apple.GeForceFXGLDriver 0x02a2751a gldUpdateDispatch + 141658 > 2 com.apple.GeForceFXGLDriver 0x029ec215 gldAllocVertexBuffer + > 25909 > 3 com.apple.GeForceFXGLDriver 0x029ee9c5 gldAllocVertexBuffer + > 36069 > 4 com.apple.GeForceFXGLDriver 0x029f01d6 gldGetTextureLevel + 2534 > 5 GLEngine0x0173ca14 gleGenMipmaps + 132 > 6 GLEngine0x016146bc glTexImage2D_Exec + 1116 > 7 libGL.dylib 0x94c2f237 glTexImage2D + 87 > 8 org.OpenSceneGraph.osg 0x008474af > osg::Texture::applyTexImage2D_load(osg::State&, unsigned int, > osg::Image const*, int, int, int) const + 2655 > 9 org.OpenSceneGraph.osg 0x0084d7c8 > osg::Texture2D::apply(osg::State&) const + 2400 > > - > 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=100&url=/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
On 17 Nov 2008, at 08:17, James Turner wrote: >> - Crash on Mac Pro (crash report from James Turner, waiting further >> feedback from him). > > About to test the binary build, the results with my own build are > depressing - something is definitely altering the RTTI information. I > was going to say 'corrupting' but it seems very consistent. Binary build works for me, though precipitation is doing something very, very odd that is killing frame-rates. Need to test on a second machine and then I'll post a proper report with some screenshots. 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Hi, As far as I'm concerned, I prefer a simple INSTALL file where I find the dependance : OSG 2.6.0 plib 1.8.5 etc... For the Linux distribution where the good release isn't present, we can't provide a new package built by the FG community. To day, I have my own package for OSG and PLIB. And of course a FG/SG releaes has to be used with an official release of OSG, Plib, etc... (and don't use a CVS/SVN devel) I can build also FG / SG packages : simgear-cvs_20081117_i386.deb simgear-dev_20081117_i386.deb Otherwise, we will link all lib in static with FG/SG (OSG, plib, libc... kernel ?) Regards, Nicolas On Sun, 16 Nov 2008 19:07:16 +0100, Tim Moore <[EMAIL PROTECTED]> wrote: > As thoughts are turning towards a release, I wanted to bring up a couple of > things. This time we are depending on libraries -- OpenSceneGraph -- that > are > not usually built statically. They are built for dynamic linking, and > libraries > that implement data file loading are loaded and linked on demand according > to > the file extension of the loaded model. OpenSceneGraph can be linked > statically, > but this seems to cause people problems -- from what I can see on the > osg-users > mailing list -- and would lose some of the model-loading flexibility we > get for > free with OSG. So, I recommend we ship the dynamically linked libraries > with our > binary releases and resign ourselves to doing what's necessary to make > this work > when FlightGear is installed. On Linux, I think it is easiest to have a > front-end script that will set the proper library path to pick up these > libraries. > > On Linux you might think that we could blow this off and depend on the > distributions' OpenSceneGraph package, but this is not practical. > OpenSceneGraph > releases come fast and furious; we will be depending on OSG 2.8, and (for > example) my distribution of choice is still supplying 2.2. So we need to > supply > to proper version. > > I'm happy to punt Windows and Mac issues to people who are knowledgeable > about > that. For Linux, should we try to build a binary release to an LSB > standard? > http://ldn.linuxfoundation.org/lsb > > Thanks, > Tim > > - > 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=100&url=/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
On 16 Nov 2008, at 23:07, Tatsuhiro Nishioka wrote: > - Crash on Mac Pro (crash report from James Turner, waiting further > feedback from him). About to test the binary build, the results with my own build are depressing - something is definitely altering the RTTI information. I was going to say 'corrupting' but it seems very consistent. 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
On Monday 17 November 2008 09:20:14 James Turner wrote: > > In the past I've worked on binary distributions for various GL-based > projects on Linux, one using VTK and one using OGRE. In both cases we > ended up shipping libstdc++ as well - in order to have a chance at > portability, the only externals you can rely on need to have C > linkage, not C++ linkage. It is possible to make C++ dependencies > work, but it seems to complicate things unduly, whereas shipping the > libstdc++ that the binaries were built with is easy. > > Maybe this situation has improved recently, however - my knowledge of > this is currently two years old. AFAIK libstdc++ is in LSB nowadays, so the situation should be better. > On 16 Nov 2008, at 18:07, Tim Moore wrote: > > On Linux you might think that we could blow this off and depend on the > > distributions' OpenSceneGraph package, but this is not practical. > > OpenSceneGraph > > releases come fast and furious; we will be depending on OSG 2.8, and > > (for > > example) my distribution of choice is still supplying 2.2. So we > > need to supply > > to proper version. To me it sounds like making sure that more recent OSG packages are available for these distros is the way to go. With the openSUSE build service, it's very easy to build and provide packages even for distributions you don't have yourself. I'd say it's definitely worth a look: https://build.opensuse.org/ Stefan signature.asc Description: This is a digitally signed message part. - 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=100&url=/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
On 16 Nov 2008, at 18:07, Tim Moore wrote: > On Linux you might think that we could blow this off and depend on the > distributions' OpenSceneGraph package, but this is not practical. > OpenSceneGraph > releases come fast and furious; we will be depending on OSG 2.8, and > (for > example) my distribution of choice is still supplying 2.2. So we > need to supply > to proper version. In the past I've worked on binary distributions for various GL-based projects on Linux, one using VTK and one using OGRE. In both cases we ended up shipping libstdc++ as well - in order to have a chance at portability, the only externals you can rely on need to have C linkage, not C++ linkage. It is possible to make C++ dependencies work, but it seems to complicate things unduly, whereas shipping the libstdc++ that the binaries were built with is easy. Maybe this situation has improved recently, however - my knowledge of this is currently two years old. 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
On 17 Nov 2008, at 06:38, Pooyan McSporran wrote: > I've tried FlightGear-cvs-bin-20081116.dmg on my 24" iMac but it > crashes. Here are the relevant parameters: > > - CPU is an Intel Core 2 Duo, 2.33 GHz, with 2GB of RAM > - GPU is NVIDIA GeForce 7600 GT (not a 7300!) with 256MB of VRAM > - OS is Mac OS X 10.5.5 > > The crash log is available, I can email it to you if you like (it's a > bit too long to attach in the mailing list). But I've pasted the > important bit below. Let me know if you'd like me to try anything > different (direct email is ok). > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x2258a008 > Crashed Thread: 0 > > Thread 0 Crashed: > 0 com.apple.GeForceFXGLDriver 0x02a267b0 gldUpdateDispatch > + 138224 > 1 com.apple.GeForceFXGLDriver 0x02a2751a gldUpdateDispatch > + 141658 > 2 com.apple.GeForceFXGLDriver 0x029ec215 > gldAllocVertexBuffer + 25909 > 3 com.apple.GeForceFXGLDriver 0x029ee9c5 > gldAllocVertexBuffer + 36069 > 4 com.apple.GeForceFXGLDriver 0x029f01d6 > gldGetTextureLevel + 2534 > 5 GLEngine0x0173ca14 gleGenMipmaps + 132 > 6 GLEngine0x016146bc glTexImage2D_Exec > + 1116 > 7 libGL.dylib 0x94c2f237 glTexImage2D + 87 > 8 org.OpenSceneGraph.osg 0x008474af > osg::Texture::applyTexImage2D_load(osg::State&, unsigned int, > osg::Image const*, int, int, int) const + 2655 > 9 org.OpenSceneGraph.osg 0x0084d7c8 > osg::Texture2D::apply(osg::State&) const + 2400 This is the 7300 hardware-mip-mapping crash, so we need to widen the GL driver check to include all 7000 series nvidia chipsets on Mac, I would guess. It's good that 8000 series chips are apparently unaffected. 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
2008/11/17 Tatsuhiro Nishioka <[EMAIL PROTECTED]>: > > Thanks for the report. I really appreciate it. > I'm also glad that it works on GeForce 8800!! Tatsuhiro, I've tried FlightGear-cvs-bin-20081116.dmg on my 24" iMac but it crashes. Here are the relevant parameters: - CPU is an Intel Core 2 Duo, 2.33 GHz, with 2GB of RAM - GPU is NVIDIA GeForce 7600 GT (not a 7300!) with 256MB of VRAM - OS is Mac OS X 10.5.5 The crash log is available, I can email it to you if you like (it's a bit too long to attach in the mailing list). But I've pasted the important bit below. Let me know if you'd like me to try anything different (direct email is ok). Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x2258a008 Crashed Thread: 0 Thread 0 Crashed: 0 com.apple.GeForceFXGLDriver 0x02a267b0 gldUpdateDispatch + 138224 1 com.apple.GeForceFXGLDriver 0x02a2751a gldUpdateDispatch + 141658 2 com.apple.GeForceFXGLDriver 0x029ec215 gldAllocVertexBuffer + 25909 3 com.apple.GeForceFXGLDriver 0x029ee9c5 gldAllocVertexBuffer + 36069 4 com.apple.GeForceFXGLDriver 0x029f01d6 gldGetTextureLevel + 2534 5 GLEngine0x0173ca14 gleGenMipmaps + 132 6 GLEngine0x016146bc glTexImage2D_Exec + 1116 7 libGL.dylib 0x94c2f237 glTexImage2D + 87 8 org.OpenSceneGraph.osg 0x008474af osg::Texture::applyTexImage2D_load(osg::State&, unsigned int, osg::Image const*, int, int, int) const + 2655 9 org.OpenSceneGraph.osg 0x0084d7c8 osg::Texture2D::apply(osg::State&) const + 2400 - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Hi Richard, Thanks for the report. I really appreciate it. I'm also glad that it works on GeForce 8800!! On Nov 17, 2008, at 8:26 AM, Richard Hornby wrote: > > One odd issue is that in video playback of the BO105 the blades are not > turning and the aircraft carries its own shadow with it! This has something to do with either bo105 or playback feature. I'll check on it later. > Plus still can't get ~ /.atlas.sh & to work with Atlas even in latest > version. atlas.sh is not at ~/ but at /Applications/FlightGear.app/Contents/Resources/atlas.sh To run it, you can do so by: 1) Open /Applications/Utilities/Terminal.app 2) type the following command on terminal. cd /Applications/FlightGear.app/Contents/Resources sh /atlas.sh # I guess I forgot to chmod 755 to atlas.sh sorry for that ;-) Okay, I'll leave my message so other users can catch this and give me feedbacks. Reports from 10.4 users are very welcome. >> I confirmed that the latest prebuilt package (as of 11/16) runs at least on: >> - MacBook Pro with Radeon X1600 (intel; 10.5.5) >> - MacBook with GMA X3100 (intel; 10.5.5) >> - iMac with GeForce7300GT (intel; 10.5.5) >> - iMac with ATI Radeon HD2400 (intel; 10.5.5) >> >> So in most of cases, it works fine but I still need to find the cause and >> workaround for each crash. >> Maybe the biggest problem is that it works fine on my machine. :-p >> So, I want many Mac users to give me feedbacks on the latest prebuilt >> flightgear/cvs. >> If some of you have Macs later than ppc/G4, please send me the following >> info: >> - name of your Mac (e.g. iMac) >> - CPU (e.g. Core 2 duo 2.1GHz) >> - GPU (e.g. ATI Radeon X1600) >> - OS version (e.g. OS X 10.5.5) >> - works or not (crash log and/or regular log if not) Tat - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Works basically well for me in all the CVS versions on OS X 10.5.5 Model Name: iMac Model Identifier: iMac8,1 Processor Name: Intel Core 2 Duo Processor Speed: 3.06 GHz Number Of Processors: 1 Total Number Of Cores:2 L2 Cache: 6 MB Memory: 2 GB Bus Speed:1.07 GHz Chipset Model: NVIDIA GeForce 8800 GS Type: Display Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 512 MB One odd issue is that in video playback of the BO105 the blades are not turning and the aircraft carries its own shadow with it! Plus still can't get ~ /.atlas.sh & to work with Atlas even in latest version. But it's great to have the pre-compiled version and it looks brill on the big screen. Tks, R On 16 Nov 2008, at 23:07, Tatsuhiro Nishioka wrote: Hi Durk, Glad to hear that you can be heading onto the release process. On Nov 17, 2008, at 5:59 AM, Durk Talsma wrote: - Compile a comprehensive change log - Finish the final selection of aircraft for inclusion in the release - Check any issues that may come up with regard to Scenery - Check how things are proceeding on the windows and Mac front. So far Mac platform has the following problems: - NVIDIA dirver bug - fixed and waiting for feedbacks from users; patch sent to osg team but not yet applied. - MAY crash inside OSG on Mac Mini with GMA 950 - sent problem report to OSG team but no response yet. - MAY crash on MacBook Air (only one report. need to investigate). - Crash on Mac Pro (crash report from James Turner, waiting further feedback from him). - Likely lack of compatibility with Mac OS X 10.4 - Wait for feedbacks from OS X 10.4 users on the latest build. There's an optimization problem on gcc 4.0 (crashes on initializing static class instances with -O1 or faster), now I'm using gcc 4.2, but gcc 4.2 comes with Xcode is only for 10.5 sdk (it is said that it is compatible as long as you don't use 10.5 specific functions) I'm still not sure if it runs on OS X 10.4. - Mac specific portion of Manual - being written and patch will soon be sent, hopefully. - Sometimes (not often) fgfs crashes on exit (can not reproduce so it could be a timing issue. still being investigated) I confirmed that the latest prebuilt package (as of 11/16) runs at least on: - MacBook Pro with Radeon X1600 (intel; 10.5.5) - MacBook with GMA X3100 (intel; 10.5.5) - iMac with GeForce7300GT (intel; 10.5.5) - iMac with ATI Radeon HD2400 (intel; 10.5.5) So in most of cases, it works fine but I still need to find the cause and workaround for each crash. Maybe the biggest problem is that it works fine on my machine. :-p So, I want many Mac users to give me feedbacks on the latest prebuilt flightgear/cvs. If some of you have Macs later than ppc/G4, please send me the following info: - name of your Mac (e.g. iMac) - CPU (e.g. Core 2 duo 2.1GHz) - GPU (e.g. ATI Radeon X1600) - OS version (e.g. OS X 10.5.5) - works or not (crash log and/or regular log if not) I'm also planning to update the GUI launcher for more usability and Atlas integration, but I'm not sure if I can have time to do so. Maybe it would be postponed until some time after the official release, like always :-( Anyway, If I can either solve (or ignore :-p) the problems above, there's no difficulties in preparing the official release. When the new release branch is made, I'll make a release candidate in a few days. Another my concern is "what version of OSG will we use for coming official release? 2.8 as Tim said?" Tat - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - 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=100&url=/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Hi Durk, Glad to hear that you can be heading onto the release process. On Nov 17, 2008, at 5:59 AM, Durk Talsma wrote: > - Compile a comprehensive change log > - Finish the final selection of aircraft for inclusion in the release > - Check any issues that may come up with regard to Scenery > - Check how things are proceeding on the windows and Mac front. So far Mac platform has the following problems: - NVIDIA dirver bug - fixed and waiting for feedbacks from users; patch sent to osg team but not yet applied. - MAY crash inside OSG on Mac Mini with GMA 950 - sent problem report to OSG team but no response yet. - MAY crash on MacBook Air (only one report. need to investigate). - Crash on Mac Pro (crash report from James Turner, waiting further feedback from him). - Likely lack of compatibility with Mac OS X 10.4 - Wait for feedbacks from OS X 10.4 users on the latest build. There's an optimization problem on gcc 4.0 (crashes on initializing static class instances with -O1 or faster), now I'm using gcc 4.2, but gcc 4.2 comes with Xcode is only for 10.5 sdk (it is said that it is compatible as long as you don't use 10.5 specific functions) I'm still not sure if it runs on OS X 10.4. - Mac specific portion of Manual - being written and patch will soon be sent, hopefully. - Sometimes (not often) fgfs crashes on exit (can not reproduce so it could be a timing issue. still being investigated) I confirmed that the latest prebuilt package (as of 11/16) runs at least on: - MacBook Pro with Radeon X1600 (intel; 10.5.5) - MacBook with GMA X3100 (intel; 10.5.5) - iMac with GeForce7300GT (intel; 10.5.5) - iMac with ATI Radeon HD2400 (intel; 10.5.5) So in most of cases, it works fine but I still need to find the cause and workaround for each crash. Maybe the biggest problem is that it works fine on my machine. :-p So, I want many Mac users to give me feedbacks on the latest prebuilt flightgear/cvs. If some of you have Macs later than ppc/G4, please send me the following info: - name of your Mac (e.g. iMac) - CPU (e.g. Core 2 duo 2.1GHz) - GPU (e.g. ATI Radeon X1600) - OS version (e.g. OS X 10.5.5) - works or not (crash log and/or regular log if not) I'm also planning to update the GUI launcher for more usability and Atlas integration, but I'm not sure if I can have time to do so. Maybe it would be postponed until some time after the official release, like always :-( Anyway, If I can either solve (or ignore :-p) the problems above, there's no difficulties in preparing the official release. When the new release branch is made, I'll make a release candidate in a few days. Another my concern is "what version of OSG will we use for coming official release? 2.8 as Tim said?" Tat - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
On dimanche 16 novembre 2008, Tim Moore wrote: > gerard robin wrote: SNIP > > That's works for me, or at least the cmake equivalent does, but we're > talking about a binary release where we don't ask end users to build > packages. > SNIP > > > > I hope i misunderstand , and what you say is not an other difficulty for > > us. > > I think you misunderstood. > > > Or this will be the end , at least for me, to work on the fg cvs > > version. freezing it to any new stable version. > > Tim Thanks -- Gérard http://pagesperso-orange.fr/GRTux/ J'ai décidé d'être heureux parce que c'est bon pour la santé. Voltaire - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Just to approach the perspective of a new release from a slightly different angle. I would indeed like to start piecing it all together. As I mentioned previously, my last three months have been rather hectic. Starting a new job, moving, and being without an internet connection for nearly two months. But, as I'm settling in into my new job, new home, with my internet connection restored, and with a new FlightGear capable computer almost assembled, it looks like I'm fully in the green to resume my duties as release coordinator. As far as I can tell, we're in a really good shape right now. Are there any pressing issues that we need to resolve before we can do a major release. If not, I would like to try and roll up a prerelease version of the source and data directory. Even though we are close to being ready to release, it would still be a good thing to take a few weeks to iron out any remaining rough edges. This would also give me an opportunity to finish the remaining issues. In particular, I still need to do the following: - Compile a comprehensive change log - Finish the final selection of aircraft for inclusion in the release - Check any issues that may come up with regard to Scenery - Check how things are proceeding on the windows and Mac front. For this reason, I'm aiming to have everything ready by December 16, or thereabouts. In the mean time, we should probably focus on improving stability instead of adding new features. Cheers, Durk - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Hi, I always pack everything inside FlightGear.app folder. The OSG in Mac binary package includes frameworks (same as DLL or so) and plugins. The GUI launcher calls a script (fgfs.sh) that sets DYLD_LIBRARY_PATH (same as LD_LIBRARY_PATH in linux) to specify plugin folders before invoking fgfs. The script look like: #!/bin/bash DYLD_LIBRARY_PATH=$PWD/plugins exec fgfs $* If OSG detects plugins inside application folder, this script is not needed. OSG does have such code but it doesn't seem working properly at this moment. maybe I need to write a patch for that. Hope it helps. On Nov 17, 2008, at 3:25 AM, Frederic Bouvier wrote: > Tim Moore a écrit : >> I'm happy to punt Windows and Mac issues to people who are knowledgeable >> about >> that. For Linux, should we try to build a binary release to an LSB standard? >> http://ldn.linuxfoundation.org/lsb >> > > For Windows users, I already provide builds that includes the complete > collection of OpenSceneGraph DLLs and executable ( examples excluded ). > The next step would be to update the Inno-setup script to install all > that binaries in the bin folder. > > -Fred > > -- > Frédéric Bouvier > http://my.fotolia.com/frfoto/ Photo gallery > http://fgsd.sourceforge.net/FlightGear Scenery Designer > > > - > 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=100&url=/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
gerard robin wrote: > On dimanche 16 novembre 2008, Tim Moore wrote: >> As thoughts are turning towards a release, I wanted to bring up a couple of >> things. This time we are depending on libraries -- OpenSceneGraph -- that >> are not usually built statically. They are built for dynamic linking, and ... >> > i am trying to understand the problem, do you mean that the "standard" which > is offered by OSG people doesn't suit to our usual needs. > > ./configure > ./make > That's works for me, or at least the cmake equivalent does, but we're talking about a binary release where we don't ask end users to build packages. > Without a lot of additional parameters, we can build and use the stable > version of OSG, that is what i do, waiting for the next stable realease, > instead of permanently updating it with the last svn. > > This is simple and untersatandable to any person mainly whose the world of > development is the past (far away), like for me. > and usable to any person who is not spending full time in front of their > computer. > > I hope i misunderstand , and what you say is not an other difficulty for us. I think you misunderstood. > > Or this will be the end , at least for me, to work on the fg cvs version. > freezing it to any new stable version. Tim - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
On dimanche 16 novembre 2008, Tim Moore wrote: > As thoughts are turning towards a release, I wanted to bring up a couple of > things. This time we are depending on libraries -- OpenSceneGraph -- that > are not usually built statically. They are built for dynamic linking, and > libraries that implement data file loading are loaded and linked on demand > according to the file extension of the loaded model. OpenSceneGraph can be > linked statically, but this seems to cause people problems -- from what I > can see on the osg-users mailing list -- and would lose some of the > model-loading flexibility we get for free with OSG. So, I recommend we ship > the dynamically linked libraries with our binary releases and resign > ourselves to doing what's necessary to make this work when FlightGear is > installed. On Linux, I think it is easiest to have a front-end script that > will set the proper library path to pick up these libraries. > > On Linux you might think that we could blow this off and depend on the > distributions' OpenSceneGraph package, but this is not practical. > OpenSceneGraph releases come fast and furious; we will be depending on OSG > 2.8, and (for example) my distribution of choice is still supplying 2.2. So > we need to supply to proper version. > > I'm happy to punt Windows and Mac issues to people who are knowledgeable > about that. For Linux, should we try to build a binary release to an LSB > standard? http://ldn.linuxfoundation.org/lsb > > Thanks, > Tim > i am trying to understand the problem, do you mean that the "standard" which is offered by OSG people doesn't suit to our usual needs. ./configure ./make Without a lot of additional parameters, we can build and use the stable version of OSG, that is what i do, waiting for the next stable realease, instead of permanently updating it with the last svn. This is simple and untersatandable to any person mainly whose the world of development is the past (far away), like for me. and usable to any person who is not spending full time in front of their computer. I hope i misunderstand , and what you say is not an other difficulty for us. Or this will be the end , at least for me, to work on the fg cvs version. freezing it to any new stable version. Cheers -- Gérard http://pagesperso-orange.fr/GRTux/ J'ai décidé d'être heureux parce que c'est bon pour la santé. Voltaire - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] release thoughts
Tim Moore a écrit : > I'm happy to punt Windows and Mac issues to people who are knowledgeable > about > that. For Linux, should we try to build a binary release to an LSB standard? > http://ldn.linuxfoundation.org/lsb > For Windows users, I already provide builds that includes the complete collection of OpenSceneGraph DLLs and executable ( examples excluded ). The next step would be to update the Inno-setup script to install all that binaries in the bin folder. -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery http://fgsd.sourceforge.net/FlightGear Scenery Designer - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] release thoughts
As thoughts are turning towards a release, I wanted to bring up a couple of things. This time we are depending on libraries -- OpenSceneGraph -- that are not usually built statically. They are built for dynamic linking, and libraries that implement data file loading are loaded and linked on demand according to the file extension of the loaded model. OpenSceneGraph can be linked statically, but this seems to cause people problems -- from what I can see on the osg-users mailing list -- and would lose some of the model-loading flexibility we get for free with OSG. So, I recommend we ship the dynamically linked libraries with our binary releases and resign ourselves to doing what's necessary to make this work when FlightGear is installed. On Linux, I think it is easiest to have a front-end script that will set the proper library path to pick up these libraries. On Linux you might think that we could blow this off and depend on the distributions' OpenSceneGraph package, but this is not practical. OpenSceneGraph releases come fast and furious; we will be depending on OSG 2.8, and (for example) my distribution of choice is still supplying 2.2. So we need to supply to proper version. I'm happy to punt Windows and Mac issues to people who are knowledgeable about that. For Linux, should we try to build a binary release to an LSB standard? http://ldn.linuxfoundation.org/lsb Thanks, Tim - 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=100&url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
