Re: [Flightgear-devel] the master branch
Tim Moore wrote: On 11/27/2009 10:08 AM, Erik Hofman wrote: You could argue that the new sound code has little benefit over the previous code (it does have the slight advantage of source management) to make it necessary to include it in the next release already. It's up to you. It seems like it touches a lot of parts of the code, and so would make future development hard to move to a master branch if it doesn't get into master fairly soon. Ok good point, lets include it. There are a few issues I'll sort out as soon as possible and have my fingers crossed it is tested on as many platforms as we can before the release. Erik -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Ubuntu 9.10, Pulseaudio - anybody had luck lately?
Ron Jensen wrote: Setting openal to not use pulse will not give these issues. Hm, that could be done for FlightGear. I´ve added support for using non default OpenAL output devices, but there's no code to use it that way yet. For example by using a command line option or environment variable. Erik -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] changes for the xml autopilot
Curt, that sounds scary and reminds me of one oddity I notices some time ago. That time only pid controller was affected, but I don't remember the details. I think it was the integral sum that was not reset to zero. The current implementation of the FGPIDController calculates differences to the last iteration which somehow got out of sync between reloads and screwed up the reference value. Without having looked into it deeply, this should be no factor anymore. If the xml-autopilot subsystemgroup is reinitialized, all contained autopilots are deleted with the destructor called and alll components are recreated from scratch. Please check, if you can still observe your described bug. Greetings, Torsten Hi Torsten, One thing I noticed recently (but this could have been in the code for a while) is that if a reference is a hard coded value instead of a property then if the autopilot definition is reloaded (something you might do often when tuning the autopilot) the value nodes can get mismapped to other nodes. I took a brief look at the code and noticed there had been some parser changes, but didn't unwind deep enough to get to the bottom of this. As a practical explanation of what I'm seeing: let's assume the first stage of the heading controller is to drive the heading-bug-error property to zero. The reference in this case is always going to be zero since the error term is computed inside the C/C++ code. In the same autopilot xml file the altitude controller has a reference of target-altitude which is a property. Let's say that is set to 3500 and I'm flying nicely. After reloading the autopilot, these can get mixed up and all of the sudden the heading controller is trying to drive the heading-bug-error to 3500 (the altitude) and this of course can never happen so the aircraft enters a perpetual circling pattern. The problem seems to be pretty deep in the parser which seems to have been rewritten a bit with some new subobjects, but I wasn't able to unravel the problem in the time I had available to look into it. :-( Thanks, Curt. On Fri, Nov 27, 2009 at 9:24 AM, Torsten Dreyer tors...@t3r.de wrote: Hi, I have just commited some changes to the xml autopilot. Along with a tiny bugfix comes a new feature which now allows more than one autopilot definition in the aircraft's -set.xml. You may now do something like this: sim systems autopilot pathAircraft/Hansajet/Systems/Hansajet-flightdirector.xml/path /autopilot autopilot pathAircraft/Hansajet/Systems/Hansajet-autopilot.xml/path /autopilot autopilot pathAircraft/Hansajet/Systems/Hansajet-digitalfilters.xml/path /autopilot /systems /sim Each autopilot element creates a new instance of the well known FGXMLAutopilot class which is added to a newly created SGSubsystemGroup. This subsystem group is added to the subsytem manager instead of the previous single instance of the autopilot. The idea behind this change is to be able to keep sophisticated autopilot configurations maintainable. No functional changes should happen to existing autopilots. Torsten - - Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] changes for the xml autopilot
Hi, Hi, I have just commited some changes to the xml autopilot. Along with a tiny bugfix Tiny? ;-) Compared to the development going on in the view and sound system, this is nothing ;-) Torsten -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] clouds heads up
On 11/28/2009 05:25 AM, Tatsuhiro Nishioka wrote: Hi Tim, As I said to you in IRC, I have a weird transparency problem with the shaders enabled. Here's the snapshot (helicopter view) with shaders. http://macflightgear.sourceforge.net/wp-content/uploads/snapshots/3dclouds-effect-enabled.png I used both FG/SG @ cvs-head as of yesterday and FG/SG @ Tim's git, but I got exactly the same result. The cause of this fancy rainbow-ish filter is the alpha calculation in both default.vert and model-default.vert. A lazy patch to avoid this issue is available at: http://macflightgear.sourceforge.net/wp-content/uploads/patches/shaders-weird-alpha-fix.diff I don't know if the real problem is in a shader side or C++ side. Tim, do you have any hint on this? Pretty bizzare. Obviously turning off alpha altogether isn't a real option. Is this a new problem since the 3d clouds went in, or are/were you seeing it without 3d clouds at all? What version of OSG are you using? Tim Best, Tat On Nov 27, 2009, at 2:41 AM, Tim Moore wrote: I've checked in code that changes 3D clouds to use effects. you should update simgear and Effects and Shaders in the data directory. There is a one frame blip of weirdness that I know about; a fix is in the works. Tim -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Ubuntu 9.10, Pulseaudio - anybody had luck lately?
Erik Hofman wrote: Ron Jensen wrote: Setting openal to not use pulse will not give these issues. Hm, that could be done for FlightGear. I´ve added support for using non default OpenAL output devices, but there's no code to use it that way yet. For example by using a command line option or environment variable. You can now specify a different OpenAL playback device using for example: --sound-device=Open Sound System (OSS) The list of available devices can be found by calling openal-info or alcinfo Erik -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] more sound problems with Tuesday cvs update
dave perry wrote: I have ATIS sound (at least at KBTL where I checked). Still no ident sounds for NDB, LOC, or VOR stations. Still now marker beacon sound. Ah, found the problem; the sound group volume wasn't set at initialization. Should be fixed now. Erik -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Simgear-cvslogs] CVS: source/simgear/scene/material Effect.cxx,
On Thu, 2009-11-26 at 19:55 +, Martin Spott wrote: Tim Moore wrote: Update of /var/cvs/SimGear-0.3/source/simgear/scene/material In directory baron.flightgear.org:/tmp/cvs-serv21713/simgear/scene/material Modified Files: Effect.cxx Log Message: [...] +#include boost/tr1/unordered_map.hpp requiring to add yet another patch to the build procedure :-/ Martin. Hi Tim, As Martin says, this now requires another patch to use boost 1.34, but the patch is to only comment out this additional #include, since Effect.hxx is already included, which includes 'unordered_map'... My Patches: ~/fg/fg7/simgear/source$ cvs diff [snip] Index: simgear/scene/material/Effect.cxx === RCS file: /var/cvs/SimGear-0.3/source/simgear/scene/material/Effect.cxx,v retrieving revision 1.29 diff -r1.29 Effect.cxx 33c33 #include boost/tr1/unordered_map.hpp --- // #include boost/tr1/unordered_map.hpp Index: simgear/scene/material/Effect.hxx === RCS file: /var/cvs/SimGear-0.3/source/simgear/scene/material/Effect.hxx,v retrieving revision 1.9 diff -r1.9 Effect.hxx 22,23c22,27 #include boost/tr1/unordered_map.hpp --- #include boost/version.hpp #if BOOST_VERSION 103401 #include boost/tr1/unordered_map.hpp #else #include tr1/unordered_map // for c++/4.2/tr1/unordered_map #endif [snip] You have left/returned configure.ac to - AX_BOOST_BASE([1.34.0]) Thanks for this... I hope you will apply the above... Regards, Geoff. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fg shows a blank screen
Hi all, I only get a blank single colour screen when I run fg (latest cvs/svn versions of plib/osg/simgear/fg). The colour changes with time settings, it is grey at noon, bluish at dusk, and black in night time. I can see the top menu and I have sound. I get the message saying which runway I am located at. On the startup terminal I get messages like this one Sat Nov 28 16:27:15 signori.local fgfs[54344] Error: CGBitmapContextCreate: unsupported parameter combination: 8 integer bits/component; 16 bits/pixel; 1-component color space; kCGImageAlphaLast; 512 bytes/row. Sat Nov 28 16:27:15 signori.local fgfs[54344] Error: CGContextDrawImage: invalid context 0x0 It worked for me a few day ago. I am compiling/running on a 64-bit mac 10.6.2. I'll try to find the problem but I am hoping for a pointer where to begin (excluding the option to roll back to a previous CVS state). Maybe someone has a hunch of a recent change that may have caused my blank screen. Cheers, Jari -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fg shows a blank screen
Jari Häkkinen a écrit : Hi all, I only get a blank single colour screen when I run fg (latest cvs/svn versions of plib/osg/simgear/fg). The colour changes with time settings, it is grey at noon, bluish at dusk, and black in night time. I can see the top menu and I have sound. I get the message saying which runway I am located at. same here with the last OSG svn, menu and hud is working and the plane too, but i only have black to blue screen, taking an old OSG solved the problem for me (i used the 10820 revision). jano -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] clouds heads up
Hi, On Nov 28, 2009, at 7:16 PM, Tim Moore wrote: On 11/28/2009 05:25 AM, Tatsuhiro Nishioka wrote: Hi Tim, As I said to you in IRC, I have a weird transparency problem with the shaders enabled. Here's the snapshot (helicopter view) with shaders. http://macflightgear.sourceforge.net/wp-content/uploads/snapshots/3dclouds-effect-enabled.png I used both FG/SG @ cvs-head as of yesterday and FG/SG @ Tim's git, but I got exactly the same result. The cause of this fancy rainbow-ish filter is the alpha calculation in both default.vert and model-default.vert. A lazy patch to avoid this issue is available at: http://macflightgear.sourceforge.net/wp-content/uploads/patches/shaders-weird-alpha-fix.diff I don't know if the real problem is in a shader side or C++ side. Tim, do you have any hint on this? Pretty bizzare. Obviously turning off alpha altogether isn't a real option. Is this a new problem since the 3d clouds went in, or are/were you seeing it without 3d clouds at all? What version of OSG are you using? I guess this problem is not that new, but I couldn't see it until you introduced the alpha calculation on .vert files. As a matter of fact, a bit older FG/SG/OSG/data (cvs or svn as of Sep/07/2009) and the latest shaders (all .eff, .vert, .frag, and materials.xml as of Nov/28/2009) gave me the similar result. The rainbow-ish effect shows up on both scenery and ground objects. Only the difference is that the older FG doesn't have a rainbow-ish effect on the aircraft model, while the latest FG/SG the latest Shader make a rainbow-ish effect on the aircraft model as well. (FYI, I use OSG/svn on Nov/27 for the latest FG/SG.) This rainbow-ish effect shows up with or without 3D clouds on both old and the latest FG, so I guess it has nothing to do with the new 3D cloud shader. Anyway, I'll keep investigating this. Tat Tim -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FSWeekend impressions
Hi, found a video on Youtube, showing some scenes from the FSweekend. And yes, we can see FlightGear:http://www.youtube.com/watch?v=HCTo4Pfi1Mofeature=related It starts at 1:24 starring Durk Talsma! There might be more videos as well! Regards HHS Hi All, Last weekend we've been organizing a booth at FSWeekend again. I'll try to write a few more elaborate set of impressions later, however, let me just say that our booth was quite large this year. :-) In the mean time, here are some pictures: http://www.xs4all.nl/~dtalsma/FSWeekend/web/index.html Cheers, Durk -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FSWeekend impressions
Does anyone have any info on the cockpit panel shown at about time 1:18 in that video? I'm wondering what they used for the various displays. If it's known an e-mail address for the builder would be appreciated! jj http://kingmont.com jj On Sat, 2009-11-28 at 19:40 +, Heiko Schulz wrote: Hi, found a video on Youtube, showing some scenes from the FSweekend. And yes, we can see FlightGear:http://www.youtube.com/watch?v=HCTo4Pfi1Mofeature=related It starts at 1:24 starring Durk Talsma! -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PATCH Suggested configure.ac changes/improvements affecting mac users
Tatsuhiro Nishioka wrote:
Hi Jari,
First, I made patches for configure.ac in both SimGear and FlightGear
(except svn lib part) so please give it a try.
I tried your changes and they work well. However, I have a slightly
different strategy so I took your changes and adopted them to my
configure.ac files.
I have added a check for the OpenAL framework in my fg configure.ac, in
your diff you simply assume that OpenAL is available. It may be true but
better safe than sorry. (See fg-check4OpenAL-confgure.diff for details.)
I added a same check to sg configure.ac (sg-check4OpenAL-configure.diff)
Your strategy with adding alut.h to your mac and use your patch to the
sg/fg configure.ac files works well. I would like you to consider the
below replacement strategy
# This assumes you have alut.h (that comes with Creative's
OpenAL.framework) in
/Developer/SDKs/MacOSX10.6/System/Library/OpenAL.framework/Headers
As I wrote in my previous posting I removed all dependency on alut.h.
This was trivial and required only changes in a few files in directory
simgear/simgear/sound. My understanding of the code is that the only
alut function used in simgear for mac is alutLoadWAVFile. If the changes
proposed in my previous post in this thread are made to simgear CVS
there is no need to add alut.h (and my sg configure.ac diff provided
here can be used with the trivial change outlined in the diff).
My proposed changes could be augmented with declarations of all five
alut functions in the OpenAL framework supplied by Apple. Use of any
other alut functionality will break simgear on default mac OpenAL
installation anyway. (It is possible to install freealut 1.1 and get
support for more alut functionality).
My point is, we can add some declarations to
simgear/simgear/sound/soundmgr_openal.hxx (or cxx) and get rid of
alut.h. This is how I do it and it works.
Cheers,
Jari
Index: configure.ac
===
RCS file: /var/cvs/SimGear-0.3/source/configure.ac,v
retrieving revision 1.118
diff -u -p -r1.118 configure.ac
--- configure.ac22 Nov 2009 22:23:01 - 1.118
+++ configure.ac28 Nov 2009 20:34:19 -
@@ -303,12 +303,6 @@ case ${host} in
*-apple-darwin*)
dnl Mac OS X
-LIBS=$LIBS -framework IOKit -framework OpenAL
-openal_LIBS=$LIBS
-# not sure how to test if OpenAL exists on MacOS (does it come by default?)
-OPENAL_OK=yes
-ALUT_OK=yes
-
dnl Thank you Christian Bauer from SheepSaver
dnl Modified by Tatsuhiro Nishioka for accepting a given framework path
dnl AC_CHECK_FRAMEWORK($1=NAME, $2=INCLUDES, $3=FRAMEWORK_PATH) ; $3 is
optional
@@ -338,6 +332,32 @@ case ${host} in
AS_VAR_POPDEF([ac_Framework])dnl
])
+LIBS=$LIBS -framework IOKit -framework OpenAL
+openal_LIBS=$LIBS
+
+if test x$with_openal_lib != x; then
+echo libopenal is not supported on Mac OS platform.
+openal_LIBS=
+else
+dnl Check that OpenAL framework can be found
+save_CPPFLAGS=$CPPFLAGS
+CPPFLAGS=
+AC_CHECK_FRAMEWORK(OpenAL,[#include OpenAL/al.h])
+if test x$ac_cv_framework_OpenAL = xyes ; then
+openal_LIBS=$FRAMEWORKS
+OPENAL_OK=yes
+# alut backward compatibility libs are provided by Apple
+# OpenAL (at least for OSX 10.5 and 10.6), no alut.h file
+# is provided. Just un-comment below line, and remove the
+# check in alut.h header.
+# ALUT_OK=yes
+dnl Looking for alut.h, if found assume that it is a part
+dnl of the OpenAL package.
+AC_CHECK_HEADERS([OpenAL/alut.h],[ALUT_OK=yes])
+fi
+CPPFLAGS=$save_CPPFLAGS
+fi
+
;;
*)
Index: configure.ac
===
RCS file: /var/cvs/FlightGear-0.9/source/configure.ac,v
retrieving revision 1.156
diff -u -p -r1.156 configure.ac
--- configure.ac22 Nov 2009 22:23:40 - 1.156
+++ configure.ac28 Nov 2009 20:28:04 -
@@ -399,11 +410,22 @@ case ${host} in
*-apple-darwin*)
dnl Mac OS X
-LIBS=$LIBS -framework IOKit -framework OpenAL
-openal_LIBS=$LIBS
-# not sure how to test if OpenAL exists on MacOS (does it come by default?)
-OPENAL_OK=yes
-ALUT_OK=yes
+if test x$with_openal_lib != x; then
+# Check for openal libs with AC_CHECK_LIB() missing here!
+openal_LIBS=
+else
+# Check that OpenAL framework can be found
+save_CPPFLAGS=$CPPFLAGS
+CPPFLAGS=
+AC_CHECK_FRAMEWORK(OpenAL,[#include OpenAL/al.h])
+if test x$ac_cv_framework_OpenAL = xyes ; then
+openal_LIBS=$FRAMEWORKS
+OPENAL_OK=yes
+ALUT_OK=yes
+fi
+CPPFLAGS=$save_CPPFLAGS
+fi
+
;;
*)
--
Let Crystal
Re: [Flightgear-devel] FSWeekend impressions
Hi, maybe this one: http://www.flyengravity.com/ Cheers Does anyone have any info on the cockpit panel shown at about time 1:18 in that video? I'm wondering what they used for the various displays. If it's known an e-mail address for the builder would be appreciated! jj http://kingmont.com jj On Sat, 2009-11-28 at 19:40 +, Heiko Schulz wrote: Hi, found a video on Youtube, showing some scenes from the FSweekend. And yes, we can see FlightGear:http://www.youtube.com/watch?v=HCTo4Pfi1Mofeature=related It starts at 1:24 starring Durk Talsma! -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PATCH Suggested configure.ac changes/improvements affecting mac users
Hi again, Tanks for the pointers. My comments was to elaborate on the consequences of the removed alut support by Apple. It is dangerous to use any alut.h you find on the web. As you point out using Creatives alut.h may make things simpler (macports.org is another option). I used freealuts alut.h which made the compiler to choose an unexpected path (for macs) in the source during compilation. The path chosen by the compiler required more alut functionality than provided by my mac. However, using freealut libs and alut.h, and Apples OpenAL framework works perfectly, I have done that for a while. (Now I changed strategy as outlined in other postings in this thread.) Cheers, Jari Tatsuhiro Nishioka wrote: Jari Häkkinen wrote: Tatsuhiro Nishioka wrote: Ah, so there is no real need for alut.h at all. Hm, so the alut.h issue should rather go in to simgear. I now tested with a zero length alut.h and no libalut. Compiling works but the linker fails with alut-complaints Undefined symbols: _alutInitWithoutContext, referenced from: SGSoundMgr::SGSoundMgr()in libsgsound.a(soundmgr_openal.o) I guess you're using SG from Tim's git repository (or similar). To get simgear I of course had to provide an alut.h but the one I have is from freealut-1.1 which gives me unwanted consequences. I am not sure about the #if statements on ALUT_API_MAJOR_VERSION in simgear/soundmgr_openal.cxx but I think that the compiler should not compile code calling alutInitWithoutContext on Apple computers. With my below suggested changes this issue will go away. Using alut.h from freealut-1.1 with Apple's OpenAL.framework (0.0.8) is a big problem. You need to use alut.h that comes with OpenAL.framework in Creative's OpenAL installer. SimGear's sound_manager.cxx uses free-alut's ALUT functions only if ALUT_API_MAJOR_VERSION is defined (free-alut's alut.h defines it, but (older) alut.h in OpenAL.framework doesn't), so using alut.h that comes with Creative's OpenAL.framework gets rid of your linker error. As a matter of fact, I have no linker errors in compiling SG @ Tim's git with alut.h that comes with Creative's OpenAL installer. and more. Listing alut-related functions in the OpenAL framwork only gives a short list of alut related functions: # nm openAL | grep alut 00013133 T _alutExit 00013168 T _alutInit 00013a2e T _alutLoadWAVFile 000136f8 T _alutLoadWAVMemory 0001311e T _alutUnloadWAV I have freealut installed to resolve the above linker problem Browsing through simgear/soundmgr_openal.cxx it looks like the calls to non-supported alut functions can be avoided. I look into that. I removed all dependencies on alut.h which all seems to be in simgear/sound only. I simply removed a few include statements and added one function declaration (see attached patch file). All of the fg components now compiles without any alut/freealut added (except for the backward compatibility stuff in OpenAL framework supplied by Apple). Isn't there non-alut replacement for alutLoadWAVFile? If there is then alut could be removed completely. I have not yet had the possiblity to extensively test the changes suggested in the patch but during a short flight the changes seems to work. If the proposed changes is pushed to the official simgear CVS then the configure scripting will be easier for simgear and fg/source wrt alut (at least for mac developers). Using the alut.h in Creative's OpenAL.framework will get the job done, so you don't have to do this yourself. If you want to use more embedded way rather than adding alut.h to Mac's Developer SDK, then you can locally add alut.h to simgear/sound folder. I used this way to avoid changing headers on every OS update. You can also use the following patches for this purpose. http://macflightgear.svn.sourceforge.net/viewvc/macflightgear/trunk/patches/SimGear-0.3-cvs-20061203-MacOSX.diff?revision=170view=markup http://macflightgear.svn.sourceforge.net/viewvc/macflightgear/trunk/patches/alc.patch?revision=217view=markup First one is a patch for local alut.h inside SimGear and the second one is a patch to alc.h for compiling with gcc 4.2.x (optional) Maybe you want to change the folder name from MacOSX10.5.sdk to MacOSX10.6.sdk in the second patch. Best, Tat -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net
Re: [Flightgear-devel] PATCH Suggested configure.ac changes/improvements affecting mac users
Jari Häkkinen wrote: Hi again, Tanks for the pointers. My comments was to elaborate on the consequences of the removed alut support by Apple. It is dangerous to use any alut.h you find on the web. As you point out using Creatives alut.h may make things simpler (macports.org is another option). I used freealuts alut.h which made the compiler to choose an unexpected path (for macs) in the source during compilation. The path chosen by the compiler required more alut functionality than provided by my mac. However, using freealut libs and alut.h, and Apples OpenAL framework works perfectly, I have done that for a while. (Now I changed strategy as outlined in other postings in this thread.) From what I understand Apple is depreciating those old alut functions (but still keeps hem in the library for backwards compatibility) and is encouraging everyone to use the freealut package instead. And so do I. Erik -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PATCH Suggested configure.ac changes/improvements affecting mac users
On 2009-11-28 23.01, Erik Hofman wrote: Jari Häkkinen wrote: My comments was to elaborate on the consequences of the removed alut support by Apple. It is dangerous to use any alut.h you find on the web. As you point out using Creatives alut.h may make things simpler (macports.org is another option). I used freealuts alut.h which made the compiler to choose an unexpected path (for macs) in the source during compilation. The path chosen by the compiler required more alut functionality than provided by my mac. However, using freealut libs and alut.h, and Apples OpenAL framework works perfectly, I have done that for a while. (Now I changed strategy as outlined in other postings in this thread.) From what I understand Apple is depreciating those old alut functions (but still keeps hem in the library for backwards compatibility) and is encouraging everyone to use the freealut package instead. And so do I. Erik Yes, you are right. Jari -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fg shows a blank screen
On 2009-11-28 16.55, jean pellotier wrote: Jari Häkkinen a écrit : Hi all, I only get a blank single colour screen when I run fg (latest cvs/svn versions of plib/osg/simgear/fg). The colour changes with time settings, it is grey at noon, bluish at dusk, and black in night time. I can see the top menu and I have sound. I get the message saying which runway I am located at. same here with the last OSG svn, menu and hud is working and the plane too, but i only have black to blue screen, taking an old OSG solved the problem for me (i used the 10820 revision). I traced the problem to changeset 10838 in OSG. I cannot say what goes wrong but maybe one of the list readers do. http://www.openscenegraph.org/projects/osg/changeset/10838/OpenSceneGraph/trunk Is this a mac specific problem or does it occur in other OSs too? Jari -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fg shows a blank screen
Jari Häkkinen a écrit : On 2009-11-28 16.55, jean pellotier wrote: Jari Häkkinen a écrit : Hi all, I only get a blank single colour screen when I run fg (latest cvs/svn versions of plib/osg/simgear/fg). The colour changes with time settings, it is grey at noon, bluish at dusk, and black in night time. I can see the top menu and I have sound. I get the message saying which runway I am located at. same here with the last OSG svn, menu and hud is working and the plane too, but i only have black to blue screen, taking an old OSG solved the problem for me (i used the 10820 revision). I traced the problem to changeset 10838 in OSG. I cannot say what goes wrong but maybe one of the list readers do. http://www.openscenegraph.org/projects/osg/changeset/10838/OpenSceneGraph/trunk Is this a mac specific problem or does it occur in other OSs too? Jari not mac specific, here on debian SID, amd athlon xp2800+, nvidia 6200. jano -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fg shows a blank screen
On Sun, Nov 29, 2009 at 12:54 AM, Jari Häkkinen j...@flygarna.se wrote: I traced the problem to changeset 10838 in OSG. I cannot say what goes wrong but maybe one of the list readers do. http://www.openscenegraph.org/projects/osg/changeset/10838/OpenSceneGraph/trunk Good job pinpointing the trouble! Since that commit introduces a change in default behaviour, I suppose restoring the previous behaviour by explicitly specifying the mask should fix it. This works for me: http://gitorious.org/fg/jesters-clone/commit/e80075464dc67e868cfc42d209a4ca7c7be234f1 But we shall wait until one of our OSG experts takes a look. We might also want to make it conditional on the OSG version (always fun, that) because this enum value hasn't existed before. -- Cheers, Csaba/Jester -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] FC12 openal and pulseaudio question
Hi, I used the preupgrade to FC12 from FC10 this Saturday on my ASUS notebook (Intel core2 duo). This installed openal-soft-1.10.622-2 openal-soft-devel-1.10.622-2 and pulseaudio-0.9.21-1 I had to use OpenSceneGraph-2.9.5 as the svn up for osg broke fgfs link. With the above I either get good frame rates (same as in FC10) and no sound or crackly sound with very low frame rates depending on how I launch fgfs. Question: What versions of openal and pulseaudio are others with FC12 using that give good sound and performance? Thanks, DaveP. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
