Re: [Flightgear-devel] Upcoming v0.9.8 release
On Sonntag 16 Januar 2005 18:33, Martin Spott wrote: > "Curtis L. Olson" wrote: > > Now that plib-1.8.4 is released, I'd like to push forward with the > > FlightGear v0.9.8 release. Does anyone have any changes that need to > > get put in before the release? > > Now that Mathias' patch is part of PLIB release maybe it makes sense to > reanimate the crease tokens in the Nimitz- and probably other models. > > Just an idea, Vivian prepares a *very* good new Nimitz model. I just put out the crease tokens together with the addition of the in cvs missing textures to get a state where all what is in cvs, is at least complete and works well with current recommended libs. ... to have a consistent state when the release happens. I won't put any further work in the the current Nimitz. So stay tuned, it will really look great! Greetings Mathias -- Mathias FrÃhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
On Sunday 16 January 2005 21:07, Erik Hofman wrote: > Oliver C. wrote: > >>Would this work just by defining two sections for the specific bindings, > >>like this: > >> > >> > >> > >>View Elevation (Default) > >> > >> 5 > >> > >> > >> > >>View Elevation (windows) > >> > >> 7 > >> > > > > The problem is, how do you define which section should be used by which > > OS? > > If you look at the code above you see that one has only an axis number > for unix and the other has only an axis number defined for windows. I > was wondering if this is accepted by the current code already. > > Erik > Now i understand what you meant. In this case it depends on the following: Does a definition get not defined when a value is missing? For example, when this is the definition: > >> > >>View Elevation (windows) > >> > >> 7 > >> then what happens when FlightGear is started on a unix system? Does this definition get ignored or do we have an error because of a NULL assignment? View Elevation (windows) <-- NULL for a UNIX OS? --> Does anyone know more about that? Best Regards, Oliver C. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
Oliver C. wrote: Would this work just by defining two sections for the specific bindings, like this: View Elevation (Default) 5 View Elevation (windows) 7 The problem is, how do you define which section should be used by which OS? If you look at the code above you see that one has only an axis number for unix and the other has only an axis number defined for windows. I was wondering if this is accepted by the current code already. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Upcoming v0.9.8 release
Martin Spott wrote: > > "Curtis L. Olson" wrote: > > Now that plib-1.8.4 is released, I'd like to push forward with the > > FlightGear v0.9.8 release. Does anyone have any changes that need to > > get put in before the release? > > Now that Mathias' patch is part of PLIB release maybe it makes sense to > reanimate the crease tokens in the Nimitz- and probably other models. > Yes, I'd like to do that - of course I still have the original 'creased' versions. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
"Curtis L. Olson" wrote: > Ampere K. Hardraade wrote: >>Will it make sense to add an option to the configure script for SimGear which >>specifies the path of OpenAL? > > Do we need this sort of thing? Not necessarily. I typically install every FlightGear dependency into the same directory that I later use for Sim-/FlightGear themselves. This way the respective libraries are being found without explicit notation of their path, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
"Curtis L. Olson" wrote: > Now that plib-1.8.4 is released, I'd like to push forward with the > FlightGear v0.9.8 release. Does anyone have any changes that need to > get put in before the release? Now that Mathias' patch is part of PLIB release maybe it makes sense to reanimate the crease tokens in the Nimitz- and probably other models. Just an idea, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
On Sunday 16 January 2005 13:13, Erik Hofman wrote:
> Oliver C. wrote:
> > Yes, i am waiting for the insertion of my joystick patch from 24 Dec.
> > 2004:
> >
> > http://www.mail-archive.com/flightgear-devel@flightgear.org/msg28933.html
> >
> > If there's something wrong with this patch, then please tell me.
>
> Would this work just by defining two sections for the specific bindings,
> like this:
>
>
>
> View Elevation (Default)
>
> 5
>
>
> true
>
> property-adjust
> /sim/current-view/goal-pitch-offset-deg
> 1.0
>
>
>
> true
>
> property-adjust
> /sim/current-view/goal-pitch-offset-deg
> -1.0
>
>
>
>
>
> View Elevation (windows)
>
> 7
>
>
> true
>
> property-adjust
> /sim/current-view/goal-pitch-offset-deg
> -1.0
>
>
>
> true
>
> property-adjust
> /sim/current-view/goal-pitch-offset-deg
> 1.0
>
>
>
>
> Erik
>
The problem is, how do you define which section should be used by which OS?
That's why i added a new property.
There's also another solution by reading the assigned joystick button number
with a nasal script like this way:
Pseudo Code:
view.panViewPitch(-1);
}
else
{
view.panViewPitch(1);
}
]]>
But someone on irc.flightgear.org told me, that this is more a hack than a
solution, so i decided to use the other solution by adding a new property to
the property system.
Best Regards,
Oliver C.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
"Curtis L. Olson" said: > Now that plib-1.8.4 is released, I'd like to push forward with the > FlightGear v0.9.8 release. Does anyone have any changes that need to > get put in before the release? > > Regards, > > Curt. > If the release isn't until at Monday morning EST, I'll have time to update my dev system and build and test with the plib release. Recently I've been using the sg & fg pre release tarballs, working on rpms that install and run on linux without using the command line (from fgrun launcher), so my local cvs doesn't have the changes from this week. Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
Oliver C. wrote: Yes, i am waiting for the insertion of my joystick patch from 24 Dec. 2004: http://www.mail-archive.com/flightgear-devel@flightgear.org/msg28933.html If there's something wrong with this patch, then please tell me. Would this work just by defining two sections for the specific bindings, like this: View Elevation (Default) 5 true property-adjust /sim/current-view/goal-pitch-offset-deg 1.0 true property-adjust /sim/current-view/goal-pitch-offset-deg -1.0 View Elevation (windows) 7 true property-adjust /sim/current-view/goal-pitch-offset-deg -1.0 true property-adjust /sim/current-view/goal-pitch-offset-deg 1.0 Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
On Sunday 16 January 2005 03:50, Curtis L. Olson wrote: > Now that plib-1.8.4 is released, I'd like to push forward with the > FlightGear v0.9.8 release. Does anyone have any changes that need to > get put in before the release? > > Regards, > > Curt. Yes, i am waiting for the insertion of my joystick patch from 24 Dec. 2004: http://www.mail-archive.com/flightgear-devel@flightgear.org/msg28933.html If there's something wrong with this patch, then please tell me. Best Regards, Oliver C. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
Ampere K. Hardraade wrote: On January 15, 2005 09:50 pm, Curtis L. Olson wrote: Now that plib-1.8.4 is released, I'd like to push forward with the FlightGear v0.9.8 release. Does anyone have any changes that need to get put in before the release? Regards, Curt. Will it make sense to add an option to the configure script for SimGear which specifies the path of OpenAL? Do we need this sort of thing? You can always set CPPFLAGS="/path/to/openal/headers" and LDDFLAGS="/path/to/openal/libs" You of course have to make sure your system can find the openal shared lib when you run flightgear (which involves /etc/ld.so.conf under linux.) Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Upcoming v0.9.8 release
On January 15, 2005 09:50 pm, Curtis L. Olson wrote: > Now that plib-1.8.4 is released, I'd like to push forward with the > FlightGear v0.9.8 release. Does anyone have any changes that need to > get put in before the release? > > Regards, > > Curt. Will it make sense to add an option to the configure script for SimGear which specifies the path of OpenAL? Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
