Re: [Flightgear-devel] new JSBSim CVS for FlightGear?

2009-01-12 Thread Erik Hofman
gerard robin wrote: Hello Erik, I have just updated within FG CVS the engines regarding the model that i am working on. These engines are now running with the the last update from Ron which is in the JSBSim CVS repo. I guess that you were talking about it. I can notice that is not a bug

Re: [Flightgear-devel] FlightGear 1.9.1

2009-01-12 Thread Alexis Bory - xiii
Vivian Meazza wrote: I'm seeing segfaults from time to time with Windows and CVS/Head trying to start when mp is running. Csaba Halász reports the same. It's most frustrating to try to track this one down, because it is not reliably repeatable. Assuming that we are not the only ones

Re: [Flightgear-devel] FlightGear 1.9.1

2009-01-12 Thread Yon Uriarte
Hi Fred, saw your message asking for some testing. I decided to post a new thread asking for more user testing: http://flightgear.org/forums/viewtopic.php?f=2t=2812 grep -r getenv OpenSceneGraph, possibly relevant env vars, some of them are changed in my patches:

Re: [Flightgear-devel] FlightGear 1.9.1

2009-01-12 Thread Stefan Seifert
On Monday, 12. January 2009, Alexis Bory - xiii wrote: Also, using gdb prevents this segfault to appear. It looks like having a timming issue in the different processes. When it's not reproducible with gdb, you can enable core dumps with ulimit -c unlimited before running FG. If it crashes it

Re: [Flightgear-devel] FlightGear 1.9.1

2009-01-12 Thread Vivian Meazza
Alexis wrote 9.1 Vivian Meazza wrote: I'm seeing segfaults from time to time with Windows and CVS/Head trying to start when mp is running. Csaba Halász reports the same. It's most frustrating to try to track this one down, because it is not reliably repeatable. Assuming that we

Re: [Flightgear-devel] FlightGear 1.9.1

2009-01-12 Thread Frederic Bouvier
Hi Yon, I saw that but also saw that the osgViewer::Renderer has its own minimum time that is not settable by environment variable, and the resulting time is the minimum of the two values, one from the pager and the other from the Renderer ( both initially set to 0.001 ). In my test build I

Re: [Flightgear-devel] FlightGear 1.9.1

2009-01-12 Thread James Turner
On 12 Jan 2009, at 11:19, Frederic Bouvier wrote: It also seems that large framerate ( more than 200 fps during splashscreen display, I even saw 600 at FSFO ) make the scenery load a bit longer. Curiouly, I see better loading time under Linux with an AMD Athlon XP 2400 and a NV FX5850,

Re: [Flightgear-devel] FlightGear 1.9.1

2009-01-12 Thread James Turner
On 11 Jan 2009, at 20:07, Tim Moore wrote: I propose that the 1.9.1 release be made from these maint branches. This would let progress continue in CVS while hopefully achieving some stability in a maintenance release. If current committers would like write access to these repos, let

Re: [Flightgear-devel] FlightGear 1.9.1

2009-01-12 Thread Yon Uriarte
Hi, On Mon, Jan 12, 2009 at 12:19 PM, Frederic Bouvier fredfgf...@free.frwrote: Hi Yon, I saw that but also saw that the osgViewer::Renderer has its own minimum time that is not settable by environment variable, and the resulting time is the minimum of the two values, one from the pager and

Re: [Flightgear-devel] new JSBSim CVS for FlightGear?

2009-01-12 Thread gerard robin
On lundi 12 janvier 2009, Erik Hofman wrote: gerard robin wrote: Hello Erik, I have just updated within FG CVS the engines regarding the model that i am working on. These engines are now running with the the last update from Ron which is in the JSBSim CVS repo. I guess that you were

Re: [Flightgear-devel] new JSBSim CVS for FlightGear?

2009-01-12 Thread Erik Hofman
gerard robin wrote: I could be wrong but Ron gave, with the FGPiston update, a c172 Engine update (eng_io320.xml) . According to the result it is very accurate. True, but this requires a base package update to work correctly. Which is better to delay a few days so the binary only bugfix

Re: [Flightgear-devel] new JSBSim CVS for FlightGear?

2009-01-12 Thread gerard robin
On lundi 12 janvier 2009, Erik Hofman wrote: gerard robin wrote: I could be wrong but Ron gave, with the FGPiston update, a c172 Engine update (eng_io320.xml) . According to the result it is very accurate. True, but this requires a base package update to work correctly. Which is better

Re: [Flightgear-devel] new JSBSim CVS for FlightGear?

2009-01-12 Thread Stefan Seifert
On Monday 12 January 2009 15:29:43 gerard robin wrote: On lundi 12 janvier 2009, Erik Hofman wrote: True, but this requires a base package update to work correctly. Which is better to delay a few days so the binary only bugfix release can get released. Ouups sorry i thought that we

Re: [Flightgear-devel] new JSBSim CVS for FlightGear?

2009-01-12 Thread gerard robin
On lundi 12 janvier 2009, Stefan Seifert wrote: I think this is a very good example of why regular releases are good. When the next release is already in sight, the pressure to push huge updates into maintenance releases lowers considerably. So, yes, it would be nice to have a much better

Re: [Flightgear-devel] GL_COLOR_MATERIAL error

2009-01-12 Thread gerard robin
On dimanche 11 janvier 2009, Frederic Bouvier wrote: gerard robin a écrit : On dimanche 11 janvier 2009, Frederic Bouvier wrote: gerard robin a écrit : On dimanche 11 janvier 2009, Frederic Bouvier wrote: gerard robin a écrit : On dimanche 11 janvier 2009, Frederic Bouvier wrote:

Re: [Flightgear-devel] New mandatory parameter in animation type material emission ??

2009-01-12 Thread Csaba Halász
On Wed, Sep 17, 2008 at 3:23 AM, Csaba Halász csaba.hal...@gmail.com wrote: I have made a sample patch for the emission property. However it only seems to work for me and not anybody else. Hopefully somebody can come up with a proper fix. Okay, here is another attempt. Please test and

Re: [Flightgear-devel] New mandatory parameter in animation type material emission ??

2009-01-12 Thread Frederic Bouvier
- Csaba Halász a écrit : On Wed, Sep 17, 2008 at 3:23 AM, Csaba Halász wrote: I have made a sample patch for the emission property. However it only seems to work for me and not anybody else. Hopefully somebody can come up with a proper fix. Okay, here is another attempt.