Re: [Flightgear-devel] Depreciating ATCDCL (Was: Crashes on reset/re-position)
Hi Durk, Le 30/07/2010 09:38, Durk Talsma a écrit : And, as an aside, but I'm sure everybody is aware of that: only the _default_ compilation behavior is changed. If you compile with --enable-atcdcl, you'll still be able to get ATIS messages. By the way, kln89_page_apt.cxx ( http://gitorious.org/fg/flightgear/blobs/next/src/Instrumentation/KLN89/kln89_page_apt.cxx ) is still referencing unconditionally ATCDCL(line 29). Changing that line to : #if ENABLE_ATCDCL #include ATCDCL/commlist.hxx #else #include ATC/atcutils.hxx #endif leads to compilation errors (ATCData not defined, that is a struct, not a class BTW). I commited some changes to fix the MSVC build, but i didn't address that issue. Regards, -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery - album photo http://www.youtube.com/user/fgfred64 Videos -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Depreciating ATCDCL (Was: Crashes on reset/re-position)
On Thursday, July 29, 2010 11:11:39 pm Dave wrote: Erik Hofman wrote: On Wed, 2010-07-28 at 09:57 +0200, Erik Hofman wrote: While this probably is a step in the right direction it also means ATC chatter will be missing (for now). Ehm, ATIS that is. Erik Yes, I hadn't realised that when I made the suggestion, I mistakenly thought we were only discussing the attempt at intelligent AI traffic. It would be a shame to lose the ATIS, especially now it's working again following the sound changes. What I propose to do is to remove all the AI traffic stuff from ATCDCL, leaving just the ATC code, and then re-enable it at compile time by default. The AI traffic is where all the crashes originate from, and this would leave the frequency lookup and ATIS working until they are ported to the new ATC system. I've discovered that my Wife's laptop has a 3D card, so I should be able to remove the AI stuff and test it. As an alternative, I would suggest that we try to port the ATIS feature over to the new system. In my earlier mail, I implied doing that; I'm sorry if that didn't come across. (Having an ATIS that is integrated with the AIModels based system has several additional advantage, such as better integration with the slowly but steadily emerging ATC system for AIModels/Traffic manager traffic, and others). I'll have a look at what I can do this weekend. And, as an aside, but I'm sure everybody is aware of that: only the _default_ compilation behavior is changed. If you compile with --enable-atcdcl, you'll still be able to get ATIS messages. Cheers, Durk -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Depreciating ATCDCL (Was: Crashes on reset/re-position)
On Fri, 2010-07-30 at 09:38 +0200, Durk Talsma wrote: On Thursday, July 29, 2010 11:11:39 pm Dave wrote: Yes, I hadn't realised that when I made the suggestion, I mistakenly thought we were only discussing the attempt at intelligent AI traffic. It would be a shame to lose the ATIS, especially now it's working again following the sound changes. What I propose to do is to remove all the AI traffic stuff from ATCDCL, leaving just the ATC code, and then re-enable it at compile time by default. The AI traffic is where all the crashes originate from, and this would leave the frequency lookup and ATIS working until they are ported to the new ATC system. I've discovered that my Wife's laptop has a 3D card, so I should be able to remove the AI stuff and test it. As an alternative, I would suggest that we try to port the ATIS feature over to the new system. In my earlier mail, I implied doing that; I'm sorry if that didn't come across. (Having an ATIS that is integrated with the AIModels based system has several additional advantage, such as better integration with the slowly but steadily emerging ATC system for AIModels/Traffic manager traffic, and others). I'll have a look at what I can do this weekend. I have been thinking about ATIS (and all queued messeges for that matter) but I think that using OpenAL's queueing mechanism would be a good idea since it offloads the burden of compiling message samples from small sound files to OpenAL where you just add another small sound file to the queue. Let me think about it some more an maybe I can come up with a good Queueing extension to the soundmanager. Erik -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Depreciating ATCDCL (Was: Crashes on reset/re-position)
Erik Hofman wrote: On Wed, 2010-07-28 at 09:57 +0200, Erik Hofman wrote: While this probably is a step in the right direction it also means ATC chatter will be missing (for now). Ehm, ATIS that is. Erik Yes, I hadn't realised that when I made the suggestion, I mistakenly thought we were only discussing the attempt at intelligent AI traffic. It would be a shame to lose the ATIS, especially now it's working again following the sound changes. What I propose to do is to remove all the AI traffic stuff from ATCDCL, leaving just the ATC code, and then re-enable it at compile time by default. The AI traffic is where all the crashes originate from, and this would leave the frequency lookup and ATIS working until they are ported to the new ATC system. I've discovered that my Wife's laptop has a 3D card, so I should be able to remove the AI stuff and test it. The only user-visible feature that would be lost would be the messages to/from ATC and the AI traffic. That however is unavoidable given that that AI system is realistically unmaintainable. Cheers - Dave -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Depreciating ATCDCL (Was: Crashes on reset/re-position)
On Wed, 2010-07-28 at 09:57 +0200, Erik Hofman wrote: While this probably is a step in the right direction it also means ATC chatter will be missing (for now). Ehm, ATIS that is. Erik -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
