[Flightgear-devel] pa24 and seneca II autopilots broken
I just updated SimGear, fgfs source, and data from cvs on my FC10 notebook. The Century IIB, Century III, and Altimatic autopilot "hot spots" don't show with ctrl-C and they don't work. I checked to see if any of their files in Aircraft/Instruments-3D/ had been changed. They had not. So I am assuming some other recent change has broken them. The digital OAT in the pa24 is also broken. What all these share is panel xml files that are relative to a model that is then loaded in another model xml. I could fix the autopilot animations by switching to "pick" hot spots. Fixing the OAT is not that simple as the OAT panel uses "layers" to write the digital temps. Any recent changes come to mind that might be the cause? Regards, Dave P. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Mac crashes / corruption with CVS
James Turner wrote: > I'm always curious to know how other Mac users build FlightGear - does > your build setup produce an fgfs binary (or application bundle) you > could make available somewhere? It would provide another case I could > test locally. Since recently I actually do both (sort of). Since the past few months I have created fgfs, terrasync, atlas, and map. All from their respective repositories. I have an update and build script that updates my working copies and rebuilds the packages if needed. This of course has to be done in the proper order because of dependencies. Also, I avoid installing to much of the moving targets so my set up is not straightforward to copy ... actually come to think of it, if I redo some things it will be fairly easy to copy my setup. Also I use a start-up script that points to different locations to run fgfs (I share data with development and released versions of fg). The reason for doing the above is that I do not like the macflightgear strategy of having snapshot copies of different fg components in the macflightgear repository. Also, getting access to all new stuff takes a while since the macflightgear maintainer must update the repo. Last week I realized that I miss the OSX lancher. I checked out the OSX launcher from the repository (trunk branch ... I don't get latest fixes to the launcher :-0), hacked around with the Xcode stuff and now I have an application bundle. Unfortunately I only bundle minimum amount of information and use links to fg/data and some other things which makes the current bundle non-distributable. The fg app works well and I think that terrasync also works but Atlas is currently broken on my machine because Atlas is currently in heavy development (I use Atlas CVS trunk). In conclusion when my Mac bundle is usable I'll make it available. Jari -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Internet presentation and handling[ was FlightGear presentation on the LinuxTag expo]
Hi, First answer for this question "1. Joomla adds an extra layer of management between the actual content and how it gets presented to web visitors. The actual content and site settings are stored in a mysql database. Question: what if our "joomla" site gets hacked some how and vandalized? How easy is it to roll back changes and restore a site after it's been damaged? With our current system it's real easy ... I just rerun the web site rsync command and yell at the ISP to fix the security hole. If the problem is all contained within our mysql database and user managment system, then that could be harder to deal with. These are things we'll have to explore, but I assume there is a way to backup the entire site off line and restore it later if there is a problem? We supposedly have that capability with our phpbb forum, but the restore side of this has never been tested. Security and recoverability and fixability is something we need to consider if we were to make an official move from a simple system to a far more complex system." _ Generally: At first you have to be sure to make the whole installation safe. Only two or three people should have the acess to it and have authority to change things. As Torsten already said: it is a mount of work to keep pages like the wiki clean, so only few authors. Changing passwords regulary should be clear. No shared servers! Make a backup! It is better on a local server apart from the webserver. Not the system avsim.com used! ;-). In the case of an hack: you can make list of those files which has changed, there is a script available for it. But it is better to delete everything and then new installation with the backup. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Internet presentation and handling[ was FlightGear presentation on the LinuxTag expo]
> Here are a couple thoughts from a devil's advocate perspective: > > Question: what if our "joomla" site gets hacked some how and vandalized? > How easy is it to roll back changes and restore a site after it's been > damaged? With our current system it's real easy ... I just rerun the web > site rsync command and yell at the ISP to fix the security hole. If the > problem is all contained within our mysql database and user managment > system, then that could be harder to deal with. These are things we'll > have to explore, but I assume there is a way to backup the entire site off > line and restore it later if there is a problem? We supposedly have that > capability with our phpbb forum, but the restore side of this has never > been tested. Security and recoverability and fixability is something we > need to consider if we were to make an official move from a simple system > to a far more complex system. Joomla is a mature system and these topics have all been addressed. At least technically. We need someone with the knowledge how to perform these tasks, though. > > 2. Simplicity versus complexity. For a long time I displayed a "powered by > vi" banner on my personal home page. That was somewhat intended in humor, > but it was also at least half true. My site was actually powered by a > combination of vi + emacs. You may continue to use vi + emacs to edit the template. And for the content, you may use the mysql command line client and to a 'insert into jos_content blah blah blah;' if you hate the gui ;-) > You probably already know this about me, but I do often view the latest > fads and the latest hype with a certain amount of skepticism. I am I going > to get massively flamed in 2 years when "froombla" is released and it's way > better than joombla and we aren't using it? :-) That will happen anyway - no matter if we stick to the current site or move to Joomla, typo3, xoops, [enter_your_favourite_cms_here]. No escape. > Have any joombla sites > crashed and burned because someone had a weak password and their account > was hacked? Or because there was some security hole in the code? And if a > mysql database gets corrupted or damaged for some reason, how hard is the > repair job? First question: Definitely yes. Second question: If they had a backup, other than the avsim guys: it's easy. My conclusion is: Having the technique, the CMS, is just premise #1. A complex system needs one or better two operators for the housekeeping. They need a certain skill and a good bunch of spare time to do the job. I am not talking about creating a flashy template or writing some content. It is the dirty all day work: removing spam, (un)locking users, resetting passwords, granting/revoking rights, etc. Just have a look at the countless hours Gijs and is spending on the wiki and you know what I mean. But if we can perform the task of setting up and operating a CMS, it will be a great improvement for flightgear.org. Torsten -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Internet presentation and handling[ was
Curtis Olson wrote: > Question: what if our "joomla" site gets hacked some how and vandalized? > How easy is it to roll back changes and restore a site after it's been > damaged? With our current system it's real easy ... I just rerun the web > site rsync command and yell at the ISP to fix the security hole. If the > problem is all contained within our mysql database and user managment > system, then that could be harder to deal with. The MySQL database is sufficiently braindead to have a backup at file system level, especially for those setups which don't see continuous editing. If you don't find a better option, then I'd offer to provide backup for the CMS-configuration plus the database to a remote system, including some history and the such, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Internet presentation and handling[ was FlightGear presentation on the LinuxTag expo]
Hi Curt, nice to see that you agree with this area. I'm still doing some wokr on it, sou everyone can see what I like to see and what not. I have similar feelings about safety when I thought about some things yesterday, but can't believe, that Joomla! is more unsave than other systems. I will investigate and try to get answers so we can absolutely sure- I would really like to see CMS, but if Joomla! is unsafe, trere are some others as well. Cheers HHS still in work: http://www.hoerbird.net/galerie.html But already done: http://www.hoerbird.net/reisen.html Von: Curtis Olson An: FlightGear developers discussions Gesendet: Montag, den 15. Juni 2009, 18:37:51 Uhr Betreff: Re: [Flightgear-devel] Internet presentation and handling[ was FlightGear presentation on the LinuxTag expo] On Sun, Jun 14, 2009 at 4:32 AM, Heiko Schulz wrote: Hi all, I installed Joomla! yesterday on my page, for making a example of what could be flightgear.org in the next time. This is a "me too" post. :-) I have also installed joomla-1.5 here: http://www.flightgear.org/joomla/ What you will find there is the originally installed default "content". However, joomla does look pretty cool and if we want to explore this direction, we could have people register and start playing around with content management. Here are a couple thoughts from a devil's advocate perspective: 1. Joomla adds an extra layer of management between the actual content and how it gets presented to web visitors. The actual content and site settings are stored in a mysql database. Question: what if our "joomla" site gets hacked some how and vandalized? How easy is it to roll back changes and restore a site after it's been damaged? With our current system it's real easy ... I just rerun the web site rsync command and yell at the ISP to fix the security hole. If the problem is all contained within our mysql database and user managment system, then that could be harder to deal with. These are things we'll have to explore, but I assume there is a way to backup the entire site off line and restore it later if there is a problem? We supposedly have that capability with our phpbb forum, but the restore side of this has never been tested. Security and recoverability and fixability is something we need to consider if we were to make an official move from a simple system to a far more complex system. 2. Simplicity versus complexity. For a long time I displayed a "powered by vi" banner on my personal home page. That was somewhat intended in humor, but it was also at least half true. My site was actually powered by a combination of vi + emacs. Modern, highly complex systems can be great, but they can also turn into a nightmare if something (even something small and simple) goes wrong. We live in a culture that lives for the next gadget, then next feature, the next release. For most of us newer is automatically better. The more flashy, the more technically complicated, the more features, the more gadgets ... the better. The other approach is to value "tried and true", to value things that are well tested and have proven themselves over the course of suffcient time. I'm not saying this to setup an argument for or against anything, I'm just saying that we need to keep a healthy perspective of the tradeoffs, the risks, and the potential difficulties if we were to move forward with it. You probably already know this about me, but I do often view the latest fads and the latest hype with a certain amount of skepticism. I am I going to get massively flamed in 2 years when "froombla" is released and it's way better than joombla and we aren't using it? :-) Have any joombla sites crashed and burned because someone had a weak password and their account was hacked? Or because there was some security hole in the code? And if a mysql database gets corrupted or damaged for some reason, how hard is the repair job? So anyway for those that are impatient (although I've never seen any evidence of that around here) you can register and give it a try. I probably have to give you write access once you register, but registration is step #1. Best regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Internet presentation and handling[ was FlightGear presentation on the LinuxTag expo]
On Sun, Jun 14, 2009 at 4:32 AM, Heiko Schulz wrote: > *Hi all,*** > *I installed Joomla! yesterday on my page, for making a example of what > could be flightgear.org in the next time.* > This is a "me too" post. :-) I have also installed joomla-1.5 here: http://www.flightgear.org/joomla/ What you will find there is the originally installed default "content". However, joomla does look pretty cool and if we want to explore this direction, we could have people register and start playing around with content management. Here are a couple thoughts from a devil's advocate perspective: 1. Joomla adds an extra layer of management between the actual content and how it gets presented to web visitors. The actual content and site settings are stored in a mysql database. Question: what if our "joomla" site gets hacked some how and vandalized? How easy is it to roll back changes and restore a site after it's been damaged? With our current system it's real easy ... I just rerun the web site rsync command and yell at the ISP to fix the security hole. If the problem is all contained within our mysql database and user managment system, then that could be harder to deal with. These are things we'll have to explore, but I assume there is a way to backup the entire site off line and restore it later if there is a problem? We supposedly have that capability with our phpbb forum, but the restore side of this has never been tested. Security and recoverability and fixability is something we need to consider if we were to make an official move from a simple system to a far more complex system. 2. Simplicity versus complexity. For a long time I displayed a "powered by vi" banner on my personal home page. That was somewhat intended in humor, but it was also at least half true. My site was actually powered by a combination of vi + emacs. Modern, highly complex systems can be great, but they can also turn into a nightmare if something (even something small and simple) goes wrong. We live in a culture that lives for the next gadget, then next feature, the next release. For most of us newer is automatically better. The more flashy, the more technically complicated, the more features, the more gadgets ... the better. The other approach is to value "tried and true", to value things that are well tested and have proven themselves over the course of suffcient time. I'm not saying this to setup an argument for or against anything, I'm just saying that we need to keep a healthy perspective of the tradeoffs, the risks, and the potential difficulties if we were to move forward with it. You probably already know this about me, but I do often view the latest fads and the latest hype with a certain amount of skepticism. I am I going to get massively flamed in 2 years when "froombla" is released and it's way better than joombla and we aren't using it? :-) Have any joombla sites crashed and burned because someone had a weak password and their account was hacked? Or because there was some security hole in the code? And if a mysql database gets corrupted or damaged for some reason, how hard is the repair job? So anyway for those that are impatient (although I've never seen any evidence of that around here) you can register and give it a try. I probably have to give you write access once you register, but registration is step #1. Best regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] X-Plane 850 file format support committed
- "Martin Spott" a écrit : > > http://frbouvi.free.fr/flightsim/KSFO-850.png > > Ah, thanks for comparing. > My reference airfields look correct, therefore I was under the > impression that the v8.50 KSFO layout is flawed. It doesn't look like > a numerical precision issue but obviously there's a fault at my end. As I already wrote, it looks like many bezier nodes are ignored and displayed as straight nodes. -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery - album photo http://fgsd.sourceforge.net/ FlightGear Scenery Designer -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SenecaII gear warning buzz
> Hi, I have seen that using SenecaII, after take off, I put MP at > 28"/2400RPM to keep cruise speed, but with this setting (Which lead at a > value of throttle around 0.14) the gear warning beeps ! > > so I modified the SenecaII-Sound.xml to stop watching for throttle > position, but to watch for MP value (That must be above 14 inches) for > each engine. > > you can find new version of the file here: > [url]http://brisa.homelinux.net/fgfs/SenecaII-Sound.xml[/url] > > I think this message should be sent to Torsten, but I don't have his > email here. > > Cheers > Francesco Hi Francesco thanks for your patch, which is now commited. The engine model in JSBSim has changed a while ago which cause some unrealistic throttle positions for boosted engines. Ron is aware of it and I think he will present a solution someday ;-) Torsten -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] X-Plane 850 file format support committed
Jon Stockill wrote: > Curtis Olson wrote: > >> I wonder what tricks and approaches the gaming community uses for >> drawing clear and realistic roads? The problem with cutting the lines >> into the surface as polygons is that (1) you explode the polygon count >> and (2) you have hard aliased edges which can become distracting in the >> distance. Cooking the lines into the surface texture gets rid of the >> aliasing problem, but then you explode your texture memory requirements >> and need to do a lot of work to generate those textures on the fly If you generate the textures on the fly, then texture memory requirements don't need to explode. However, fancy texture management is then required. Also, drawing credible roads quickly gets complex if you try to do things like lane markers and intersections. > > You also lose the polygon material mapping if you're just going to have > a surface (presumably generated from just SRTM data) with the generated > texture draped over it. IMHO this is a huge benefit of what we have > already, since that's what allows us to have things like amphibious > aircraft, operate aircraft from roads (I'm thinking of the harrier, > jaguar, air ambulance operations etc etc) and generally ensure a nice > bumpy landing when you have to choose a field for your glider because > you ran out of altitude before you made it back home. AFAIK this is > something pretty unique to FlightGear - we should think very carefully > before dropping it. You can get the material property by testing against the vector outline that's used to render the texture. Tim -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Mac crashes / corruption with CVS
On 14 Jun 2009, at 23:38, Jari Häkkinen wrote: > I am running fg on an MacBook Pro (10.5.7) equipped with an GeForce > 8600M GT graphics card. I have not experienced any problems with > macflightgears 1.9.1 nor with the May 19 CVS package (my 1 hour flight > ended just a few minutes ago). I usually run a non-macflighgear > based fg > that I build frequently without any problems related to the graphics > card. Thanks for the information, Jari - you've eliminated many possible explanations. (I was worried the 10.5.7 had included an nVidia driver update that broke something) I'm always curious to know how other Mac users build FlightGear - does your build setup produce an fgfs binary (or application bundle) you could make available somewhere? It would provide another case I could test locally. James -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
